Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 26 Jan 2000 12:06:36 -0500
From:      "Michael S. O'Donnell" <mso@bus.net>
To:        Mike Wade <mwade@cdc.net>
Cc:        "Jeffrey S. Sharp" <jss@subatomix.com>, Greg Lehey <grog@lemis.com>, freebsd-small <freebsd-small@FreeBSD.ORG>
Subject:   Re: your mail
Message-ID:  <388F299C.8976DAC5@bus.net>
References:  <Pine.GSO.4.10.10001260957410.4247-100000@server2>

next in thread | previous in thread | raw e-mail | index | archive | help
> > > Also it would be nice to have an "accidental power off" safe file
> > > system when using hard drives for embedded devices such as
> > > Internet Appliances.

i just started developing a hardware solution for this for a client
who has servers going to trade shows where uniformed individuals
occasionally take it upon themselves to 'push the button'.  i don't
mind losing the project to a software solution.  i know that would
be the solution the client would prefer (hardware would require me to
build a new unit for every different server; the design doesn't change,
but, the footprint and mounting does).  if anyone knows how to do it,
please tell me and/or the list.  i will request that the client make
the solution available under the FreeBSD license (my hardware solution
will not be).  the client runs _all_ systems under FreeBSD and i'm
quite confident he would welcome the opportunity to contribute.

thank you.
Michael S. O'Donnell


Mike Wade wrote:
> 
> On 26 Jan 2000, Jeffrey S. Sharp wrote:
> 
> > Therefore, I suggest something like what Warner has done (and that I am
> > working on as time permits), where the flash is the root fs and /tmp,
> > /var, and so on are mounted as small MFS filesystems.  The flash is
> > normally kept mounted read-only.  Then, instead of running an update
> > script, one simply remounts the flash read-write, makes changes, and
> > remounts read-only.
> 
> I've attempted this and I ended up with a filesystem of corrupted files
> when mounting read-only, remounting read-write, then remounting read-only
> several times.  I ended up partitioning the flash and creating a read-only
> binary partition and a read/write config partition that is mounted only on
> update.
> 
> >From the mount man page:
> 
> BUGS
>      It is possible for a corrupted file system to cause a crash.
>      Switching a filesystem back and forth between asynchronous and normal
>      operation or between read/write and read/only access using ``mount
>      -u'' may gradually bring about severe filesystem corruption.
> 
> It would be very nice to have this feature when dealing with flash.  Also
> it would be nice to have a "accidental power off" safe file system when
> using hard drives for embedded devices such as Internet Appliances.
> 
> ---
> Mike Wade (mwade@cdc.net)
> Director of Systems Administration
> CDC Internet, Inc.
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-small" in the body of the message


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-small" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?388F299C.8976DAC5>