multiple clients requiring different chroots...
David Van Assche
dvanassche at gmail.com
Wed Oct 31 22:09:02 GMT 2007
Ok, So I've tried this... creating 2 chroots (the existing working fglrx
containing one) [/opt/ltsp/i386-ati] and a new one by doing a
ltsp-build-client...
So my dhcpd.conf looks like this now:
host computerlab2 {
hardware ethernet 00:1a:92:28:1c:12;
fixed-address 192.168.0.70;
option host-name "computerlab2";
# filename "/pxelinux.0";
# next-server mayserve;
option root-path "/opt/ltsp/i386-ati";
if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
filename "/ltsp/i386-ati/pxelinux.0";
}
else{
filename "/ltsp/i386-ati/nbi.img";
}
}
It loads the correct rootserver and filename, but then crashes here:
Negotiation: mount: Mounting /rofs on /root/rofs failed: Invalid Argument
I'm not sure about the images created either, for now I just moved the old
image to i386-ati.img. I'm sure I'm doing something wrong, any help is much
appreciated...
David Van Assche
On 10/31/07, David Van Assche <dvanassche at gmail.com> wrote:
>
> Hi,
> I'm trying to get the computers which I had running as workstations to
> join the thin client network, but am having some serious problems due to the
> current clients all being fglrx loading thin clients. Even when I set the
> [default] in lts.conf file to XSERVER=auto, the server refuses to do
> anything but load the fglrx driver. I'm assuming this is because I'm using
> the restricted linux headers, so I guess I need to create another chroot for
> all the other clients. Should I just copy the chroot to a new location, say
> /opt/ltsp/i386-ati and then build a new chroot? Then from the dhcp file, I
> can load one chroot or another depending on the mac address?
>
> There must be a better way...
>
> David Van Assche
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/edubuntu-users/attachments/20071031/ddadefc8/attachment.htm
More information about the edubuntu-users
mailing list