<div class="gmail_quote">On Mon, Jul 19, 2010 at 5:37 PM, Walter Bender <span dir="ltr"><<a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Mon, Jul 19, 2010 at 1:06 PM, Frederick Grose <<a href="mailto:fgrose@gmail.com">fgrose@gmail.com</a>> wrote:<br>
> On Mon, Jul 19, 2010 at 10:41 AM, Mel Chua <<a href="mailto:mel@melchua.com">mel@melchua.com</a>> wrote:<br>
>><br>
>> I'm going to have to miss today's meeting, but as an update on my task<br>
>> from last week: <a href="http://bugs.sugarlabs.org/ticket/1798#comment:22" target="_blank">http://bugs.sugarlabs.org/ticket/1798#comment:22</a><br>
><br>
><br>
> See this comment added to <a href="http://bugs.sugarlabs.org/ticket/1798#comment:23" target="_blank">http://bugs.sugarlabs.org/ticket/1798#comment:23</a> :<br>
><br>
> School-based deployments may want to take advantage of the persistent /home/<br>
> directory installation instead of the persistent OS overlay. The persistent<br>
> home folder is not a write-once, ever-diminishing storage space.<br>
><br>
> For consistency and stability reasons, the school may want to leave out the<br>
> persistent OS overlay (using a temporary overlay on each boot) and just use<br>
> the persistent /home/ directories to save the Learners' Journals and<br>
> settings.<br>
><br>
> If a school-wide system change were desired, the Sticks could be upgraded<br>
> with a simple exchange of the /LiveOS/squashfs.img file in the base file<br>
> system of each device or stick, perhaps, even triggered by the School<br>
> Server.<br></div></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">{...}</div></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"> if the size of the image changes</div>
dramatically, are there any issues regarding how space may have been<br>
allocated?</blockquote><div><br></div><div>Yes, I imagine that if all free space were allocated to the home.img file and a new, larger squashfs.img needed to fit on the disc, it would fail.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
{...}</blockquote><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">> storage space optimization is discussed on this<div class="im">
> page, <a href="http://wiki.sugarlabs.org/go/LiveOS_image" target="_blank">http://wiki.sugarlabs.org/go/LiveOS_image</a>.</div></blockquote><div><br></div><div>On that page, there are some reasons suggested for leaving some free space outside of the LiveOS installation.</div>
<div><br></div><div>So some planning may pay off. --Fred</div><div><br></div></div>