The whole idea of read-only is for two reasons:
nightly in a typical museum situation) 2) To preserve the CF memory, which has a limited number of write cycles, in the case of a HD-less system
If the computer needs to be networked, then you might be moving away from the situation I have in mind, mainly an audio/video system in a gallery or museum. Another situation for this would be a "headless" computer for live stage performance, where you would often be powering it up and down like any other effects unit or sound module. (Unless you're one of those weirdos that likes typing on the laptop in front of crowds...)
In case of a networked installation, you'd probably want to set it up more like a "normal" server and put it someplace where you know it won't get zapped. But imagine, you don't *have* to connect to the internet to use a computer... ;-)
d.
errordeveloper@gmail.com wrote:
hm .. how about locks and other stuff ? there always some things which want to be written to somewhere in /var! the gentoo runscripts use /var/lib/init.d/ i reckon having a bit of space writable in /var and /tmp symlinked to /var ..could be usefull, keep one or two day's logs as well and log them on a loghost or mail before they being wiped off.. you can mail without a server .. might be able to use mutt or some command line util to do it via smtp .. well, this deppends on the network availability!
On Tue, Jan 01, 2008 at 10:49:14PM +0100, Derek Holzer wrote:
Can't use logrotate if the partition is mounted readonly. I can see the point if the idea wasn't to fill up disk space, but my whole idea is to not write to the disk at all. Symlink is also a good idea, though.
best, d.
Andy Farnell wrote:
On Tue, 1 Jan 2008 21:57:18 +0100 plessas@mur.at (Peter Plessas) wrote:
- Derek Holzer derek@umatic.nl [2007-12-31 18:47]:
So I made sure to mount all my drives read-only, and that everything would start from a script on power-up. Having the whole operating system on a Flash card/USB stick (again, no logging, read-only) is also quite
How do you do that? Do you mount /var/log as ramdisk which gets erased at reboot, or do you tell every service/daemon not to log?
Symlink logs to /dev/null or use logrotate to delete them on the hour. Better if you can tell a process not to log though, stop the problem at its source.
thanks, PP
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- derek holzer ::: http://www.umatic.nl ::: http://blog.myspace.com/macumbista ---Oblique Strategy # 65: "Emphasize differences"
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list