Whoops, I knew I'd forget something. I also needed to create an lts.conf file
and put it in /opt/ltsp-4.2/i386/etc
Here's the minimum that needs to be included in that file:
[Default]
SERVER = 192.168.2.251
XSERVER = auto
SCREEN_01 = startx
-Rob
On Fri, Jan 25, 2008 at 02:28:32PM -0500, Rob Owens wrote:
> Just reporting on my success...
>
> After using LTSP 4.2 for a few years, I tried out LTSP 5 at home and found
> that it didn't work properly with some of my old Pentium 2 thin clients. So
> I downloaded LTSP 4.2 from
> http://wiki.ltsp.org/twiki/bin/view/Ltsp/DownLoads#Ltsp_4_2 and re-installed
> it on the same machine which is running LTSP 5.
>
> I'm using Debian. I needed to install LTSP 4.2 from source, though, because
> the deb on the above page conflicted with ltsp-server (the LTSP 5 package).
> Installing from source works fine, though, and I don't have any conflicts
> that I'm aware of.
>
> Next I ran ltspadmin and instructed it to put the client tree in
> /opt/ltsp-4.2 (LTSP5 on my system uses /opt/ltsp). Then I installed all the
> packages. This is the part where it downloads all the files to populate
> /opt/ltsp-4.2.
>
> I did not "Configure LTSP" using ltspadmin. I configured by hand:
>
> 1) I added this to /etc/exports:
> /opt/ltsp-4.2 192.168.2.0/255.255.255.0(ro,no_root_squash,async)
>
> 2) I enabled XDMCP using gdmsetup. On the "Remote" tab I chose "Same as
> Local". I also notice what might be a bug here. In order for this option to
> "stick", I needed to click on another tab before hitting "Close".
>
> 3) ltspadmin puts all the kernel files in /tftpboot. LTSP 5, however, keeps
> its kernel files in /var/lib/tftpboot/ltsp/i386. Per my LTSP 5 installation,
> /var/lib/tftpboot is defined as my tftp directory in /etc/inetd.conf, so...
>
> 3a) I created /var/lib/tftpboot/ltsp-4.2
> 3b) I moved everything from /tftpboot into /var/lib/tftpboot/ltsp-4.2
>
> 4) Next I specified the MAC addresses of my LTSP 4.2 clients in my
> dhcpd.conf file. I created a group for them, like this:
>
> group LTSP-4-2-THIN-CLIENTS {
> use-host-decl-names on;
> option log-servers 192.168.2.251; #not sure if this is needed
> option root-path "192.168.2.251://opt/ltsp-4.2/i386";
> filename "/ltsp-4.2/vmlinuz-2.6.20.9-ltsp-1";
>
> host apple {
> hardware ethernet 00:50:04:7C:DD:54;
> fixed-address 192.168.2.154;
> }
> host orange {
> hardware ethernet 00:40:F4:BE:E3:24;
> fixed-address 192.168.2.155;
> }
>
> }
>
> 5) Next I added my LTSP 4.2 clients to /etc/hosts:
> 192.168.2.154 apple.owens.net apple
> 192.168.2.155 orange.owens.net orange
>
> Unless I'm forgetting something, that's all there is to it. Just make sure
> you adjust for your network.
>
> I think this is a good way forward (for me at least). It allows me to use
> LTSP 5, which is obviously the way of the future. It also allows me to keep
> the functionality of my old LTSP 4.2 system--functionality that has so far
> not been ironed out completely in LTSP 5.
>
> -Rob
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _____________________________________________________________________
> 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
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_____________________________________________________________________
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
