<div dir="ltr">On Mon, Aug 4, 2008 at 8:51 AM, Jeremy Katz <span dir="ltr"><<a href="mailto:katzj@redhat.com">katzj@redhat.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Mon, 2008-08-04 at 08:43 -0500, Richard Shaw wrote:<br>
> On Mon, Aug 4, 2008 at 7:54 AM, Jeremy Katz <<a href="mailto:katzj@redhat.com">katzj@redhat.com</a>> wrote:<br>
</div><div class="Ih2E3d">> >> Also, after reading a previous post on this list, I would keep updates<br>
> >> to only things you care about since the overlay file records block<br>
> >> changes and you will eventually run out of overlay.<br>
> > This is the case and unfortunately, with things currently in the kernel,<br>
> > I don't really see any way around it. Modulo writing some tool to<br>
> > (likely offline) analyze and rewrite the snapshot file. But relatively<br>
> > deep dark voodoo required to write such a tool<br>
><br>
</div><div class="Ih2E3d">> I don't know if this would be easier, but what about a tool that would<br>
> incorporate the changes back into the image file and then re-zero the<br>
> overlay?<br>
<br>
</div>The problem is that incorporating the changes back in basically boils<br>
down to "make a new image". Which isn't that difficult to do, it's just<br>
a matter of having the disk space for it and also the time -- it'd<br>
largely just be a matter of running good chunks of the livecd image<br>
creation process over again.<br>
<div><div></div><div class="Wj3C7c"><br>
Jeremy<br>
<br>
</div></div></blockquote></div>Well, I don't know about other users of the live USB system, but that would be okay with me. A prereq. would be you have enough HD space to copy the image, update it, and then copy it back to the USB drive.<br>
<br>Richard<br></div>