On 08.12.2010 00:45, Joey Hess wrote: >> Doing a fully automated conversion would probably not be that easy and I'm >> not >> convinced it would be a good idea anyways. >> >> And we can't simply comment out entries like the above without risking to >> lose >> network connection. > > Unfortunatly I don't see much of a choice, unless you want to just > change the default to managed=true. There are probably a great many > systems out there that have already been installed and have this > problem.
I honestly doubt that. First, installing over wireless is certainly not the norm, especially as WEP is deader than dead and open wireless networks are not that common either. And second, allow-hotplug not working on your system is afaics due to a buggy driver. All in all this is a rather rare combination I'd say, altough I certainly admit it is an issue for you. Switching to managed=true has a much wider impact which I don't want to risk at this stage of the release. And simply commenting out wireless configurations generated by d-i is risky too: On systems where allow-hotplug works and ifupdown is used to configure the interface, commenting it out will kill the network configuration. A compromise could be, to only comment out a wireless configuration found in /e/n/i, if we find a corresponding (I'd use essid is the same as criteria) network-manager configuration. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
