-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 30 Oct 2005 14:44:36 -0700
Vagrant Cascadian <[EMAIL PROTECTED]> wrote:
> i am unable to figure out how to configure yaird for NFS Root.
Hi Vagrant :-)
I agree with you that this is not currently very well handled.
> i can't figure out what the appropriate entry in /etc/fstab would be,
Currently, MOUNTDIR does not support nfsroot so needs to be commented
out completely.
> 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?
Recognizing NFS rootfs defined in fstab would probably be neat and not
hurt, but would only work for cases like lessdisks were the ramdisk is
built within the chroot also offered as rootfs.
Another issue is NIC drivers to include. When run on the NFS server as
is usually the case with lessdisks, by default only the driver for the
server NIC is included, which probably isn't what you want.
Attached is my current approach to running lessdisks with yaird.
- Jonas
- --
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
- Enden er nær: http://www.shibumi.org/eoti.htm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDZU5fn7DbMsAkQLgRAvHmAJ9Kols59yXgRVXLdcSxXz+kK0tdlACfWyxi
+Sr19eXBAU119njPrMhoBCY=
=M5vP
-----END PGP SIGNATURE-----
--- Default.cfg.orig 2005-09-12 07:28:02.000000000 +0200
+++ Default.cfg 2005-10-13 02:21:07.000000000 +0200
@@ -66,7 +66,12 @@
# the disadvantage is that it stops working if you get a
# new kernel where the modules are named differently.
#
- INPUT
+ #INPUT
+ MODULE usbhid
+ MODULE psmouse
+ MODULE i8042
+ MODULE serio
+ MODULE atkbd
#
# MODULE -- make a module available. If the module is
@@ -93,6 +98,29 @@
MODULE evdev
#
+ # Try blindly to load network interface cards
+ MODULE ne
+ MODULE 3c509
+ MODULE 3c59x
+ MODULE 8139cp
+ MODULE 8139too
+ MODULE dmfe
+ MODULE e100
+ MODULE eepro100
+ MODULE e1000
+ MODULE eexpress
+ MODULE epic100
+ MODULE hp100
+ MODULE ne2k-pci
+ MODULE sis900
+ MODULE tlan
+ MODULE de4x5
+ MODULE tulip
+ MODULE via-rhine
+ MODULE yellowfin
+ MODULE forcedeth
+
+ #
# NETWORK -- Insert modules for all ethernet devices
# connected to the system, eg for NFS boot. Note that
# the 'network' command does not set up IP addresses,
@@ -101,16 +129,16 @@
# 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
#
# MOUNTDIR -- Given a directory name that occurs in
@@ -119,7 +147,7 @@
# and mount it somewhere else, eg in "/mnt".
# The block device can be raid, LVM, or encrypted.
#
- MOUNTDIR "/" "/mnt"
+ #MOUNTDIR "/" "/mnt"
#
# MOUNTDEV -- You can also specify the device to be
--- Templates.cfg.orig 2005-09-12 07:28:03.000000000 +0200
+++ Templates.cfg 2005-10-16 22:39:35.000000000 +0200
@@ -215,10 +215,11 @@
# optionList may be undef
# and already is suitably escaped.
+ # (used to blindly attempt loading all NIC, so never fail)
SCRIPT "/init"
BEGIN
!/sbin/insmod '<TMPL_VAR NAME=target>' \
- ! <TMPL_VAR NAME=optionList>
+ ! <TMPL_VAR NAME=optionList> || true
END SCRIPT
END TEMPLATE
