bootdisk/nfsroot problems (fwd)

[Niall Young]

Haven't heard back from Thomas yet so I thought I'd see if anyone
can help.  One thing I noticed is /usr/lib/fai/nfsroot/initrd contains
nothing - how is rcS_fai called after boot?  This seems to be where
I'm stuck.

--                                                              
Niall Young						
             Linux Solutions -- www.linuxsolutions.net.au
     Providing Internet and Audio/Video Solutions and Consulting
 PH: 0407 421 537 -- PO BOX 1117, Gwelup WA 6018 -- GPG ID: 8B3AE631


---------- Forwarded message ----------
Date: Mon, 18 Sep 2000 17:08:15 +0800 (WST)
From: Niall Young <niall at linuxsolutions.net.au>
To: Thomas Lange <lange at informatik.Uni-Koeln.DE>
Subject: RE: bootdisk/nfsroot problems

On Thu, 14 Sep 2000, Thomas Lange wrote:

> If you get your potato CD's and have the FAI_ACTION problem futher
> more, please send me you dhcpd.conf and the log files (located in /tmp).

Hi Thomas,

Same problem I'm afraid - I've got my potato CDs but get stuck at the same
point.  Have followed INSTALL to the letter afaik.  DHCP and NFS appear to
be working fine.  /usr/lib/fai/nfsroot/fai/DHCP exists and the symlink in
/boot/fai is setup.

Sep 18 16:58:24 smeagol dhcpd-2.2.x: DHCPDISCOVER from 00:40:05:35:ce:9d via eth0
Sep 18 16:58:25 smeagol dhcpd-2.2.x: DHCPOFFER on 192.168.1.10 to 00:40:05:35:ce:9d via eth0
Sep 18 16:58:27 smeagol dhcpd-2.2.x: DHCPREQUEST for 192.168.1.10 from 00:40:05:35:ce:9d via eth0
Sep 18 16:58:27 smeagol dhcpd-2.2.x: DHCPACK on 192.168.1.10 to 00:40:05:35:ce:9d via eth0
Sep 18 16:58:27 smeagol mountd[142]: NFS mount of /usr/lib/fai/nfsroot attempted from 192.168.1.10 
Sep 18 16:58:27 smeagol mountd[142]: /usr/lib/fai/nfsroot has been mounted by 192.168.1.10 

smeagol:/usr/share/doc/fai# grep -v ^# /etc/dhcpd.conf 
option domain-name "holbytla.org";
option domain-name-servers 192.168.1.1;
option subnet-mask 255.255.255.0;
default-lease-time 600;
max-lease-time 7200;
subnet 192.168.1.0 netmask 255.255.255.0 {
  range 192.168.1.10 192.168.1.253;
  option broadcast-address 192.168.1.255;
  option routers 192.168.1.1;
}

I'll try giving BOOTP a go now, but I really do prefer DHCP where possible.
Any ideas on this one?

--                                                              
Niall Young						
             Linux Solutions -- www.linuxsolutions.net.au
     Providing Internet and Audio/Video Solutions and Consulting
 PH: 0407 421 537 -- PO BOX 1117, Gwelup WA 6018 -- GPG ID: 8B3AE631