On Monday 30 August 2010 09:43:01 Andreas Kasenides wrote: > I have been trying to build LFS 6.5 with jhalfs 2.3.2 but have found out > that it > fails with script 131-network. As far as I can tell this script tries > to configure the network devices eth0,1... and lo (by doing a udev --test > on > devices in the /sys/classes/net/*)!! > Isn't this the wrong thing to do at that point in the build? > Since at that point we are running in a chroot environment > it is not possible to discover any ethernet devices (or any devices for > that > matter) that udev is supposed to discover at boot time and appropriately > mount the /sys filesystem. > > Am I missing something?
This is based on what I learned integrating udev into a system that didn't have it. I've never looked to see if udev effects changes in /sys. You might just be missing something. /Sys needs to be mounted before udev can do its thing. With /proc and /sys mounted, udev should be able to at least find devices for testing purposes. I don't think the kernel cares how many 'coldplug/hotplug listeners' there are. Having more than one daemon on the host and one in chroot actually changing device names could cause problems, though I've never investigated it. But having more than one daemon monitoring device changes shouldn't hurt a'tall. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
