> Package: initrd-netboot-tools > Version: 0.5.3cvs.20040906-11 > Severity: normal
> I tried switching an ia64 with an existing debian sarge netboot system > on it (was using a hand-built nfsroot kernel) to using > initrd-netboot-tools. There were some problems.. thanks for giving it a whirl... > I get this on boot, until I hit ctrl-c: > > /etc/lessdisks/mkinitrd/network_script: eth0: bound to 192.168.1.7 > NOTE: assuming siaddr 192.168.1.1 is also NFS server... > attempting to mount NFS filesystem... > mount -nt nfs -o ro,async,nolock 192.168.1.1:/srv/nfs/elephant /mnt > mount: proc already mounted or proc busy > INIT: version 2.86 booting > Couldnt get a file descriptor referring to the console at this point, it has booted past initrd-netboot-tools- all the messages are related to other scripts, most likely from /etc/rcS.d/* they are probably related to missing entries in /dev, like you suggested. > Well, I sshed in and it seems that /dev/ is a devfs filesystem. As I > have no devfsd, this can't work well. I looked at > /etc/lessdisks/mkinitrd/install_scripts/90_mount_nfs_root and found the > devfs mount there. Seems useless for my case since my nfs root includes > a complete, static /dev. I commented the mount out, remade my initrd, > and all is well. if you're using a 2.6 kernel, you might consider installing udev into the terminal's root filesystem. i have tried it and it seems to work with lessdisks without (too much) trouble- it will mount udev over the devfs mount and populate /dev with appropriate device nodes. > I think I'm trying to use this package in a way you didn't really > expect; probably some part of using it right (in a fully lessdisks > environment) makes the devfs mount make sense. i honestly don't remember why i started using devfs. lessdisks mounts it's root filesystem as read-only, and devfs is typically used to provide writeable access to the various devices in /dev. i'll look into it further. > I do think it would be nice if it supported what I'm trying to do with > it a little bit better. Maybe it could omit mounting devfs if /dev is > already fully populated? it's a little tricky, as it has to verify that we have write-access to /dev (or at least /dev/console), as well. ideas on how to get this to work intelligently would be appreciated. as a less-ideal workaround, i could also set up a configuration file variable that determines weather to use devfs or not. live well, vagrant p.s. please let us know about additional kernels you get working with initrd-netboot-tools, so we can add them to kernel-image-netbootable. currently only x86 and alpha kernels have been verified to work.
signature.asc
Description: Digital signature
