Hi all,

in helping someone to get KDE instead of gnome, I suggested:

On Wed, 21 Feb 2007, Gavin McCullagh wrote:

> If this is true, you may be able to put something like
> 
>       LDM_REMOTECMD=/usr/bin/startkde
> 
> but I really haven't tested this so I'm not sure.  As an initial test, you
> could set:
> 
>       LDM_REMOTECMD=/usr/bin/firefox
> 
> in /opt/ltsp/i386/etc/lts.conf and reboot the thin client.  If when you
> login it goes straight into firefox, this works.  It'd be very useful to
> know if this works so please tell us how you get on.

Oliver gave the proper correct answer which was to use update-alternatives.

However, LDM_REMOTECMD has its uses so I thought I might mention them here
in case people are interested.

Since edgy, a thin client user can choose their session if there is more
than one available using the dropdown box on the login screen.  ldm, which
presents the login screen on the thin clients, makes a request of the
server to find out what sessions are available and populates the session
dropdown box with this info.

Suppose you don't like people having the choice and want to force certain
computers to always use a particular session.  You can record the computers
mac addresses and edit /opt/ltsp/i386/etc/lts.conf 

[00:02:a5:1d:4b:f8]
  LDM_REMOTECMD=/etc/X11/Xsession

[00:02:a5:94:20:ab]
  LDM_REMOTECMD=/usr/bin/startkde

from now on, the pc with the first mac address will always use and Xsession
(which is usually the default session) and the second will always run KDE.
This basically over-rides the session drop-down box.

==Our web kiosks==

In setting up a very basic web kiosk, we have used the following:

  1. use LDM_REMOTECMD to force use of Xsession from kiosk computers
  2. created a "kiosk" user and modified /home/kiosk/.Xsession to contain:

        /usr/bin/firefox -CreateProfile `echo $SSH_CLIENT | cut -d " " -f1`
        exec /usr/bin/firefox -P `echo $SSH_CLIENT | cut -d " " -f1`

  3. Set the Xsession as immutable so the user cannot edit it
        chattr +i /home/kiosk/.Xsession

This means that the kiosk user, logging in on these computers must use
firefox as their session. By contrast, other users will get their usual
xsession (usually gnome).  

[1] prevents them from picking gnome from the dropdown, [2] forces firefox
to be the xsession and creates a firefox profile for each thin client, [3]
stops them modifying the xsession.

Gavin


-- 
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/edubuntu-users

Reply via email to