I have used Mozilla Kiosk (also works with Phoenix) quite successfully....
http://kiosk.mozdev.org/
I use autologin with gdm using a little autologin.sh in /usr/bin
The kiosk is completely locked down.
Rgds
Malcolm
Ragnar Wisloff wrote:
Rod wrote:
Greetings,
New to the list so forgive my ignorance. I've been surfing the web and
searching the archives but still have some questions as to whether ltsp
is what I should be using or attempting something from scratch.
I'm interested in setting up diskless nodes in a library setting for
searching the libary catalog web server. The existing implementation is
based on locked down Windows 95 boxes but these will be upgraded to
something else soon. The current thinking is either a commercial thin
client solution or Windows 2000, both of which may be overkill
technically and/or financially.
Here's what I am looking for. I've seen many of the relevant howto's
and postings but nothing that quite fits (or I understand to fit).
Autologin: either single user mode or based on nodename
Browser Autolaunch: Netscape or /Mozilla
Reasonably secure/stable locked down environment that just requires a
reboot to get back to. No current requirement for saving session.
As much as possible running locally on the diskless node: After the
network boot, Browser running locally, window manager, etc.
A light window manager: FVWM? IceWM? ??? that supports autologin.
I've just implemented jsyuta bout all of this, the exception is that
it is a true LTSP thin client with nothing running locally. This is by
design, I don't want anything to run locally.
I've used kdm's features, using the ability to autologin named
workstations and starting nothing but a browser using the Startup
parameter in kdmrc. The browser I've used is Opera 6.11 which supports
a number of kiosk features including filtering of URLs which you want
in order to stop people form browsing your file system. This setup
starts no wm at all, just X and the browser is running. I toyed with
disabling Alt_ctrl_backspace, but found some annoying side effects and
used the Restart parameter in kdmrc instead to loop back to Opera if
someone uses that key combination. You can fine tune both the command
switches for Opera using whatever script you specify in the Startup
parameter and the other features using the opera6.ini file for each
user (which means terminal). It is easy to implement e.g. a side bar
to make announcements etc.
This works well for my use, but has no timing features.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
