<br><br><div class="gmail_quote">On Sat, Jul 18, 2009 at 8:42 PM, John Watlington <span dir="ltr"><<a href="mailto:wad@laptop.org">wad@laptop.org</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"><br>
On Jul 16, 2009, at 4:40 PM, Sameer Verma wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Any documentation on what lives in /library and how to make it useful?<br>
</blockquote>
<br></div>
The idea behind /library was that the school server needed someplace to<br>
place large collections of content and user data.<br>
<br>
While some people have talked about backing up /library, my thinking<br>
was almost the opposite: while other partitions would move to an SSD<br>
for reliability, /library would remain on a hard disk for a good $/GB ratio.<br>
<br>
Cost wise, a 4 GB SSD should be about $10.<br>
<br>
Cheers,<br>
wad<br>
<br>
</blockquote></div><br>Interesting. <br><br>We used to use this distro called pebble (<a href="http://www.google.com/search?q=pebble+linux">http://www.google.com/search?q=pebble+linux</a>) for wifi routers and captive portals a few years ago. The current successor to pebble is Pyramid (<a href="http://code.google.com/p/pyramidlinux/">http://code.google.com/p/pyramidlinux/</a>). The OS would set up /var at boot time by partitioning the RAM (10MB, I think) and mounting /var there. The rest of the OS would be mounted in read only mode on a 64MB CF card and run from there. For updating, we would remount the OS in read-write mode via a script, apt-get update it, and remount it as read only. <br>
<br>logrotate would pick up compressed logs and you could either keep trimmed logs in RAM or ship them elsewhere (e-mailed or written to a rw partition). <br><br>We could do something along the lines of that. The solid state drive would run in read only mode, and the read-write (/var) could be delegated to a hard disk externally. <br>
<br>cheers,<br>Sameer<br>-- <br>Dr. Sameer Verma, Ph.D.<br>Associate Professor of Information Systems<br>San Francisco State University<br>San Francisco CA 94132 USA<br><a href="http://verma.sfsu.edu/">http://verma.sfsu.edu/</a><br>
<a href="http://opensource.sfsu.edu/">http://opensource.sfsu.edu/</a><br>