> given an /etc/fstab entry like so:
> swap /var mfs -s32768,-P/.var,rw 0 0
> the system will reach multiuser with /var mounted twice. this can be
> remedied with a minor tweak of /etc/rc:
> < mount /var >/dev/null 2>&1
> > if [ ! -d /var/tmp ]; then
> > mount /var >/dev/null 2>&1
> > fi
Non-unified diff, bah!
I think it is better to mark the filesystem noauto. Relying on the
contents is just a hack. This has been discussed previously; search
the archives, I think it was misc@.
+<h3>Using the device as a system disk</h3>
+Because flash memory devices have a limited number of write cycles, filesystems
+should be mounted using the <tt>noatime</tt> option, with <tt>/var</tt> and
+<tt>/tmp</tt> created in memory by <tt>mount_mfs</tt>.
+An example <tt>/etc/fstab</tt>:
+/dev/wd0a / ffs rw,noatime 1 1
+swap /tmp mfs -s65536,rw 0 0
+swap /var mfs -s32768,-P/.var,rw,noauto 0 0
+The stock <tt>/var</tt> is renamed to <tt>/.var</tt>, which is then used to
+populate the mfs <tt>/var</tt> filesystem when it is created. Note that this
+can be an extremely useful hack in situations where the BIOS does not
+understand how to boot from an obscure or unsupported storage device.
+(The Sun Ultra5/10 machines, at least, are known to boot happily from
+CompactFlash cards given the proper adaptor; once the kernel is loaded,
+any supported PCI interface should work, even if it doesn't have OpenFirmware.)
<h3>You received the memory device from someone with whom you want to exchange data</h3>