From: Andrew Clausen <clausen@conectiva.com.br>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, bug-parted@gnu.org,
linux-kernel@vger.kernel.org
Subject: Re: Partition IDs in the New World TM
Date: Mon, 22 Jan 2001 20:30:54 -0200 [thread overview]
Message-ID: <3A6CB49E.75B8937D@conectiva.com.br> (raw)
In-Reply-To: <200101222139.f0MLd8r01730@flint.arm.linux.org.uk>
Russell King wrote:
>
> Andrew Clausen writes:
> > But, for "well behaved operating systems", can't we do it this way?
> > (For the dos partition table scheme, 0x83 could be our "file system
> > type", 0x82 our "swap type", or whatever)
>
> I think you're complaining about the partition IDs in this thread, and not
> the partition "schemes" that Linux supports. Am I right?
Well, I don't like either, hehe. But, partition IDs are the only
thing I'm talking about here (the other was merely drive-by flaming)
> Well, the Linux kernel doesn't really care about partition IDs at all,
> except in one circumstance - to detect auto RAID partitions.
Why is this necessary? Can't the RAID drivers probe the device for
signatures, the same way file systems do?
(BTW: LVM does this too, and linux-ppc uses partition types as
heuristics
for finding the root device, IIRC, and lots of other boring stuff. But,
I suspect it isn't needed)
> Apart from
> that, the kernel couldn't care. You could set all your Ext2 partitions
> as ID 82, your swap as ID 83 and Linux would carry on as if nothing had
> changed.
Exactly. So, for new disk labels, or whatever, we should recommend to
the relevant hackers that we have exactly one number for Linux. Or
what?
> About the only user programs that know about partition IDs are:
> - fdisk (its part of the partition table format)
> - installers (to stop users doing stupid things)
Exactly.
Andrew Clausen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-22 22:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-22 16:17 Partition IDs in the New World TM Andrew Clausen
2001-01-22 16:32 ` Brian Gerst
2001-01-22 16:47 ` Andrew Clausen
2001-01-22 21:39 ` Russell King
2001-01-22 22:30 ` Andrew Clausen [this message]
2001-01-22 22:42 ` Russell King
2001-01-22 23:28 ` Andrew Clausen
2001-01-22 23:35 ` H. Peter Anvin
2001-01-23 4:47 ` Andreas Dilger
2001-01-23 6:23 ` H. Peter Anvin
2001-01-23 19:26 ` Matt D. Robinson
2001-01-24 8:18 ` Andreas Dilger
2001-01-22 22:16 ` Glenn McGrath
2001-01-22 23:35 ` Jason Venner
-- strict thread matches above, loose matches on Subject: below --
2001-01-22 22:42 Andries.Brouwer
2001-01-22 17:35 ` Mark I Manning IV
2001-01-22 22:55 Andries.Brouwer
2001-01-23 15:46 Andries.Brouwer
[not found] <OF03708398.46274A87-ON872569DD.005CA0DE@LocalDomain>
2001-01-23 17:08 ` Andrew Clausen
[not found] <OF5F9BE7DB.C1ADFB0E-ON872569DD.006485CC@LocalDomain>
2001-01-23 18:35 ` Andrew Clausen
2001-01-23 22:01 ` Glenn McGrath
2001-01-24 13:40 ` Andrew Clausen
2001-01-24 10:28 Andries.Brouwer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A6CB49E.75B8937D@conectiva.com.br \
--to=clausen@conectiva.com.br \
--cc=bug-parted@gnu.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox