[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: thin-client options for sarge

Hash: SHA1

Finn-Arne Johansen wrote:
many of the bugs for lessdisks don't appear to be present in
the newer upstream versions(see links below).

And they will work without problem with sarge, and if so, what is
stopping them from entering sarge ?

yes, they do.

* Lessdisks supports both SSH-tunneled XDMCP traffic (the
Debian-packages sdm and sdm-terminal) and the simpler insecure traffic
used by ltsp3 (which requires less CPU on both client and server).

sdm actually uses ssh X11Forwarding instead of XDMCP used by xdm, kdm,
gdm... still more secure, though :)

Is it possible to use both ?

you have the choice for a terminal to come up as one of these.

* Lessdisks ties terminal configuration to MAC address instead of IP

i believe LTSP can be configured to use mac address, hostname or ip
address in recent versions.

Yes, that's the case with LTSP4

it was the case as well with v3.

* Lessdisks by default (when properly implemented - Vagrant claims it
works now) uses plain vanilla default Debian Linux kernels, so
security updates is swift! (hey, I added that part! ;-))

not only kernels, but any package available for debian is available for
lessdisks, generally without modification.

That will be my main goal

it works like Vagrant claimed

it uses debootstrap to create a standard debian read-only root
filesystem for the terminals, with as few modifications as possible.
this is probably it's main strength.

It's not easy to install, and get up running, at least not the packages
in sarge. I'll try to use the ones from sid, and see what the status

lessdisks is just a few realitvely simple shell scripts on top of
debian, really :)

In the close future is also Vagrant working on compatibility for
ltsp-like configuration in order to make it easier to switch

well, i've incorporated and/or re-written some of the ltsp code for use
with lessdisks, mainly x configuration.

i haven't really put much time into converting from an existing ltsp
installation since i'd have to learn LTSP to do it.  though there's at
least one person quite familiar with LTSP that might be able to do
something to that effect.

well, for a setup of LTSP with fixed ip addresses you have to

   - grab hostname and mac address out of dhcpd.conf anp put those
     lines into the file /etc/lessdisks/terminal.config
   - grab the entries out of lts.conf section [hostname]
     and put them in a file called <hostname> in the directory
having done this for e.g. mouse, X settings, the terminal will come up with those values configured like known from LTSP

main weaknesses of lessdisks right now:
* access to local devices (printer, sound, floppy, cdrom, etc)

That should be managable, as long as the solution runs on a thick
client (but as a diskless)

you're right with this


- -- Public Key available at pgp keyservers, e.g. http://pgp.mit.edu
Öffentlicher Schlüssel liegt u.a. auf http://blackhole.pca.dfn.de

Version: GnuPG v1.2.4 (GNU/Linux)


Reply to: