From: Hollis Blanchard <hollis@amulet.co.jp>
To: Tom Gall <tom_gall@vnet.ibm.com>
Cc: yellowdog-devel@lists.yellowdoglinux.com,
linuxppc-dev@lists.linuxppc.org
Subject: Re: RFC: Changing default partition type for linux/ppc
Date: Fri, 07 Jul 2000 22:33:10 +0900 [thread overview]
Message-ID: <3965DC16.7CB143B3@amulet.co.jp> (raw)
In-Reply-To: 3965D59C.BC1BAC93@vnet.ibm.com
Tom Gall wrote:
>
> Benjamin Herrenschmidt wrote:
> >
> > So I suggest moving to Linux_ext2, Linux_swap, or maybe simply Linux and
> > Linux_swap (since ext2 is not the only filesystem Linux may put on
> > these). Using a different type for swap would help avoiding confusion.
>
> I agree. I think this is a good step. However there's the obvious interoperability
> problems with MacOS, OS X etc... Hopefully Apple's OSes wouldn't do anything evil
> to the partition they don't recognize.
Well, they don't at this point. For example in partitioning tool in
LinuxPPC 2000, LinuxPPC Inc decided it would be better to use the type
"Linux_PPC". This works (in that nothing gets overwritten, corrupted,
etc) but has the disadvantage that no other software knows anything
about that type.
If you were writing software it would be pretty poor form to find data
you didn't understand and decide to "fix" it. I know there are programs
like that out there (if you look at
http://www.win.tue.nl/~aeb/partitions/partition_types-1.html it seems
there is a rich history of them), but Apple seems to be doing well in
that regard so far...
Of course, everything may change with OS X but I would hope they don't
get malicious all of a sudden.
-Hollis
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-07 13:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-07 10:59 RFC: Changing default partition type for linux/ppc Benjamin Herrenschmidt
2000-07-07 13:05 ` Tom Gall
2000-07-07 13:28 ` Olaf Hering
2000-07-07 13:33 ` Hollis Blanchard [this message]
2000-07-07 15:25 ` Charles Stevenson
2000-07-07 16:14 ` Michael Schmitz
2000-07-07 22:19 ` Benjamin Herrenschmidt
2000-07-07 19:30 ` Nelson Abramson
2000-07-08 5:16 ` Ethan Benson
2000-07-10 14:38 ` Michael Schmitz
2000-07-09 7:37 ` Hollis Blanchard
2000-07-07 14:12 ` Eric Valette
2000-07-07 17:37 ` Mark Hatle
2000-07-07 22:21 ` Benjamin Herrenschmidt
2000-07-09 21:22 ` Tom Vier
2000-07-09 21:33 ` Benjamin Herrenschmidt
2000-07-10 0:33 ` Tom Vier
2000-07-10 1:49 ` Matt Brubeck
-- strict thread matches above, loose matches on Subject: below --
2000-07-07 11:22 Iain Sandoe
2000-07-07 12:49 ` Hollis Blanchard
2000-07-07 14:13 ` Geert Uytterhoeven
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=3965DC16.7CB143B3@amulet.co.jp \
--to=hollis@amulet.co.jp \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tom_gall@vnet.ibm.com \
--cc=yellowdog-devel@lists.yellowdoglinux.com \
/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).