Hurro.. Sounds neat.
I've only worked with the straight ltsp install on RH7.2, but I'm going to assume it's pretty much the same. for 1. Just turn it off. for 2. Ummm, syslogd should be running with the -r (?) parameter I think it was, and that allows remotes to log to it, and then you have the syslog entry in the lts.conf or dhcpd.conf (I've not got a box running here with it installed, so I'm flying from memory). The kernel messages then wind up in /var/log/somewhere. I think by default they wound up mixed in messages with the server ones. I'll have a look tonight and see where mine wind up, as I know I've read it somewhere to solve a video card problem I had with one thin machine. As for sound on the terminals, I've only tried it once, and it just worked, sort of.. I just followed the instructions at: http://www.ltsp.org/ltsp_sound_docs.txt And it worked, although some apps still produced sound on the server instead of the workstation end. One MP3 player I tried, for example. The GUI was on the workstation saying 'playing' etc, but the sound was coming out of the server. The machine I was using was a P133, 24Mb of ram, PCI soundblaster Live 128, and 10Mb NIC, S3 video. My plan was for an MP3 jukebox with no drive noise, but I've still not found a decent MP3 jukebox for Linux that can replace MusicMatch feature for feature. (or the three or four features I want.) Cheers, Chris Hellyar. -----Original Message----- From: Nick Rout [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 11 June 2002 9:36 a.m. To: CLUG Subject: Linux Terminal Server I got the k12 Linux Terminal Server going last night. It is basiaclly a Redhat 7.3 system, with the Linux Terminal Server Project isos added and some educational software plus open office. (K12 is the US abbreviation for school - Kindergarten to year 12). I had it running over a 10M network with a athlon 1133 w/256M memory as a server and a p166 w/32 M RAM as a terminal. The terminal boots from a floppy (just to load a bootp/dhcp client, it hen loads its kernel over the network - very fast). The disk drives on the terminal are not used at all, in fact you could do away with the floppy too if you had bootable ethernet cards. It goes quite nicely, but I would recommend a 100M network with a switch (rather than hub) to use it seriously. The price of 100M cards is fairly minimal these days, although the desiarbility of a pci slot for the 100M card does mean you cannot go too retro on hardware. This would be a good setup for a school with (say) a set of aging p200's. Buy a server, some 100M cards and a switch and your hardware gets a few more good years. I know a couple of other people have had similar setups going and I have a couple of questions: 1. how do you turn the terminal off or restart it, other than exiting the window manager and hitting the power/reset switch. Ordering a reboot from the login screen reboots the server (oops) (does require root password) 2. is it possible to get a dmesg display for the _terminal_ as I am trying to get sound going on the terminal and want to debug the startup messages. Typing dmesg in an xterm gives the dmesg for the _server_. -- Nick Rout <[EMAIL PROTECTED]> ###################################################################### The contents of this e-mail message may be privileged and/or confidential. If you are not the intended recipient please delete the message and notify the sender. Any views or opinions presented are solely those of the author, and do not necessarily represent the official position of the Selwyn District Council ######################################################################
