> What's the deal with putting Vinum-specific hacks into generic FFS
   > support code?
   
   It's not really Vinum-specific.  It applies to any file system where
   the name doesn't include information about partitioning.  But yes, it
   *is* a hack.  Arguably, so are partition encodings in the device name.
   I'm open to discussion on a better way of doing it.

see the raw partition.
   
   On Friday, 10 October 2003 at 16:23:31 +1000, matthew green wrote:
   >
   > what's this all about?  this sounds like a strange option to me
   > and i don't recall it being discussed anywhere...
   >
   > how is it different to using `sysctl kern.rawpartition`?
   
   Good question.  Where do I find the docco for kern.rawpartition?

try sysctl(8)?
   
   In any case, the intention here is to stop newfs from looking at the
   last letter of the device name and saying "Ah, that must be partition
   x.  But we don't have that many partitions".  If there's a nicer way
   of doing it, I'm all for it.  In FreeBSD it became superfluous during
   the transition to GEOM.
   
   BTW, this applies to fsck as well, and I haven't committed that code
   yet.  I'm holding off pending the outcome of this discussion.


the raw partition is the whole disk.  i'm almost certainly
you just need to document that people should run newfs on
the raw partition, but i haven't looked at the code at all.


.mrg.