Bump :)
-----Original Message-----
From:
nslu2-linux@... [mailto:
nslu2-linux@...] On
Behalf Of obi_jan
Sent: Tuesday, June 09, 2009 2:32 PM
To:
nslu2-linux@...
Subject: [nslu2-linux] SlugOS 5.3: /var/volatile same as ramfs?
As previously mentioned, I just advanced from SlugOS 3.10 to 5.3 and am
exploring this new world. Being a creature of habit, I immediately started
setting it up the same way I did under 3.10. In that regard, I always used
to apply the method to move /dev and /var to a ramfs, as described further
down in this Wiki article here:
http://www.nslu2-linux.org/wiki/FAQ/SpinDownUSBHarddisksThe rationale behind this is to minimize the writes to the memstick I am
booting off. However, I realized that in 5.3, most sub directories in the
/var tree actually reside in /var/volatile (sym-linked). After further
reading online and in this forum, I have come to the conclusion that
/var/volatile is in fact already an in-memory filesystem, is that correct?
How much memory does it take away from the RAM, and do I now need to employ
log rotation and archiving strategies to make sure the volatile fs never
fills up?
Also, is it still worthwhile to try to move /dev to a separate ramfs to
further minimize access to it? I guess it's not necessary, as the access to
/dev is mostly read-only, which is not a problem for solid state memory, is
that correct? Under 3.10, I was actually booting off an external HDD, so it
was important for me to minimize both reads and writes to it to allow for it
to spin down after some idle time.
Jan
