>[..]
>/dev/wd0a           30206    24414     3376    88%    /
>/dev/wd0s3a         76239    16131    54009    23%    /opt
>/dev/wd0s2e        265310   249630    -5544   102%    /usr
>/dev/wd0s3g         98479    33211    57390    37%    /usr/local
>/dev/wd0s3e         39950    13796    22958    38%    /var
>/dev/wd2s4a         31279    11233    18483    38%    /netbsd
>/dev/wd2s4e        248335   107127   128792    45%    /netbsd/usr
>/dev/wd0s3f         39950      204    36550     1%    /netbsd/var
>/dev/wd0s3h         98479       23    90578     0%    /netbsd/usr/local
>
>Surely by now NetBSD can recognise more than one BSD partition on a disk...

It seems to me right off the bat that you could have NetBSD recognize any
number of BSD partitions on a disk, since the BSD disklabel doesn't have
any relation to the MS-DOS partiton table.  Whether or not it should is
another interesting question :-)  If you were to plug the right numbers
into a NetBSD disklabel, it could access another partition just fine (I mean,
after all, that's how the MS-DOS partition works).  Of course, this doesn't
solve the "eight partitions per disk problem".  FreeBSD has "eight partitions
per slice", which is great as long as you've already divided up your disk
into multiple slices.  (Errr, I could be wrong about FreeBSD -- you may be
able to have more than 8 partitions per slice.  It's been a while).

The FreeBSD slice code does get you some nice interoperability with MS-DOS,
though, which is something that NetBSD doesn't do so well.

--Ken