>I'm running an LTSP server on a Debian 2.2 machine. When I boot a client out
>of an etherboot floppy, it gets it's correct IP address from the DHCP server,
>but then the tftp kernel download fails with the following error message:
>
>Me: 192.168.0.2, Server: 192.168.0.1, Gateway: 192.168.0.1
>Loading 192.168.0.1:/lts/vmlinuz-2.4.9-ltsp-5 TFTP error 2 (Access violation)
>Unable to load file
>
>On the server's log file (/var/log/syslog) I only find this:
>
>Mar 24 14:28:48 claritas in.tftpd[491]: connect from 192.168.0.2
>Mar 24 14:28:48 claritas tftpd[492]: tftpd: trying to get file: /lts/vmlinuz-
>2.4.9-ltsp-5
>
>[root@claritas ~]# cat /etc/dhcpd.conf
>
>...
>
>group {
> use-host-decl-names on;
> option log-servers 192.168.0.1;
>
> host obscuritas {
> hardware ethernet 00:50:04:2C:A4:A8;
> filename "/lts/vmlinuz-2.4.9-ltsp-5";
> fixed-address 192.168.0.2;
> server-name "claritas.localdomain";
> }
You asked for /lts/vmlinuz-2.4.9-ltsp-5. This is an absolute path.
However in inetd.conf, you told tftpd that only pathnames from /tftpboot
may be served. So tftpd said you couldn't have it.
Try changing that to /tftpboot/lts/vmlinuz-2.4.9-ltsp-5
There's always confusion over tftp pathnames because there are two major
schools of behaviour depending on which tftpd you have. (1) The tftpd
does a chroot (real or virtual) to the directory specified in the tftpd
command line. Then all pathnames are relative to this root. (2) The
directory parameter on the tftpd command line specifies the legal
directory and the pathname requested must start with it. The behaviour
to relative paths may or may not be determinate. You were expecting (1)
but you got (2).
_____________________________________________________________________
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.openprojects.net
