Re: CF and Disk Writes

Chuck Yerkes <[email protected]> Fri, 21 Jun 2002 10:36:51 -0700
Newsgroups gmane.os.openbsd.embedded
Message-ID <[email protected]>
Quoting [email protected] ([email protected]):
> "David Simmons" <[email protected]> writes:
> > How do I know what else will write/destroy the CF without putting
> > the write-protect on the whole thing (since it needs to be 'open'
> > for the leases file?)
> 
> Along the lines of what a few other people have posted (Chuck Yerkes
> for one), I modified the rc file to not remount the CF read/write at
> boot time, and to extract a tar file of /var into an MFS partition.

Actually, I have /var/mfs/  mounted.
On startup, after mounting that, I rsync -av /var/mfs.PROTO/ /var/mfs/
It's got the basics to run (dhcpd.leases, some namedb stuff I want,
structure for /var/run/).

I tweaked libutil to use /dev/term/  for ptys.  
Must redo that "right" to get wtmp to work, but on login,
there's a chown that happens to the device, so the startup
also does:
  mount /dev/term/  #(mfs)
  (cd /dev/term && sh /dev/MAKEDEV terms)   #(build devices on /dev/term/).

I'd done those libutil hack a long time ago when I was playing
with readonly root partitions in general.

syslog.conf points everything to another host.  It's a home
firewall, so taht host is sometimes down.  BUt someone whacking
at a readonly box when all the boxes behind it are off it
pretty much moot to me.

Question:
what options in fstab will let me limit the size of an MFS?
It's easy on Solaris, but the /dev/term/ "partition" can be
50k, really.


I looked at some other boxes, with Pentiums, but all these "embedded
Pentium" type people don't seem to get that Keyboards and VGA are not
just unneeded, but also undesirable.

I still want one of these "innovating" PC companies to come out with
a freaking Open Boot PROM instead of BIOS.  Like my Suns.  My SGIs.
Like my freaking Mac laptop.  ("boot net" from a laptop is cool)