Package: yaird Version: 0.0.11-9 Severity: normal i am unable to figure out how to configure yaird for NFS Root.
reading the documentation in /usr/share/doc/yaird/yaird.html describes
the theory behind setting it up, but not how to actually set it up. the
configuration file format for yaird is anything but intuitive, so good
documentation is critical.
a diff of the configuration i attempted to use, and the default
configuration:
--- Default.cfg 2005-10-26 09:21:56.000000000 +0000
+++ Default.cfg.new 2005-10-30 19:47:14.909130146 +0000
@@ -98,19 +98,19 @@
# the 'network' command does not set up IP addresses,
# only the hardware.
#
- # NETWORK
+ NETWORK
#
# nfs implements the NFS protocol.
- # MODULE nfs
+ MODULE nfs
#
# af_packet allows access to network devices below
# the IP level, as raw packets. It's needed for DHCP
# clients.
- # MODULE af_packet
+ MODULE af_packet
#
# the nfsstart template uses DHCP to find IP addresses
# for the ethernet devices, then mounts a boot disk
# specified with DHCP and hands switches root to that.
- # TEMPLATE nfsstart
+ TEMPLATE nfsstart
the command:
# dpkg-reconfigure linux-image-2.6.14-1-386
Using /usr/sbin/mkinitrd.yaird to build the ramdisk.
Other suitable ramdisk generating tools : /usr/sbin/mkinitramfs.
Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd
/usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs.
yaird error: bad device name 'disk:/var/lib/lessdisks' (/etc/fstab:1)
(fatal)
Failed to create initrd image.
i can't figure out what the appropriate entry in /etc/fstab would be, as
many NFS Root setups have no entry in /etc/fstab for root at all, and
should be buildable in a chroot environment. perhaps if the third column
in /etc/fstab for "/" is "nfs" it should realize that it's an nfsroot?
since mkinitrd/initrd-tools is no longer supported by the newer 2.6
kernels, which makes initrd-netboot-tools useless, it would be nice to
have a viable replacement for initrd-netboot-tools.
live well,
vagrant
signature.asc
Description: Digital signature
