On Mon, 2005-07-25 at 17:24 -0400, Derek Atkins wrote: > Quoting Colin Walters <walters verbum org>: > > > If you're using network login, your computer is tied specifically to > > that network; you can't switch networks, which invalidates a lot of the > > point of NetworkManager as it is today. For the short term you could > > just use your OS native wireless networking scripts, hardcode the > > wireless network and WEP key in /etc/whatever. > > Actually, that's not true at all. I could be in any of a dozen different > buildings at MIT, at my house, at Usenix or IETF or some other conference -- Yep, NetworkManager rocks for this. > and I should be able to use my standard network login from any of those > locations. I completely agree! The PAM cached credentials work should fix this. > Moreover, I have a bunch of network services that don't like to startup without > network. > Even now I have to restart ntpd, sendmail, and athena-zhm by hand.. As Dan said, this is just bugs in the init system and/or those daemons. > And I don't even want to think about the hell that OpenAFS would be! Most network file systems were designed before the roaming laptop era, and do not account for the network arbitrarily disappearing and instead like to eat applications by blocking them in IO wait state (hi NFS!). I don't know whether OpenAFS is similar but I imagine so. I just gave up on network file systems like NFS for my laptop long ago. > Yea, every once in a blue moon do I need a static IP.. It would be nice to have > it available. OTOH I don't think it's odd at all to want the network to come > up during the boot sequence. Note the desktop login is really part of the boot sequence from the normal user perception.
Attachment:
signature.asc
Description: This is a digitally signed message part