Subject: Re: new disklabels - part2
To: Bill Studenmund <email@example.com>
From: Greywolf <firstname.lastname@example.org>
Date: 09/21/1999 11:11:59
[ still need to read that wedge thing...but...]
Why not have the central disklabel accommodate 16 partitions (hard),
with the remaining six entries pointing to other partition types at
other locations on the disk...?
# > My suggestion for the raw-device would be partition zero. Otherwise, what
# > are you planning to do when we bump to, say, 128 partitions? Move it again?
# I don't forsee us ever moving this number again. I think we should get it
# right now, and leave it alone.
# raw == partition 0 would be fine too. I was just thinking of keeping the
# minor #'s the same for the first 8 partitions, but that's not a big deal.
Is intel the only port that uses 'd' as the 'whole (Berkeley) disk',
while others use 'c'?
In this case, getting it 'right' would probably be one of the following
1. Keep 'c' as the default whole disk partition.
2. Allow the whole disk partition to be moved at will.
(1) makes the assumption that we're going to keep the 'whole disk'
semantics in the driver, but it also holds with the traditional layout
of the disk. Is 'c' usable, actually, as a whole-disk partition at the
moment, or is that an illegal operation (haven't tried it, don't know)?
(2) would require the administrator to provide the location of the whole
disk to a disklabel(8) command, which could turn out to be guesswork,
unless we granted explicit permission to access the disklabel through
any partition on the disk. This might be confusing to the neophyte,
and it could well be a PITA to implement correctly.
[note: my logic is not the greatest, so forgive any fallacious jumps
I might have made.]
# Take care,
"Just click on the START button and your journey to the Dark Side
will be complete!"