Re: LTSP 5.3 will be tagged tomorrow at 19:00 UTC

Michael Shigorin <[email protected]> Thu, 16 Feb 2012 09:40:45 +0200
Newsgroups gmane.linux.terminal-server.devel
Message-ID <[email protected]>
On Wed, Feb 15, 2012 at 02:17:37PM -0500, St?phane Graber wrote:
> >> and move most ltsp-build-client plugins into init scripts running
> >> at boot time on the client.
> > Should have a look, what's the boot time impact like if it got
> > measured already?
> It's mostly removing files and moving some others, so if it takes more
> than a second, I'd be worried (as in, we're doing something wrong).

Erm, wouldn't mv on overlay (rw is overlay, right?) increase
memory consumption?

> The main advantage of this is that you can in theory install the LTSP
> packages on a regular desktop machine and they won't do anything,
> unless you reboot it with init=/sbin/init-ltsp, then it turns into a
> thin client but without actually touching anything on the disk.
> The goal for Ubuntu 12.10 is to basically have the ltsp-client
> packages installed by default on Edubuntu, allowing to simply export
> our install media as a fat chroot, so no more shipping chroots and
> building chroots (for the most common cases).

Discussed yesterday with the colleague who did the heavy lifting
on ALTSP back then -- he's thinking in rather similar direction;
I reminded him that flexibility and universality likes to come
for a price in complexity and resources.  Current infrastructure
does allow for both ways to coexist but it's internal forking.

OK, I should first grok the changes (and not just `bzr pull`),
and any notional discussion should wait until tomorrow at least.

> I obviously don't have any authority to impose that to the
> other LTSP developers

Hey, I barely qualify as one in the first place, so that was
more of a query of the driving forces and whether there's sense
in maint branches for 5.x -- for packages, I do have those, but
for the common ground, I don't know whether it's reasonable yet.

> so at this point, I'm just hoping other contributors will see a
> 20 days to a month period after 5.3 is released as a good idea
> and as something beneficial for LTSP upstream as a whole.

I consider doing some sort of facelift/release in roughly similar
timeframe but have no problem releasing 5.2-based packages if the
effort to forward-port the diff and prepare for yet another merge
would take too much time before ~April.

-- 
 ---- WBR, Michael Shigorin <mike-u2l5PoMzF/[email protected]>
  ------ Linux.Kiev http://www.linux.kiev.ua/

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_____________________________________________________________________
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