Since you grant my premise, the corollary is that it wouldn't hurt to have mono installed. See <a href="http://www.mono-project.com/Small_footprint">here</a> about the mono footprint on disk and in memory.<br><br><div class="gmail_quote"> On Fri, May 15, 2009 at 5:34 AM, Martin Langhoff <span dir="ltr"><<a href="mailto:martin.langhoff@gmail.com">martin.langhoff@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="im">On Fri, May 15, 2009 at 2:14 PM, Carol Farlow Lerche <<a href="mailto:cafl@msbit.com">cafl@msbit.com</a>> wrote:<br> > Martin, the last disk we bought, a few days ago, was $100 and half a<br> > terabyte. I understand that you are trying to fit the XS into the<br> > preexisting XO hardware, but realistically it is unlikely to be a<br> > configuration a real school could use by itself. The deployments we know<br> <br> </div>I agree. The XS-on-XO should be read as "XS on XO+ext usb hd" :-)<br> <br> If the ext usb hd is usb-powered, the whole setup can survive<br> unreliable power and brownouts quite well, which is one of the main<br> factors wrt cost of the XS.<br> <div><div></div><div class="h5"><br> cheers,<br> <br> <br> m<br> --<br> <a href="mailto:martin.langhoff@gmail.com">martin.langhoff@gmail.com</a><br> <a href="mailto:martin@laptop.org">martin@laptop.org</a> -- School Server Architect<br> - ask interesting questions<br> - don't get distracted with shiny stuff - working code first<br> - <a href="http://wiki.laptop.org/go/User:Martinlanghoff" target="_blank">http://wiki.laptop.org/go/User:Martinlanghoff</a><br> </div></div></blockquote></div><br>