-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 16 Oct 2005 21:56:28 +0200
Erik van Konijnenburg <[EMAIL PROTECTED]> wrote:
> On Sun, Oct 16, 2005 at 02:42:53PM +0200, Sven Luther wrote:
> > In the meantime, i am refining the kernel-package patch, but am i
> > right in thinking there is no way to use yaird in a chroot ? It
> > complained about no root in /etc/fstab :)
>
> That depends on how completely you dress up the chroot. Yaird needs
> a fairly complete environment: /sys and /proc mounted, complete
> versions of /etc/modprobe.conf and /etc/fstab; see the FILES section
> of the manual page. I've never tested the chroot approach for yaird.
I have!
You need either to define your rootfs in /etc/fstab within your chroot
or edit /etc/yaird/Default.cfg to use nfsroot.
I have attached my configs working with lessdisks.
- 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)
iD8DBQFDUrvrn7DbMsAkQLgRAmwqAJ9uyrg0UF7LARtsycFyInxlS0j35ACfbYpL
3DRw1K2AGpQxrkIGwj0GgNE=
=aR05
-----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
