lkml.org 
[lkml]   [1999]   [Mar]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Parition Slices
Date
From
Richard Gooch writes:

->> You seem to be suggesting to use the same ID for primary and extended
->> paritions.
->
->Well, yes, but not in the way you describe.

->you have 4 main partitions, which may be either "primary" or
->"extended". They are numbered 1 to 4. Changing a primary to an
->extended does not change the partition numbers for the main
->partitions.
->
->The subpartitions within extended partitions are called logical
->partitions, and they start counting from 5. There is the potential for
->these to be renumbered, if you change a primary partition to an
->extended partition (where there is another extended partition after
->it). The logical partitions in the second extended partition will be
->renumbered.
->
->So, the only problem you should have is if you create *two* extended
->partitions and populate them both. While this is a potential problem,
->I don't think it really matters because there isn't much point to
->having multiple extended partitions. A single extended partition can
->hold plenty of logical partitions.

But it is not such rare either. If I happen to have bsd-subpartitions,
slices, and dos-subpartitions ,extended partitions, then the ID's tend to
jump in the current implementation. BSD here's just an example, it could
be Solaris slices, or mac stuff, or Minix, or maybe even future raw
(sub-)paritions.

You suggest to solve this problem to assign 'slice' to bsd-style
sub-partitions.

I think that it would be much simpler to just decide that whatever is
inside of a primary partition be it 'dos extended partition' or a 'bsd
slices' or whatever else like Minix. should have their own ID. I think
that we can just call them 'slices'. If there's no slices it would be
just 's0' or we could skip it altogether.

Thus the only change over what you had suggested already
would be that 'dos extended partition' would be named a 'slice'.

Thus the current design:

controller
bus (aka. primary/secondary)
target (aka. master/slave)
unit
partition (DOS primary or logical)
slice (Solaris/*BSD slices)


would change to ([*] means changed):

controller
bus (aka. primary/secondary)
target (aka. master/slave)
unit
partition (DOS primary/BSD disklabel/??) [*]
slice (Solaris/*BSD slices/DOS logical/MINIX sub-part/??) [*]

I think in this way we have most flexibility and we are sure that the
"ID"'s won't accidentally jump if we change something else, semingly
unrelated.

Comments?

Adam

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:50    [W:0.175 / U:0.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site