James Robertson wrote: > I am new to jhalfs, so please bear with me. I am working on using > jhalfs to build a custom server personal "distro" for my IT shop. I am > starting with stock jhalfs 2.3.2 running commands for the 6.5 book on a > stock 6.4 host to start off with. > > I get this error at step 131-network > > Building target 131-network > make: *** [131-network] Error 2 > make: *** [mk_BOOT] Error 2 > > when I look at the logs\131-network file I see this error > > unable to open device '/sys/class/net/*' > > I can ls that on my host though > > ls -l /sys/class/net > total 0 > lrwxrwxrwx 1 root root 0 2009-08-28 15:01 eth0 -> > ../../devices/pci0000:00/0000:00:0a.0/net/eth0 > lrwxrwxrwx 1 root root 0 2009-08-28 09:09 lo -> ../../devices/virtual/net/lo > lrwxrwxrwx 1 root root 0 2009-08-28 09:09 sit0 -> > ../../devices/virtual/net/sit0 > > How can I see what the CHROOT environment sees with respect to this? I > see in the Makefile where the mounts happen for chroot > > devices: ck_LFS ck_UID > sudo mount -v --bind /dev $(LFS)/dev > sudo mount -vt devpts devpts $(LFS)/dev/pts > sudo mount -vt tmpfs shm $(LFS)/dev/shm > sudo mount -vt proc proc $(LFS)/proc > sudo mount -vt sysfs sysfs $(LFS)/sys > > Any ideas?
May seem like an obvious question, but what is the output of mount? Do you see $(LFS)/sys still mounted? Plus an easy to get back into chroot with jhalfs, is to do make chroot. Thomas -- http://linuxfromscratch.org/mailman/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
