On Fri,18.Jul.08, 10:10:44, Sven Joachim wrote: > On 2008-06-25 19:09 +0200, Petter Reinholdtsen wrote: > > > [Andrei Popescu] > >> Attached > > > > Thank you. Reading the boot sequence, I see nothing obviously wrong > > with it. When exactly is the network interfaces configured? It need > > to be done by init.d/networking, and not by udev events, because > > /var/run/ is not writable when udev is executed. > > > > The only issue that can be problematic, is this one from rcS.d/: > > > >> S14networking > >> S15mountnfs.sh > >> S15shorewall > >> S16mountnfs-bootclean.sh > > And there's also S13bootmisc.sh which leads to /var/run being cleaned by > S16mountnfs-bootclean.sh, see #491059. This could mess up things quite > badly, especially if /etc/network/run is a symlink to /var/run. > > Andrei, can you please run the commands > > sed -i -e 's/local/remote/' /etc/init.d/bootmisc.sh > insserv > > and see if things get better after a reboot?
Yes, they do get better. Now I can use wpa_cli immediatelly after reboot, which wasn't possible before. wpa-supplicant is still picking up the wrong ap, which doesn't happen if I just blacklist the wireless module and modprobe it afterwards. I will try to test some more when I'm back from work. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein)
signature.asc
Description: Digital signature
