Wireless setup

[Simon Geard]

On Tue, 2009-02-17 at 11:34 +0000, richard.melville at ntlworld.com wrote:
> On a laptop I can see the necessity for some control over a wifi
> connection because it is a mobile device, but on a desktop I cannot
> see why it is necessary.  It just seems to be over-complicating
> matters to invoke DHCP, dbus, hal, and networkmanager.  Surely, if, as
> you say, you want a wifi connection to happen automatically at
> boot-time then why not just enable it with boot scripts and a static
> IP address?  My view is: "the simpler the better".

Not addressed to me, but I'll answer as someone using NM for such a
desktop system. First, I have DHCP because my network uses DHCP. I have
dbus and hal because it's a desktop system, and whether you use KDE or
Gnome, dbus and hal are essential infrastructure these days.

So, given that, installing and running NM on top of that is hardly a
huge increase in complication. It's a simple enough trade - I can
configure things manually in boot scripts, or I can add a few more
packages to the system and have it all work for me. Personally, I'm
happy with knowing how to do the former, but choosing to do the latter.

Simon.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://linuxfromscratch.org/pipermail/blfs-support/attachments/20090218/fb16524c/attachment.bin