Hi Tom > > $ grep filename /etc/dhcpd.conf > filename "/lts/vmlinuz-2.4.19-ltsp-1";
YES > 2. Verify the file size, permissions and checksum. It > should be readable by everybody and its subdirectories > should have read and execute access for everybody: > > $ ls -l /tftpboot/lts/vmlinuz-2.4.19-ltsp-1 > -rw-r--r-- 1 root root 1418240 Sep 4 22:59 > /tftpboot/lts/vmlinuz-2.4.19-ltsp-1 I get this: -rwxr-xr-x 1 root root 1418240 jan 19 22:13 /tftpboot/lts/vmlinuz-2.4.19-ltsp-1 > $ sum /tftpboot/lts/vmlinuz-2.4.19-ltsp-1 > 40086 1385 YES > $ ls -dl /tftpboot/lts > drwxr-xr-x 3 root root 4096 Oct 25 03:14 /tftpboot/lts I get this drwxr-xr-x 2 root root 1024 jan 19 23:27 /tftpboot/lts > $ ls -dl /tftpboot > drwxr-xr-x 4 root root 4096 Jan 12 16:59 /tftpboot I get this: drwxr-xr-x 4 root root 1024 sep 5 05:59 /tftpboot > 3. From a client, use "tftp" to retrieve the file > from the server (192.168.1.128 in my case): > > $ tftp 192.168.1.128 > tftp> bin > tftp> get /lts/vmlinuz-2.4.19-ltsp-1 > Received 1418240 bytes in 0.1 seconds > tftp> quit YES > 4. Verify the image checksum with the file on the > server (step 2). Note that I am using the same kernel > you are, so your checksums should match mine: > > $ sum vmlinuz-2.4.19-ltsp-1 > 40086 1385 YES > If this much is working, the kernel should boot like so: NO > > Loading 192.168.1.128:/lts/vmlinuz-2.4.19-ltsp-1 ..(NBI) ... .. So fare, but then it stops .......... ??? > If this isn't happening, something must be wrong with the > kernel image. Ho do I get a new one then? /Tue ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _____________________________________________________________________ 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
