[Pkg-ltsp-devel] features i'd like to work on

[Otavio Salvador]

Vagrant Cascadian <vagrant at freegeek.org> writes:

> the first one is a wrapper around chroot that does special things like
> mounting /proc and /sys and /tmp in the chroot, as well as setting
> environment variables that prevent daemons from starting within the
> chroot on the server. then, instead of calling chroot directly, our
> scripts can use this wrapper script. we could even set up some alias
> commands for commonly used things like apt-get pretty easily. this is a
> feature i've implemented in lessdisks that i would really like to see
> for ltsp(and can probably even copy some of the code).  oh, i couldn't
> resist, i've already implemented this:
> http://llama.freegeek.org/~vagrant/bzr-archives/ltsp/vagrant-ltsp-chroot

I like the idea but I found some problems with current code:

 - arch detection is debian dependent. There's already made code to be
   generic in set-arch and you might do a look at it;
 - impossibility to set ROOT to something different of /opt/ltsp while
   in ltsp-build-client it's possible;

The way the I see to workaround this issues is to use a ltsp common
plugin repository to set the architecture and root running same code
that will be run by ltsp-build-client. The most complicated problem
is, when the user use --base it won't be passed to ltsp-chroot and
then we'll need to pass the commandline option. That won't make too
much difference of current way to do it.

> i'd also like to split some of the functionality found in
> ltsp-update-kernels get split into the ltsp-client package, and have it
> run chrooted(or in the case of a different architecture, on a privledged
> client with write access of some sort). then the ltsp-update-kernels
> package would mostly just copy files into place(and maybe run chrooted
> scripts if the architecture is supported), rather than the special
> network-bootable preparations(mknbi, yaboot, netabootwrap, etc). this
> way we could get support for multiple architectures.

I didn't understand this last one. If we remove mknbi and like we
loose support to anything but pxe. No?

-- 
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: otavio at debian.org      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
 you the whole house."