X_CONF=/etc/X11/xorg.conf.multiseat
in your lts.conf file (located in
/var/lib/tftpboot/ltsp/amd64/lts.conf if you are booting a 64-bit
chroot. Also, don't forget a section header, such as [default] if this
is a new file)
-Gadi
On Wed, Aug 18, 2010 at 2:26 PM, Marco Müller wrote:
>
> Hello,
>
Hello,
I built in a hdd and installed Ubuntu locally on the client. Than created a
working! multiseat xorg.conf (got 2 kdm login screens can login/logout)
I copied this xorg.conf into /opt/ltsp/amd64/etc/X11/xorg.conf.multiseat and
sudo ltsp-update-image
What would be the next step?
server: kubu
This precedence find is spot-on. Thank you!
While it is obvious that nothing was every really 'broken' and no
functionality changed with an update - (what changed was my
hosts.allow), I am glad that we went through this rigmarole. I hope it
will help future generations of LTSP users.
Cheers Alkis
Le vendredi 13 août 2010 08:47:31, Krzysztof Paliga a écrit :
> One of our servers is acting strange since yesterday.
> Thin Clients trying to boot using it give an initramfs error, whit
> following output on screen 1:
> ...
> filename : /ltsp/i386/pxelinux.0
> Negotiation: Error: INIT_PASSWD bad
>
Distro/version?
E.g. in Ubuntu Lucid I think it's handled by "/etc/init.d/ondemand",
which is provided by the "initscripts" package, which should be
preinstalled on the chroot.
The main thing this script does is:
for CPUFREQ in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
do
[ -f $CPUF
One of the reasons I use LTSP is to reduce power consumption on my
clients. I have discovered that a machine I run normally as a thick
client will use CPU scaling so the majority of the time the machine is
running at 800 MHz despite having a 2.6 GHz processor. If I boot this
machine as an LTSP cl
