> Date: Sat, 24 May 2008 08:48:28 +0800 > From: jam <[EMAIL PROTECTED]> > Subject: Re: [Ltsp-discuss] ltsp ubunty hardy, different tftp, ltsp > and dhcp server > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > On Saturday 24 May 2008 03:07:19 [EMAIL PROTECTED] > wrote: >> Hello, >> >> I'm new to ltsp and have a default setup working. ?Now I would like to >> try to integrate into our network. >> >> That means: >> - an already existing seperate dhcp server >> - an already existing seperate tftp server >> - a new ltsp server >> >> I can configure (for now) that when my client does a pxe boot it gets >> the correct tftp server: >> >> host linutop.UGent.be { fixed-address 157.193.39.120; hardware ethernet >> 00:40:ca:a2:9f:91; next-server wopr; filename "pxelinux.0"; } >> >> wopr is the tftp server >> >> My pxe config file has: >> wopr:/srv/tftp/fai/pxelinux.cfg# cat 9DC12778 >> DEFAULT linutop ro initrd=linutop.img quiet splash >> >> >> When I pxe boot the client it finds the linutop kernel and linutop.img >> file. ?But then I fail into the busybox shell. >> >> I clearly haven't configured where he needs to get his root file system. >> ? From the ltsp server. >> >> How do I this? ?I thought I should be able to do that from the >> pxelinux.cf directory. > > Hardy does not use root file path. It uses nbd and a squash image. > EG tigger (254) is dhcp server > ------------------------------------ > from /etc/dhcp3/dhcpd.conf > ------------------------------------ > ddns-update-style ad-hoc; > > option subnet-mask 255.255.255.0; > option broadcast-address 192.168.5.255; > option routers 192.168.5.1; > option domain-name-servers 192.168.5.254; > option domain-name "home"; # You really should fix this > option option-128 code 128 = string; > option option-129 code 129 = text; > > get-lease-hostnames true; > > #next-server 192.168.5.254; > next-server 192.168.5.120; > > subnet 192.168.5.0 netmask 255.255.255.0 { > range 192.168.5.121 192.168.5.125; > filename "/ltsp/i386/pxelinux.0"; > } > ... > ----------------------------------- > eeyore (120) is tftp server > ----------------------------------- > from /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default > default vmlinuz ro initrd=initrd.img quiet splash > > eeyore must run nbd and have > /opt/ltsp/images/i386.img
Thank you! This put me on the right track. It's a pitty that you need to have the nbd running on the tftp server. -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Rudy Gevaert [EMAIL PROTECTED] tel:+32 9 264 4734 Directie ICT, afd. Infrastructuur ICT Department, Infrastructure office Groep Systemen Systems group Universiteit Gent Ghent University Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
