From: J G Miller on
On Sat, 27 Mar 2010 19:33:34 -0500, JEDIDIAH wrote:

> Linux is the same bits repackaged in different ways.

CentOS being the best example of this ;)
From: chrisv on
The Natural Philosopher wrote:

> mentally-ill troll wrote:
>>
>> Wrong again Porter.
>
>To be honest, Moshe, one should refrain from projecting ones own
>inadequacies onto others.

Just KF the mentally-ill, nym-shifting POS.

From: Jonathan N. Little on
Hadron wrote:

> What he SAID, and I agree from first hand experience, is that its NOT
> just a case of BLINDLY copying your $HOME around and expecting it to
> work. There are umpteen incompatibilities between distros - even
> distros with a common inheritance. The COLA "advocates" would have you
> believe it all "just works". It doesnt.

> The problem with "advocates" is that they are normally so dumb that if
> and when they manage to create a separate HOME partition they think they
> are some kind of mega-1337 super hacker.


Now my "Document and Settings" folder *is* on a different drive and in
Windows that *is* some kind of mega-1337 super hacker. Linux is far more
flexible, easier, successful, to update, transfer, or recreate a profile
or system.

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
From: Mark on
On Sat, 27 Mar 2010 14:29:23 -0500, Ignoramus11443
<ignoramus11443(a)NOSPAM.11443.invalid> wrote:

>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 believe this issue is now fixed by I was not patient enough to wait
and I ditched Network Manager. I prefer manual configuration anyway
since you can easily back up your settings.
--
(\__/) M.
(='.'=) Due to the amount of spam posted via googlegroups and
(")_(") their inaction to the problem. I am blocking most articles
posted from there. If you wish your postings to be seen by
everyone you will need use a different method of posting.