[Server-devel] /library partition

[Sameer Verma]

On Sat, Jul 18, 2009 at 8:42 PM, John Watlington <wad at laptop.org> wrote:

>
> On Jul 16, 2009, at 4:40 PM, Sameer Verma wrote:
>
>  Any documentation on what lives in /library and how to make it useful?
>>
>
> The idea behind /library was that the school server needed someplace to
> place large collections of content and user data.
>
> While some people have talked about backing up /library, my thinking
> was almost the opposite: while other partitions would move to an SSD
> for reliability,  /library would remain on a hard disk for a good $/GB
> ratio.
>
> Cost wise, a 4 GB SSD should be about $10.
>
> Cheers,
> wad
>
>
Interesting.

We used to use this distro called pebble (
http://www.google.com/search?q=pebble+linux) for wifi routers and captive
portals a few years ago. The current successor to pebble is Pyramid (
http://code.google.com/p/pyramidlinux/). 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.

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).

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.

cheers,
Sameer
-- 
Dr. Sameer Verma, Ph.D.
Associate Professor of Information Systems
San Francisco State University
San Francisco CA 94132 USA
http://verma.sfsu.edu/
http://opensource.sfsu.edu/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.laptop.org/pipermail/server-devel/attachments/20090718/e5eaa97d/attachment.htm