-----BEGIN PGP SIGNED MESSAGE-----


  I have a machine just installed with NetBSD-1.2. We installed
boot blocks and a kernel that talk to COM1 instead of pc0/vt0.
  We want two different root partitions; for two different versions
of a product that needs to be tested. We share a common /var partition
(which is ridiculously large given trends in IDE drive pricing, but
then we may need a rediculous amount of log space to debug)
  When we boot from the second root partition (wd0e), we are unable
to mount wd0f. We can mount /dev/wd0a just fine, and when booting
from /dev/wd0a, we can mount e and f just fine.
  The error we get is:

# mount /var
ffs: /dev/wd0f on /var: Device busy

  Is there some protection of the partition following the root
partition that is messing us up?
  Should we reinstall with two *DOS* partitions and use a boot manager
to switch between boot areas instead of using the NetBSD boot blocks?

]   Temporarily located in balmy Helsinki, Finland, at SSH      | one quark   [
]  Michael Richardson, Sandelman Software Works, Ottawa, ON     | two quark   [
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ | red q blue q[
] panic("Just another NetBSD/notebook using, kernel hacking, security guy");  [

  
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQB1AwUBMxsHW8mxxiPyUBAxAQGymQMAqMbrMOI+L/M2oqVECGRTpWj2Pdsr8CqP
hfDSxt0R+XHr8WAbXiw+x8IsDkIhoWIoOvaJSZoMjUPWKj9fnduISt5/6AZUyIF+
tQ+sXZoQf2WuRH/hExikjrvyfAW0FbeJ
=xs0+
-----END PGP SIGNATURE-----