Re: New configuration subsystem for LTSP

So the daemon will be a SimpleHTTPServer, listening on port 8080, and
the client will be able to use e.g. wget from the initramfs to get its
configuration, right? If so, I like that part, even though the sysadmin
will need to learn python and to write a plugin to state "if client ram
> 500, make it a fat client". Maybe rules-based configuration files and
an editor for them can be added later.

My main concern is, since many many thin clients here have only 64 Mb or
128 Mb RAM, and python with just `import xmlrpclib` adds about 9 MB
overhead (no jetpipe or anything else running, no RAM for it), could you
leave the ltsp-cluster-agent-thinclient optional? I.e. if it's
available / enabled, use it, else just use wget?

Or in that case it will fallback to tftp and lose all the plugin
functionality on the server?


------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_____________________________________________________________________
Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help,   try #ltsp channel on irc.freenode.net