Rob Owens wrote:
> Anselm Martin Hoffmeister wrote:
>
>> Am Dienstag, den 21.08.2007, 10:48 -0400 schrieb Rob Owens:
>>
>>
>>> I'm currently running LTSP 4.2, but would like to test version 5.0. Is
>>> there a convenient way to do this with both servers on the same network?
>>>
>>> My current setup is Xubuntu 6.10 running LTSP 4.2, with Debian Etch
>>> handling DHCP (next-server points to the Xubuntu machine). I'd like to
>>> enable LTSP 5.0 on the Debian system while keeping my regular users on
>>> 4.2. Is there a way I can choose which system to boot from?
>>>
>>>
>> Sure. The easiest way in my opionion would be setting up DHCP right (on
>> the old box), which would also allow you to migrate stations one-by-one
>> once your turnover point is reached.
>>
>> Setup would be as follows: Both machines run a full LTSP setup,
>> including all the daemons (NFS, LDM, TFTP, you name it), but only the
>> old machine runs DHCP-server. This way the old setup needs no changes,
>> except for the pointers that allow select boxes to boot off the new
>> server.
>>
>> In your dhcpd.conf, you probably have a "range" statement assigning IPs
>> from a pool to the thin clients in your network.
>> Just add a "host stanza" for the one machine that you want to boot off
>> the new server:
>>
>> host testltsp5 {
>> hardware ethernet 00:c0:1d:c0:ff:ee;
>> fixed-address 192.168.55.191;
>> root-path "192.168.55.66:/opt/ltsp";
>> next-server 192.168.55.66;
>> filename "/lts/ltsp5-kernel-whatever";
>> }
>>
>> where of course the 192.168.55.66 and .191 have to be replaced by the
>> new server's IP address and a free IP address you want to assign to that
>> client, respectively. 00:c0:1d:c0:ff:ee also wants to be replaced - by
>> the MAC address of your terminal. Don't forget to restart the DHCP
>> server.
>>
>> It seems you have some experience on (K12)LTSP setups, so this is
>> probably not completely new to you. Ask back if you have trouble with
>> this approach.
>>
> Well I'm getting somewhere. My client started to boot, but reboots
> itself before I get to X. The messages go by really fast, but the last
> line I saw had the word "initrd" in it. I'll check the server logs
> tonight to see if I can get any clues. It does appear to be booting off
> of my LTSP 5.0 server, because I saw the IP address of that server flash by.
>
> -Rob
>
I got it to work. Here's the stanza I included for my LTSP 5 client,
booting off a Debian Etch system.
# LTSP 5.0 test host:
host stinky {
hardware ethernet 00:40:F4:BE:E1:A9;
fixed-address 192.168.2.153;
filename "/ltsp/i386/nbi.img";
next-server 192.168.2.251;
option root-path "/opt/ltsp/i386";
}
Note that at first I had set: option root-path
"192.168.2.251:/opt/ltsp/i386"; but that didn't work (even though it
works in LTSP 4.2). I found suggestions on the internet that this is a
bug in Debian.
-Rob
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.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
