From: David Greaves <david@dgreaves.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Neil Brown <neilb@suse.de>, Doug Ledford <dledford@redhat.com>,
Peter Rabbitson <rabbit+list@rabbit.us>,
linux-raid@vger.kernel.org
Subject: Re: Proper partition type for components with V1.x superblocks?
Date: Tue, 08 Jul 2008 00:10:00 +0100 [thread overview]
Message-ID: <4872A248.7060904@dgreaves.com> (raw)
In-Reply-To: <48725312.6090201@zytor.com>
H. Peter Anvin wrote:
> Neil Brown wrote:
>> On Thursday July 3, dledford@redhat.com wrote:
>>> On Wed, 2008-07-02 at 15:02 -0700, H. Peter Anvin wrote:
>>>> Why 0xDA?
>>>>
>>>> As far as I know, the closest thing there is to a registry is the
>>>> list that aeb at least used to maintain.
>>
>> Yes. http://www.win.tue.nl/~aeb/partitions/partition_types-1.html
>> lists 0xDA as
>>
>> da Non-FS Data
>>
>> Added on request of John Hardin (johnh@aproposretail.com).
>>
>> which is the closest we could come to "you won't want to look at
>> or do anything to this partition".
>>
>
> But that's not really what it is, either. The best would be to pick a
> new partition identifier entirely.
I thought that.
But then I asked why?
Couldn't come up with a decent reason.
non-fs seems to cover everything.
David
next prev parent reply other threads:[~2008-07-07 23:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 9:26 Proper partition type for components with V1.x superblocks? Peter Rabbitson
2008-06-11 11:23 ` Andre Noll
2008-06-11 12:12 ` Peter Rabbitson
2008-06-11 21:06 ` Andre Noll
2008-06-11 11:24 ` David Greaves
2008-06-11 11:35 ` Peter Rabbitson
2008-06-11 23:52 ` Neil Brown
2008-07-02 22:02 ` H. Peter Anvin
2008-07-03 5:17 ` Doug Ledford
2008-07-07 3:17 ` Neil Brown
2008-07-07 14:02 ` Doug Ledford
2008-07-07 17:33 ` H. Peter Anvin
2008-07-07 17:32 ` H. Peter Anvin
2008-07-07 23:10 ` David Greaves [this message]
2008-07-07 23:47 ` H. Peter Anvin
2008-07-07 17:38 ` H. Peter Anvin
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=4872A248.7060904@dgreaves.com \
--to=david@dgreaves.com \
--cc=dledford@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=rabbit+list@rabbit.us \
/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;
as well as URLs for NNTP newsgroup(s).