LTSP/ThinClient report

Fabio Massimo Di Nitto fabbione at ubuntu.com
Thu Aug 25 01:41:18 CDT 2005


Hi Matt,

Server installation based on breezy-install from 24-08-2004 and upgraded at 25-08-2005 (around 6 am
UTC) with 2 nics, one connected to internet and one to serve the ltsp vlan.

Following the instruction on https://wiki.ubuntu.com/ThinClientHowto step by step:

- installed ltsp-server-standalone [OK]
- ltsp-build-client run [OK]
  * note that you added several option like --mirror and the possibility to use
    /etc/ltsp/ltsp-build-client.conf while the wiki page still reports hardencoded values.
  I think it would be more useful to "hardcode" the values in the config file and ship it as such.
  Just to avoid to trash the changes on an upgrade (for people that will edit ltsp-build-client
  directly)
- ssh keys were ok.
- ltsp fails to configure tftp properly. The path to the images is correct, but
  #Defaults for tftpd-hpa
  RUN_DAEMON="no"
  will make the tftp not to start and clearly the clients cannot boot. Given that we start different
  services, this one should start too automatically.
- Given that the installer doesn't setup the secondary interface, i had to do this manually and
  i wished 2 thing:
  root at cerberus:/etc/network # cat options
  ip_forward=no
  set to yes.
  (or at least document that forwarding is not enabled)
  and like we discussed on IRC that NAT rules where in place and this is something we need to work
  out.
  Of course the network setup is the most complex one across all the others, but clearly we need to
  see if we can automate it more.

Booting the client:

- Other than the problem described in http://bugzilla.ubuntu.com/show_bug.cgi?id=12942
  that i can sometimes workaround leaveing eth1 in promisc mode, the client boots and work
  as expected.

So other than few minor details, this stuff is really cool and works great!

Congratulation Matt!

Fabio

-- 
I'm going to make him an offer he can't refuse.



More information about the ubuntu-devel mailing list