Re: Serious flaw in virtual-ltsp scripts

--===============7905438304997549765==
Content-Type: multipart/alternative; boundary="000000000000953acd0577a4b747"

--000000000000953acd0577a4b747
Content-Type: text/plain; charset="UTF-8"

On Sat, Oct 6, 2018 at 10:56 AM Alkis Georgopoulos <[email protected]> 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

--000000000000953acd0577a4b747
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div cl=
ass=3D"gmail_quote"><div dir=3D"ltr">On Sat, Oct 6, 2018 at 10:56 AM Alkis =
Georgopoulos &lt;<a href=3D"mailto:[email protected]">[email protected]</a>&g=
t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
&gt; I get the impression that any scripts listed on `/etc/ltsp/cleanup.d` =
<br>
&gt; will be called automatically, besides the scripts on `/usr/share/ltsp/=
cleanup.d`,<br></blockquote><div><br></div><div>This works, but at least in=
 my case it is not so clean. I also install software</div><div>by compiling=
 the code, and so it is not easy to clean up everything (just by removing</=
div><div>packages).</div><div><br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex">
&gt; Another possible solution, which would be &quot;clean&quot; in my opin=
ion, is<br>
&gt; to create a chroot directory by taking a snapshot/copy of the root (&q=
uot;/&quot;)<br>
&gt; directory. Then it can be managed as a chroot client image (chroot to =
it,<br>
&gt; install new packages and software, etc.) Then whatever is installed on=
<br>
&gt; the server after the creation of the chroot directory does affect the =
<br>
&gt; content<br>
<br>
That&#39;s just like `cp -a / /opt/ltsp/i386`. There&#39;s no need to get a=
 <br>
specific tool for it. And then it still involves chroots for <br>
maintenance, which is what chrooted ltsp wants to avoid, as not all <br>
people like to use console to maintain installations.<br></blockquote><div>=
<br></div><div>This command (`cp -a / /opt/ltsp/i386`) somehow did not work=
 for me.</div><div>I searched on internet and found this one that works bet=
ter:</div><div>`rsync -a --exclude=3D{/proc,/dev,/sys,/opt/ltsp,/tmp,/run,/=
mnt,/media,/lost+found} / /opt/ltsp/i386`</div><div>However when I run `lts=
p-update-image --cleanup /opt/ltsp/i386` it fails.</div><div>Maybe I am mis=
sing something.</div><div><br></div><div>So, for the time being I am still =
keeping the clumsy solution (when something new</div><div>needs to be insta=
lled on the client, just rebuild the whole ltsp server).</div><div><br></di=
v><div>Regards,</div><div>Dashamir</div></div></div></div></div></div>

--000000000000953acd0577a4b747--


--===============7905438304997549765==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============7905438304997549765==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_____________________________________________________________________
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

--===============7905438304997549765==--