Ubuntu/GNOME deteriorating?
in [General Linux]
|
From: Kelsey Bjarnason on 27 Mar 2010 14:42 [snips] The Natural Philosopher wrote: >> Tell me, do you Linux freaks actually use your Linux systems for >> anything productive? > > yes. CAD work, communication with clients, developing back office > software, running back office software, USING the back office software > to place orders, ship goods and run a business..online stock trading and > market research..word processing..watching TV on, watching films on, > listening to the radio on..I can even run windows on it to run the two > applications out of the hundred or so that I use that WONT run under Linux! > Oh, but you don't seem to be running MS Office, so you're not doing *serious* work. Just ask raylopez. :)
From: RonB on 27 Mar 2010 14:54 On Sat, 27 Mar 2010 13:35:46 +0000, The Natural Philosopher wrote: > Moshe wrote: >> You seem to spend more time installing and removing various versions of >> Linux than anything else. > > No, that's what we talk about here. > Because that is - strangely - what this group is about. Strange how that works out, isn't it? You think "Moshe" will ever get a clue? -- RonB Registered Linux User #498581 CentOS 5.4 or Vector Linux Deluxe 6.0
From: Kelsey Bjarnason on 27 Mar 2010 14:48 [snips] Ignoramus8345 wrote: >> Probably. If by that you mean a windows like GUI that allows you to >> manually connect to WiFi. > > To wifi, and to wireless broadband and modems. > >> I have to say, I junked it in favour of a 'connect at boot time' script.. > > connect at boot time does not work for me -- I use too many different > ways of connecting. I have sort of the opposite problem: I prefer boot-time connections, as I tend to mount remote shares, which kinda necessitates having a working connection. While I could do this at "desktop time", I'd much rather have it done as part of the boot process. As a result, I tossed Network Manager and replaced it with wicd. wicd's model makes it trivial, as the GUI component isn't required to launch a connection; it's used to create new connections, manage existing ones, etc. I use the GUI to define my default wireless setup, on reboots it automagically does its thing, but I can switch to a different connection when needed. Perhaps NetworkManager can also do this, but IME, it doesn't; it seems to insist that the GUI component be run and the proper credentials supplied (i.e. enter the admin pass) before it'll do anything useful.
From: Moshe on 27 Mar 2010 15:13 On Sat, 27 Mar 2010 18:54:52 +0000 (UTC), RonB wrote: > On Sat, 27 Mar 2010 13:35:46 +0000, The Natural Philosopher wrote: > >> Moshe wrote: > >>> You seem to spend more time installing and removing various versions of >>> Linux than anything else. >> >> No, that's what we talk about here. >> Because that is - strangely - what this group is about. > > Strange how that works out, isn't it? You think "Moshe" will ever get a > clue? All your going on the offense won't change the fact that you have yet to back up your claims of YouTube videos owning your Windows machine. So where is the proof of your claims RonB?
From: Ignoramus11443 on 27 Mar 2010 15:29
On 2010-03-27, Kelsey Bjarnason <kbjarnason(a)gmail.com> wrote: > [snips] > > Ignoramus8345 wrote: > >>> Probably. If by that you mean a windows like GUI that allows you to >>> manually connect to WiFi. >> >> To wifi, and to wireless broadband and modems. >> >>> I have to say, I junked it in favour of a 'connect at boot time' script.. >> >> connect at boot time does not work for me -- I use too many different >> ways of connecting. > > I have sort of the opposite problem: I prefer boot-time connections, as > I tend to mount remote shares, which kinda necessitates having a working > connection. Not at all. I have a laptop on NetworkManager, and have several NFS mounts that only work at home. I have a little command that runs every 10 minutes and mounts these shares if I am at home. It works great . > While I could do this at "desktop time", I'd much rather > have it done as part of the boot process. > > As a result, I tossed Network Manager and replaced it with wicd. wicd's > model makes it trivial, as the GUI component isn't required to launch a > connection; it's used to create new connections, manage existing ones, > etc. This was not necessary. > I use the GUI to define my default wireless setup, on reboots it > automagically does its thing, but I can switch to a different connection > when needed. > > Perhaps NetworkManager can also do this, but IME, it doesn't; it seems > to insist that the GUI component be run and the proper credentials > supplied (i.e. enter the admin pass) before it'll do anything useful. Sadly, this is true. i |