On Sat, Mar 29, 2014 at 2:54 PM, Stefan Lippers-Hollmann <[email protected]> wrote: > Hi > > On Saturday 29 March 2014, Cameron Norman wrote: >> This bug can be seen in Upstart (#694963), and hangs boot in a NFS >> mounted /usr, as well as errors the network setup when one uses "auto" >> in /etc/network/interfaces. Here is the output of ldd, with the libs in >> /usr bolded (HTML): > > [ please avoid HTML Mails, they're very likely to be eaten by antispam > measures along their way ]
Sorry about that, was not aware about the anti spam problems. > As you see in the bugreport, this is a long standing issue, which is > only partially under our control. Actually the situation has been > improved significantly during the last release cycle with many of the > required libraries moving from /usr/lib/ to /lib/ already. What remains > is libssl1.0.0, as libpcsclite can be avoided, but actually working on > that (which is a bit problematic on kfreebsd-any) doesn't make sense > before the hard-dependency is out of the way (libssl). I think another problem with starting wpa_supplicant before the filesystem is up is that it uses /var/run where it should use /run. Do you think you (or somebody else) will be interested in doing that? If so, should I file a new bug? > That said, trying to mount any remote filesystem over wlan at the > kernel level, even more so for vital filesystems just as /usr/, /var/ > or /tmp/ would be plainly insane, as you do have to expect interruption > with wlan for any real world deployment (which would make your system > hang, if vital parts are mounted over wlan). Likewise 'auto' is usually > not a good configuration for wireless interfaces either, as -like you > mentioned- this does block booting until a connection has been > established, which is something you can't guarantee for wlan - not even > for a static system. I do not think it blocks boot on async systems (at least when NFS is not used) like Upstart or systemd. Best regards, -- Cameron Norman -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
