Glenn More <glenn@sonication.net> made this nice patch with the following improvements: 1. System logger- it can be kind of obtuse to find out how to get remote connections to work. I'd suggest just putting in how to make the various common loggers work. I use sysklogd, and all I needed to do was add "-r" in /etc/conf.d/sysklogd to the SYSLOGD line, so that it read: SYSLOGD="-m 0 -r". I don't know how syslog-ng works, which seems to be what the Gentoo docs suggest these days. 2. TFTP. Bah. This took a bit of troubleshooting. First, the file /etc/xinetd.d/tftp isn't created during the emerge process, and finding the correct example took a bit. I think it would be worth it to add it to the how-to: /etc/xinetd.d/tftp: service tftp { disable = no socket_type = dgram protocol = udp wait = yes user = root server = /usr/sbin/in.tftpd } Next, the user needs edit the file /etc/conf.d/in.tftpd to change the two options within as follows: /etc/conf.d/in.tftpd: INTFTPD_PATH="/tftpboot" INTFTPD_OPTS="${INTFTPD_PATH}" However, it still doesn't work until the user comments out the "only_from = localhost" line from /etc/xinetd.conf. Then they can start xinetd and tftpd will work. 3. DHCP. Your example works fine, except that it would be really handy if you went through and changed all of the "//"-prefaced comments to "##", so that if the user copies & pastes the config file, it works fine (once they've changed the values, of course). If the silly user (ahem) forgets to remove the slashes, dhcpd fails to start, but doesn't return an error (besides not saying "OK" when you do an /etc/init.d/dhcp start"), leading to needless troubleshooting. 4. lts.conf. I agree that you shouldn't include every detail of doing this file, but sadly LTSP.org's docs aren't that great. A couple quick pointers can have most people up & running right away. First, they need to copy /opt/ltsp/i386/etc/lts.conf.example to lts.conf, and edit that as needed. The first thing to do is change "SCREEN_01" to "SCREEN_01 = startx", as the other display manager scripts don't seem to work right. A second good tip is, to get a USB mouse working on the client, add the following lines, and change the mouse protocol and mouse device as shown: MODULE_01 = usb-uhci MODULE_02 = mousedev MODULE_03 = usbmouse X_MOUSE_PROTOCOL = "IMPS/2" X_MOUSE_DEVICE = "/dev/input/mice" 5. Display manager. Fine, except maybe a quick aside that just restarting X doesn't restart kdm :) Yep, I also spent 20m trying to figure out why it wasn't accepting remote connections.
Created attachment 27392 [details, diff] lts.xml.diff
Committed in CVS. Thanks!
