Re: [Ltsp-developer] Serious flaw in virtual-ltsp scripts

[Dashamir H. <das...@gm...>]

On Sat, Oct 6, 2018 at 10:56 AM Alkis Georgopoulos <al...@gm...> wrote:

>
> > I get the impression that any scripts listed on `/etc/ltsp/cleanup.d`
> > will be called automatically, besides the scripts on
> `/usr/share/ltsp/cleanup.d`,
>

This works, but at least in my case it is not so clean. I also install
software
by compiling the code, and so it is not easy to clean up everything (just
by removing
packages).

> Another possible solution, which would be "clean" in my opinion, is
> > to create a chroot directory by taking a snapshot/copy of the root ("/")
> > directory. Then it can be managed as a chroot client image (chroot to it,
> > install new packages and software, etc.) Then whatever is installed on
> > the server after the creation of the chroot directory does affect the
> > content
>
> That's just like `cp -a / /opt/ltsp/i386`. There's no need to get a
> specific tool for it. And then it still involves chroots for
> maintenance, which is what chrooted ltsp wants to avoid, as not all
> people like to use console to maintain installations.
>

This command (`cp -a / /opt/ltsp/i386`) somehow did not work for me.
I searched on internet and found this one that works better:
`rsync -a
--exclude={/proc,/dev,/sys,/opt/ltsp,/tmp,/run,/mnt,/media,/lost+found} /
/opt/ltsp/i386`
However when I run `ltsp-update-image --cleanup /opt/ltsp/i386` it fails.
Maybe I am missing something.

So, for the time being I am still keeping the clumsy solution (when
something new
needs to be installed on the client, just rebuild the whole ltsp server).

Regards,
Dashamir