Jonathan, the other issue could be that udev is not detecting your network adapter, I do build my as a module, so that could be the difference.
Mine certainly isn't a module and I don't really want to mess around with my kernel configuration at the moment. Updating to udev-rules 1.1-pre3 doesn't appear to have changed anything either. My guess is that the start function in the network script is being called and since there is no such function in udev-rules version, it exits with a return value of 1. I confess that I don't really understand how having only the stop function (instead of start, restart, and stop) would make the whole hotplug thing work, but on my machine it continues to be unhappy with me. The clfs-bootscripts network script works just fine (minus the hotplugability of course), but it doesn't have the desired behavior. By the way, why do the the clfs-bootscripts and udev-rules network scripts have different stop functions? The clfs-bootscripts version looks at the interfaces in sysconfig and the udev-rules version looks at the ones in /sys. As a result, the udev-rules version attempts to take down interfaces that don't even exist when the computer is shut down. I don't think that that has anything to do with my difficulties, but it strikes as me as odd that they differ in that manner. I'd guess that one was changed and the other was not updated to match. In any case, I think that I'm going to have to give up on the udev-rules network script since it isn't working and I haven't a clue how to make it work. Either my setup doesn't work with it for some reason orthere's a bug that your setup manages to avoid and mine doesn't. I think that it would be good to fix such a bug if there is one, but I haven't a clue what it could be or how to do so. In either case, thanks for your help. - Jonathan M Davis _______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
