<br><br><div class="gmail_quote">On Tue, Mar 18, 2008 at 8:24 PM, Bryan Berry <<a href="mailto:bryan@olenepal.org">bryan@olenepal.org</a>> 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="Ih2E3d"><br>
> I would like to minimize, if not eliminate, such local customizations...<br>
><br>
> This is still an open technical argument. Comments ?<br>
<br>
</div>Our XS setup will probably differ significantly from that in Birmingham<br>
or Uruguay since we will not have Squid or Dansguardian running on the<br>
XS. We intend for our XS installations to be roughly identical in terms<br>
of configuration but our XS installations will likely be very different<br>
from other countries.<br>
<br>
"One-size" does not fit all when it comes to the XS, in my opinion.</blockquote><div><br>Just because you don't need Squid or Dansguardian does not necessarily mean that you can't use the same distro. In fact, it isn't really a driving factor.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Also, different countries will use different hardware. In Nepal, it is<br>
difficult for us to order a particular brand of server and configuration<br>
due to customs issues. We would love to use a custom hardware solution<br>
like the one Wad has in mind, however we can't use it until it is ready<br>
*and* falls into our price range, including customs duties.</blockquote><div><br>I disagree with this on one fundamental thing. We can create a Linux
distro that can run on just about any hardware that is remotely
standard. This has been done many times. The issue then becomes size of
distro vs. benefit to keeping "cruft" in it. <br><br>Custom hardware would obviously only be useful if it was a benefit to those who would buy it. I imagine that discussion is ongoing within the organization, but I'm a noob and don't know how this place works yet ;)<br>
</div><div> </div><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">> OS + config info + system state (ejabberd database, user database &<br>
> info) <=> school server<br>
<br>
</div>This could all be backed up to a livecd or usb key w/ Mondo archive,<br>
very easily. Or,<br>
<br>
OS + Config Info => LiveCD w/ Mondo <br></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
system state + Library => rsync or rdiffbackup</blockquote><div><br>These look like very decent options and are being done all over the place. Check out my other email responding to Wad for another, more disruptive, idea.<br>
<br>Have you used these in your current testing? What are your results so far? What would help beyond an organizational decision in getting your backup solution in place?<br></div></div><br clear="all"><br>-- <br>Aaron Huslage - 503.860.1634<br>
<a href="http://blog.hact.net">http://blog.hact.net</a><br>IM: AIM - ahuslage; Yahoo - ahuslage; MSN - <a href="mailto:huslage@gmail.com">huslage@gmail.com</a>; GTalk - <a href="mailto:huslage@gmail.com">huslage@gmail.com</a>