[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] k12ltsp as next-server



Johan,
Hopefully, the following is correct and helpful. 

Have you set the correct option-path for the kernel in dhcpd.conf?

It will probably look like this for you, if *.66.150 is where the ltsp
kernels are

 option root-path "192.168.66.150:/opt/ltsp/i386"; 
or if you are using nbd
option root-path "nbd:192.168.66.150:2000:squashfs:ro";

filename "/ltsp/i386/pxelinux.0"; only is for the pxe image. From there,
it needs to find its full kernel to finish booting

also, you will have to edit 
/opt/ltsp/i386/usr/sbin/ltsp-client-launch
if you want your clients to connect to *.66.150 or anything other than
the default ip from install for the ldm session.
look for the server variable on line 46.

Regards,
William

> Message: 1
> Date: Mon, 30 Jan 2012 19:29:35 +0100
> From: Johan Vermeulen <jvermeulen cawdekempen be>
> To: "Support list for open source software in schools."
> 	<k12osn redhat com>
> Subject: [K12OSN] k12ltsp as next-server
> Message-ID: <4F26E18F 4070907 cawdekempen be>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
> 
> dear All,
> 
> I'm trying to set up a K12Ltsp server on Centos6.2 as next-server behind 
> an OpenSuse11.1 Kiwi-ltsp server.
> So everybody on this site boots from the Kiwi-ltsp machine, but I want 
> to put some users on the newer CentOs-server.
> 
> 
> So in /etc/dhcpd.conf on the Kiwi-ltsp machine it says:
> 
> *group {
> next-server 192.168.66.150;
> filename "/ltsp/i386/pxelinux.0";
> 
> host testtc {
> hardware ethernet 00:22:64:29:a9:4e;
> fixed-address 192.168.66.156;
> }
> }*
> 
> next-server being the K12ltsp machine.
> host testtc, the test thinclient, is a Hp thinclient attached to the 
> Kiwi-ltsp machine.
> 
> The K12ltsp setup on the Centos6.2 machine is completely new installed 
> and exactly like it's explained on the site.
> So firewall is off.
> 
> The thinclient gets an dhcp address and begins booting, then halfway 
> down stalls with this EM:
> 
> *Dracut: Warning: Boot has failed. To debug this issue add "rdshell" to 
> the kernel
> command line.
> Dracut Warning : Signal caught.
> 
> Kernel Panic -not syncing : attempted to kill init!
> id:1, comm: init Tainted :6 
> --------------------------------------------#2.6.32-131.6.1el6.i6
> 6.thinclient s1
> 
> *If I want to add "rdshell", where would I put it?
> 
> Could this be a simple permission problem --- the Kiwi-Ltsp machine 
> boots with the pxelinux.0 from the CentOs machine
> if I understand it correctly -.
> 
> Or could the 2 systems be incompatible?
> 
> Thanks for any advise on this.
> 
> greetings, J.
> *
> *
> 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]