Diskless Workstation Boot - kernel.diskless can't parse file...

[K Anderson]

Bigbrother wrote:
> 
> 
> 
>>-----Original Message-----
>>From: K Anderson [mailto:freebsduser at attbi.com] 
>>Sent: Tuesday, April 22, 2003 03:35
>>To: nkinkade at fastmail.fm
>>Cc: FreeBSD Questions
>>Subject: Re: Diskless Workstation Boot - kernel.diskless 
>>can't parse file...
>>
>>
>>
>>
>>Nathan Kinkade wrote:
>>
>>>On Mon, Apr 21, 2003 at 02:12:05PM -0700, K Anderson wrote:
>>>
>>>
>>>>Greetings,
>>>>
>>>>I'm interested in checking out the diskless workstation 
>>>
>>stuff but I am 
>>
>>>>finding the documentation sorely lacking.
>>>>
>>>>I have the dhcp server configured but I am at a point where the 
>>>>etherboot floppy connects, gets the assigned IP address and other 
>>>>information then gets stuck with the following error
>>>>
>>>>Loading 192.168.100.105:kernel.diskless can't parse file name 
>>>>kernel.diskless
>>>>
>>>>I think it might have to do with the tag kernel but the 
>>>
>>command to make 
>>
>>>>the tagged kernel doesn't exist.
>>>>
>>>>So I'm looking for someone to lead me to the holly grail of 
>>>
>>diskless 
>>
>>>>workstations so I can check it out.
>>>>
>>>>Really good instructions are greatly appreciated.
>>>>
>>>>I'm using Etherboot 5.0.8 from ports.
>>>
>>>
>>>First, FreeBSD does not need a tagged kernel like Linux, so 
>>
>>do not tag
>>
>>>or attempt to tag the kernel.  What sort of path do you have to
>>>kernel.diskless in your dhcpd.conf file?  Are you using nfs or tftp?
>>>I've got a diskless terminal going here with 4.8.  I used 
>>
>>nfs across the
>>
>>>board so that I don't have to enable tftpd, and thence inetd.  Here
>>>would be some useful information for me to know:
>>>1) your dhcpd.conf file
>>>2) options you selected when building your etherboot image
>>>3) nfs or tftpd
>>>
>>>I may not be able to help, even with these, but possibly I'll see
>>>something??
>>>
>>>Nathan
>>
>>Ok, no tagged kernel. :) Thanks. Oh, I'm using a laptop, it has boot 
>>from NIC and it works, but the problem with that is it says img is to 
>>large for low memory. So that's why I went to etherboot.
>>
>>1) here's the dhcp.conf lines (etherboot reports getting an IP):
>>host bailey {
>>  hardware ethernet 00:0b:db:13:90:ab;
>>  fixed-address 192.168.100.200;
>>  next-server 192.168.100.105;
>>  filename "kernel.diskless";
>>  option root-path "192.168.100.105:/diskless_root";
>>}
>>
>>
>>2) Options for etherboot? I just typed make in 
>>/usr/ports/net/etherboot 
>>without any options.
>>
>>3) I used tftpd to get the kernel. tftpd is /tftpboot
>>This I finally figured out when I kept getting file not found errors. 
>>hehehe. So I just tftp'd to the localhost and doh! it was right, file 
>>wasn't found. I had the wrong path all over the place.
>>
>>NETBOOT kernel is
>><...>
> 
> 
> 
> 
> On my server for the diskless I have
> 
> inetd.conf:
> <..>
> tftp    dgram   udp     wait    root    /usr/libexec/tftpd      tftpd -s
> /tftpboot
> <..>
> 
> 
> dhcpd.conf:
> <..>
> filename "/tftpboot/kernel";
> <..>
> 
> 
> exports:
> <..>
> /    -ro -alldirs -maproot=root: -network 192.168.168.0 -mask
> 255.255.255.0
> <..>
> 
> 
> Make sure that you also have along your lines, the previous lines!
> 
> Regardz,
> 
> BB
>  
> 
> 
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
> 

Hmm, thanks for your response I managed to get a little further.
1) Kernel is loading and booting.
2) DHCP got root path - rootfs 192.168.100.105:/diskless_boot hostname 
bailey
3) Adjusted interface xl0
4) Shutdown interface faith0
5) panic: nfs_boot: mountd root, error=72
   (how about meaningfull error messages like..you dummy create something)