Black screen when thin client boots

Krsnendu dasa krsnendu108 at gmail.com
Thu Oct 25 16:36:24 BST 2007


> > On Feisty i used I used X_COLOR_DEPTH=16 in /opt/ltsp/i386/etc/lts.conf ...
> >
> > Is this correct place in Feisty?
> yes
>
> > Is there a need to use ltsp-update-image on Feisty?
> there is no image in feisty, so there would be nothing to update :)
> (and in fact that command doesnt exists there)
>
> ltsp-update-image creates a new squashfs image from the contents
> of /opt/ltsp/i386 the image is the actual rootfs so if you make changes
> there and want them in the image (read in the actually running client
> system) you need to update the image contents.
>
> since that gets very annoying to wait for minutes if you only want to
> try out a change of a config value, gutsy has a function in the
> initramfs that checks if lts.conf sits in the tftp root, if thats the
> case it downloads it and copies it over the one in the mounted client
> root before booting.
>
> so if you want to go on in gutsy with using /opt/ltsp/i386/etc/lts.conf
> you are free to do so. it will be used as long as there is no file
> in /var/lib/tftpboot/ltsp/i386/lts.conf

So in Gutsy /var/lib/tftpboot/ltsp/i386/lts.conf is the configuration file not
/opt/ltsp/i386/etc/lts.conf like it is in Feisty?

If so what is the need for /opt/ltsp/i386/etc/lts.conf  and  ltsp-update-image ?
>
> i'm working on some gui tools for hardy that will make all this easier
> and you shouldnt have to care for file locations with it anymore :)

Sounds good.


Krsnendu



More information about the edubuntu-users mailing list