On Mon, Feb 28, 2011 at 09:24:39AM -0700, David Burgess wrote:
> True only if wear levelling is in place. To my knowledge, most
> consumer-marketed CF don't use this, so death will come much
> sooner if you try that.
And wear on the flash isn't the only good reason for read-only
filesystems on a non-redundantly-powered, headless device intended
to be used as a fast-booting network appliance:
* Checking root file system...
fsck 1.41.3 (12-Oct-2008)
/dev/sda1 contains a file system with errors, check forced.
/dev/da1:
Inodes that were part of a corrupted orphan linked list found.
/dev/sda1: UNEXPECTED INCOSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck fied with exit status 4 [fail]
* An automatic file system check (fsck) of the root filesystem failed.
A manual fsck must be performed, then the system restarted.
The fsck should be performed in maintenance mode with the
root filesystem mounted in read-only mode.
* The root filesystem is currently mounted in read-only mode.
A maintenance shell will now be started.
After performing system maintenance, press CONTROL-D
to terminate the maintenance shell and restart the system.
Give root password for maintenance
(or type Control-D to continue): _
--
{ IRL(Jeremy_Stanley); WWW(http://fungi.yuggoth.org/); PGP(43495829);
WHOIS(STANL3-ARIN); SMTP([email protected]); FINGER([email protected]);
MUD([email protected]:6669); IRC([email protected]#ccl);
ICQ(114362511); YAHOO(crawlingchaoslabs); AIM(dreadazathoth); }
_______________________________________________
Soekris-tech mailing list
[email protected]
http://lists.soekris.com/mailman/listinfo/soekris-tech
