Re: Thin clients
Fred Zinsli wrote:
> Well I have been working on this for days now and I can't seem to get past
> an error from the client saying pxelinuz.0 isn't a valid image.
you need syslinux or a like package there you'll find pxelinux.0. read
below
>
> At the fedup and grumpy stage now, but don't want to let it beat me.
>
> I have googled and tried about everything I could find to get this to
> work. So if anyone has a working howto for etch on this subject I would
> like to get a copy.
>
> I just don't have enough knowledge about linux so I do need to be spoon
> feed.
>
First of all don't top post - it makes mail threads less readable.
then read about tftp vs. aftp daemons and decide which you would like to do.
I usually look first for howtos at http://tldp.org/
http://tldp.org/HOWTO/NFS-Root.html
http://tldp.org/HOWTO/NFS-Root-Client-mini-HOWTO/index.html
http://tldp.org/HOWTO/Diskless-root-NFS-HOWTO.html
then figure out if your network card supports pxe boot or bootp. you have to
configure the bios of the card to boot from the server.
read more here http://www.etherboot.org/wiki/howtos
if it's not the case there is a way using bios patches for the card.
http://www.etherboot.org/wiki/romburning
I never did it so I can not help here. I did it with a usb stick where I
wrote an gpxe image which was working fine.
I then found out that I can boot from the usb drive with grub or lilo and
pass nfs-root parameter to the kernel. Together with the network card
module and nfs-client compiled in, the kernel can download and boot from a
root on nfs all it needs even an initrd.
It all depends on the device and it's charactereistics
(memory/disk?/cpu/etc).
regards
PS:
here is what I have configured for an intel 686 and geode 586 cpus. Files
and places depend on configuration
cd /opt/remote/
ls
nfsroot tftpboot
find .
tftpboot/
tftpboot/pxelinux.cfg
tftpboot/pxelinux.cfg/01-02-03-00-00-00-00
tftpboot/pxelinux.cfg/0-default
tftpboot/pxelinux.cfg/01-02-03-00-00-00-01
tftpboot/pxelinux.cfg/01-02-03-00-00-00-02
tftpboot/bootmenu.txt
tftpboot/i586
tftpboot/i586/initrd.gz
tftpboot/i586/config
tftpboot/i586/System.map
tftpboot/i586/vmlinuz
tftpboot/isolinux.bin
tftpboot/i686
tftpboot/i686/boot.cat
tftpboot/i686/boot.txt
tftpboot/i686/f10.txt
tftpboot/i686/f1.txt
tftpboot/i686/f2.txt
tftpboot/i686/f3.txt
tftpboot/i686/f4.txt
tftpboot/i686/f5.txt
tftpboot/i686/f6.txt
tftpboot/i686/f7.txt
tftpboot/i686/f8.txt
tftpboot/i686/f9.txt
tftpboot/i686/isolinux.bin
tftpboot/i686/isolinux.cfg
tftpboot/i686/splash.rle
tftpboot/i686/initrd.gz
tftpboot/i686/vmlinuz
tftpboot/isolinux.cfg
tftpboot/ldlinux.sys
tftpboot/pxelinux.0
tftpboot/pxelinux.0-atftp+tsize
tftpboot/pxelinux.0-tftp-tsize
cat /etc/inetd.conf | grep -A2 ftp
#:BOOT: Tftp service is provided primarily for booting. Most sites
# run this only on machines acting as "boot servers."
tftp dgram udp wait
nobody /usr/sbin/tcpd /usr/sbin/in.tftpd /opt/remote/tftpboot
#bootps dgram udp wait root /usr/sbin/tcpd
bootpd -i -t 120
and dhcpd.conf which I posted before
Reply to: