On Thu, Jan 8, 2009 at 10:28 AM, Mark Haney <mhaney@xxxxxxxxxxxxxxxx> wrote: > This is just a silly implementation change that > didn't need to be made. IMO. Initiating an interface on log in? Why? > I still have yet to see any reasonable explanation. Not that I expect > to get one. Pre-login networking is on the roadmap for NM development. There is desire to make pre-login possible, but its not the primary usage case that drives NM development. The intent was to focus first on mobile use cases, cases where multiple network credentials may need to be stored into a cryptographically secured cache for easily lookup and which can be unlocked by a human. I use 4 different vpn networks (depending on which national government's space based weaponry I'm working on that day), across a number of public and private wired and wireless dynamic networks. NM's design saves me hassle dealing with my own custom scripts. Do I really want to write a script that specifically helps me get on the curling club network and vpn into North Korea's weapon program datacenter handling the passphrases and crap..no thanks. With I login, unlock my session keyring. the curling clubs network brought up automatically and I just click on NM to start up the North Korean VPN or the Icelandic VPN...depending on which weapon I'm working on that day. Far less hassle than dealing with scripts for me. Pre-login network and multiple connections are on the roadmap moving forward. -jef -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
