In looking around last night I got to this page. Evidently I wasn't the only one with the dhcpcd not being shut down issue. The problem was fixed in a later revision.
I grabbed the latest official release and after checking that I didn't make any changes, I put the new wifi-radar main file where the old one was (after renaming the old one, so I could go back to it if needed). I still saw the errors, but it does shut down dhcpcd properly and thus also connect again without my having to fiddle around.
The curious thing is that I am now running revision 72 rather than 43... but the fix I noticed was in revision 86. Scrolling down, a similar issue was taken care of in revision 71. Evidently I got lucky and only ran into the earlier bug.
It looks like I'll probably be putting Wolvix on the laptop after all.
no subject
Date: 24 Jan 2007 15:15 (UTC)no subject
Date: 24 Jan 2007 16:12 (UTC)That is exactly the case. The older version was bundled with the distribution. I suspect it is what was bundled with the version of SLAX that Wolvix derives from. With the newer version, all I had to do was edit the wifi-radar.conf file to use eth0 rather than wlan0 and things "Just Work" - at least after stopping dhcpcd that is brought up on boot. After that, things are as they ought to be. I'm still running Wolvix as a LiveCD so that issue might well go away once it is installed to HDD. Or can be made to go away, at least.