Re: [gentoo-user] tftp config problem (ltsp)
Looked over the directory structure in the tftp directory compared to what was setup in the ltsp directory. Found some differences. Copied over a directory called 2.6.17.80ltsp-1 which contained all the needed files in proper placement to tftp under the same original name. Adjusted some conf files to point where needed and my test laptop started to boot. First problem I ran into here was due to the touch mouse hardware. It caused the boot to hang or panic. I deactivated the touch mouse and the boot restarted and progressed further till another problem. During the boot process was getting error notices about not being able to connect to the nfs server. Did some research and found this sometimes occurs when the speed of the server nic is so much faster then the client nic. Apparently this showed up with the 2.6 kernel. Anyway, some more tweeks and had a successful boot and was greeted by the KDE login screen. Logged in and was greeted by my usual desktop. Setting are still default so will play with them for such things as sound. Decided to order a diskless workstation from http://www.disklessworkstation.com/ They appear to be a supporter of the ltsp project. Also ordered an etherboot model, since that is an open standard. Now when that shows up get to beat on it for a while. Thanks all for the help, Sean -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] tftp config problem (ltsp)
On Fri, 09 Nov 2007 16:09:06 + sean [EMAIL PROTECTED] wrote: Decided to order a diskless workstation from http://www.disklessworkstation.com/ They appear to be a supporter of the ltsp project. why would you do that? Coudn't you build an excellent diskless host for less than they cost? And their specs aren't very impressive... -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] tftp config problem (ltsp)
Dan Farrell wrote: On Fri, 09 Nov 2007 16:09:06 + sean [EMAIL PROTECTED] wrote: Decided to order a diskless workstation from http://www.disklessworkstation.com/ They appear to be a supporter of the ltsp project. why would you do that? Coudn't you build an excellent diskless host for less than they cost? And their specs aren't very impressive... They support the project so I figured one could not hurt. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] tftp config problem (ltsp)
Hi Sean,
sean [EMAIL PROTECTED] writes:
I set up diskless booting recently but I'm by no means an expert, so
take my comments with plenty of salt.
Below is my in.tftpd file.
# /etc/init.d/in.tftpd
# Path to server files from
# Depending on your application you may have to change this.
# This is commented out to force you to look at the file!
#INTFTPD_PATH=/var/tftp/
INTFTPD_PATH=/tftpboot/
What happens with INTFTPD_PATH=/tftpboot? (remove trailing / )
#INTFTPD_PATH=/tftproot/
# For more options, see in.tftpd(8)
# -R 4096:32767 solves problems with ARC firmware, and obsoletes
# the /proc/sys/net/ipv4/ip_local_port_range hack.
# -s causes $INTFTPD_PATH to be the root of the TFTP tree.
# -l is passed by the init script in addition to these options.
#INTFTPD_OPTS=-R 4096:32767 -s ${INTFTPD_PATH}
INTFTPD_OPTS= -s ${INTFTPD_PATH}
The tftp file looks exactly like the one specified in the instructions.
tardis tftpboot # ls
lts pxe pxelinux.cfg
Are you using syslinux? I'm not sure but shouldn't there be a
pxelinux.0 file in /tftpboot?
Cheers,
Roger
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] tftp config problem (ltsp)
Roger Mason wrote: I set up diskless booting recently but I'm by no means an expert, so take my comments with plenty of salt. Sounds like you have had better success than me. INTFTPD_PATH=/tftpboot/ What happens with INTFTPD_PATH=/tftpboot? (remove trailing / ) Since removed. Made no difference. Are you using syslinux? I'm not sure but shouldn't there be a pxelinux.0 file in /tftpboot? I am using what ever was emerged using Gentoo's instructions. I have had a bit more success since last posting, but not full success. Depends on what I put in the dhcpd.conf file for the filename entry. If it specifies filename /pxe/pxelinux.0; it will start the boot but finally halts stating cannot find kernel image: linux. If it specifies filename /lts/vmlinuz-2.6.17.8-ltsp-1; then I get the NBP is to large for memory error. So far no luck getting past either point. Thanks Sean -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] tftp config problem (ltsp)
On Tue, 06 Nov 2007 10:06:30 -0500
sean [EMAIL PROTECTED] wrote:
If it specifies
filename /pxe/pxelinux.0; it will start the boot but finally halts
stating cannot find kernel image: linux.
If it specifies
filename /lts/vmlinuz-2.6.17.8-ltsp-1; then I get the NBP is to
large for memory error.
Sean,
You appear to be missing just a bit of the config. I _think_
this is all the relevant info from my dhcpd.conf:
=
===
=== dhcpd.conf
===
=
#don't actually know what these are for...
option oe-key code 159 =string;
option oe-gateway code 160 = ip-address;
# tftp server:
next-server 192.168.10.1;
option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cportcode 2 = unsigned integer 16;
option PXE.mtftp-sportcode 3 = unsigned integer 16;
option PXE.mtftp-tmoutcode 4 = unsigned integer 8;
option PXE.mtftp-delaycode 5 = unsigned integer 8;
option PXE.discovery-control code 6 = unsigned integer 8;
option PXE.discovery-mcast-addr code 7 = ip-address;
option option-150 code 150 = text ;
zone spore.ath.cx. {
primary 192.168.1.87;
key rndc-key;
}
zone 1.168.192.in-addr.arpa. {
primary 192.168.1.87;
key rndc-key;
}
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.101 192.168.1.199;
option domain-name-servers 192.168.1.87, 192.168.1.1;
option domain-name spore.ath.cx;
ddns-domainname spore.ath.cx;
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.1.255;
one-lease-per-client on;
update-static-leases on;
# diskless client
host davey{
hardware ethernet 00:01:03:20:AE:CF;
fixed-address 192.168.1.1;
option host-name davey;
option routers none;
DDNS-hostname davey;
option PXE.mtftp-ip 192.168.1.87;
filename pxelinux.0;
}
}
=
===
=== in.tftp configuration:
===
=
# /etc/init.d/in.tftpd
# Path to server files from
INTFTPD_PATH=/var/tftp
INTFTPD_USER=nobody
# For more options, see tftpd(8)
#INTFTPD_OPTS=-l -v -s ${INTFTPD_PATH} -a 192.168.10.1
INTFTPD_OPTS=-u ${INTFTPD_USER} -l -vv -p -c -s ${INTFTPD_PATH} -a
192.168.1.87
==
==
== relevant contents of /var/ftp
==
==
/var/tftp/
/var/tftp/pxelinux.0
/var/tftp/pxelinux.cfg/
/var/tftp/pxelinux.cfg/01-00-01-03-20-ae-cf
# you'll notice the config file is named for the mac
# address, prepended by 01-, and with '-' instead of
# ':', with all lower case. you could also use
# 'default', if the same entry could be shared.
/var/tftp/pxelinux.cfg/default
/var/tftp/bzImage.davey
=
==
== 01-00-01-03-20-ae-cf
==
=
DEFAULT /bzImage.davey
APPEND ip=dhcp root=/dev/nfs nfsroot=192.168.1.87:/diskless/davey
=
I think that should help out a lot.
--
[EMAIL PROTECTED] mailing list
[gentoo-user] tftp config problem (ltsp)
I am trying to get LTSP working here.
All appear on the right track with one apparent problem, tftp'ing the file.
When I boot a client it appears to pull in the network information but
when it starts to tftp the file, I receive a message that the file is
not found on the client display.
I have been following the instructions here,
http://www.gentoo.org/doc/en/ltsp.xml
and of course alter to what I need for my system.
Am I missing something obvious or something less so?
Thanks,
Sean
Below is my in.tftpd file.
# /etc/init.d/in.tftpd
# Path to server files from
# Depending on your application you may have to change this.
# This is commented out to force you to look at the file!
#INTFTPD_PATH=/var/tftp/
INTFTPD_PATH=/tftpboot/
#INTFTPD_PATH=/tftproot/
# For more options, see in.tftpd(8)
# -R 4096:32767 solves problems with ARC firmware, and obsoletes
# the /proc/sys/net/ipv4/ip_local_port_range hack.
# -s causes $INTFTPD_PATH to be the root of the TFTP tree.
# -l is passed by the init script in addition to these options.
#INTFTPD_OPTS=-R 4096:32767 -s ${INTFTPD_PATH}
INTFTPD_OPTS= -s ${INTFTPD_PATH}
The tftp file looks exactly like the one specified in the instructions.
Here is my dhcpd.conf file
#General Options
default-lease-time 21600;
max-lease-time 21620;
ddns-update-style ad-hoc;
use-host-decl-names on;
#authoritative;
#Boot Options
allow booting;
allow bootp;
#Network Options
#option subnet-mask 255.255.255.0;
#option broadcast-address 192.168.0.255;
#option domain-name mydomain.net;
#option domain-name-servers 192.168.0.1;
#option log-servers 192.168.0.11;
#option routers 192.168.0.1;
#LTSP Path Options
option root-path192.168.0.11:/opt/ltsp-4.2/i386;
filename /opt/ltsp-4.2/vmlinuz-2.6.17.8-ltsp-1;
#filename /tftboot/lts/ltsp-4.2/vmlinuz-2.6.17.8-ltsp-1;
next-server 192.168.0.11;
shared-network WORKSTATIONS
{
subnet 192.168.0.0 netmask 255.255.255.0
{
range dynamic-bootp 192.168.0.40 192.168.0.50;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option domain-name mydomain.net;
option domain-name-servers 192.168.0.1;
option log-servers 192.168.0.11;
option routers 192.168.0.1;
}
}
ls of the opt/ltsp location
tardis / # cd opt/ltsp-4.2/
tardis ltsp-4.2 # ls
2.6.17.8-ltsp-1 i386 vmlinuz-2.6.17.8-ltsp-1
tardis ltsp-4.2 # pwd
/opt/ltsp-4.2
tardis ltsp-4.2 #
ls of the tftpboot structure
tardis tftpboot # pwd
/tftpboot
tardis tftpboot # ls
lts pxe pxelinux.cfg
tardis tftpboot # cd lts/
tardis lts # ls
vmlinuz-2.6.17.8-ltsp-1
tardis lts # cd ..
tardis tftpboot # cd pxe
tardis pxe # ls
bzImage-2.6.17.8-ltsp-1eb-5.0.9-eepro100.lzpxe initramfs.gz
eb-5.0.9-3c905c-tpo.lzpxe eb-5.0.9-rtl8139.lzpxe pxelinux.0
tardis pxe #
Here is the tail of the message log. If I am rading correctly, it looks
proper and the client is trying to start the tftp session.
Nov 3 18:44:18 tardis dhcpd: DHCPDISCOVER from 00:00:86:43:b9:c0 via eth0
Nov 3 18:44:19 tardis dhcpd: DHCPOFFER on 192.168.0.40 to
00:00:86:43:b9:c0 via eth0
Nov 3 18:44:20 tardis dhcpd: DHCPDISCOVER from 00:00:86:43:b9:c0 via eth0
Nov 3 18:44:20 tardis dhcpd: DHCPOFFER on 192.168.0.40 to
00:00:86:43:b9:c0 via eth0
Nov 3 18:44:24 tardis dhcpd: DHCPDISCOVER from 00:00:86:43:b9:c0 via eth0
Nov 3 18:44:24 tardis dhcpd: DHCPOFFER on 192.168.0.40 to
00:00:86:43:b9:c0 via eth0
Nov 3 18:44:32 tardis dhcpd: DHCPREQUEST for 192.168.0.40
(192.168.0.11) from 00:00:86:43:b9:c0 via eth0
Nov 3 18:44:32 tardis dhcpd: DHCPACK on 192.168.0.40 to
00:00:86:43:b9:c0 via eth0
Nov 3 18:44:32 tardis xinetd[12818]: START: tftp pid=12826
from=192.168.0.40
Here is some info from the message log after starting xinetd.
That file is at default.
Nov 3 19:01:22 tardis xinetd[13084]: Reading included configuration
file: /etc/xinetd.d/chargen-dgram [file=/etc/xinetd.conf] [line=49]
Nov 3 19:01:22 tardis xinetd[13084]: Reading included configuration
file: /etc/xinetd.d/chargen-stream [file=/etc/xinetd.d/chargen-stream]
[line=67]
Nov 3 19:01:22 tardis xinetd[13084]: Reading included configuration
file: /etc/xinetd.d/cups-lpd [file=/etc/xinetd.d/cups-lpd] [line=67]
Nov 3 19:01:22 tardis xinetd[13084]: Reading included configuration
file: /etc/xinetd.d/daytime-dgram [file=/etc/xinetd.d/daytime-dgram]
[line=12]
Nov 3 19:01:22 tardis xinetd[13084]: Reading included configuration
file: /etc/xinetd.d/daytime-stream [file=/etc/xinetd.d/daytime-stream]
[line=67]
Nov 3 19:01:22 tardis xinetd[13084]: Reading included
