From: Hollis Blanchard <hollis@amulet.co.jp>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: yellowdog-devel@lists.yellowdoglinux.com,
linuxppc-dev@lists.linuxppc.org
Subject: Re: RFC: Changing default partition type for linux/ppc
Date: Sun, 09 Jul 2000 16:37:54 +0900 [thread overview]
Message-ID: <39682BD2.C34BE171@amulet.co.jp> (raw)
In-Reply-To: Pine.LNX.4.10.10007071754400.28685-100000@opal.biophys.uni-duesseldorf.de
Michael Schmitz wrote:
>
> >
> > 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.
>
> So can we get all distributions to agree on this partition type scheme?
[snip]
> LinuxPPC 1999 used the same type, and I think the 2000 change is a bad
> thing. What are YellowDog and SuSE using?
I agree. So far the Linux "standard" has been to pretend to be A/UX
partitions. To my knowledge, every distribution with the exception of
LinuxPPC 2000 uses Apple_UNIX_SVR2. (And I'm not sure that alteration
was especially well thought out.)
> Benh: are you maintaining the official version of pdisk now?
That would be Eryk Vershen <eryk@cfcl.com>, who recently resurfaced in
February
(http://lists.linuxppc.org/listarcs/linuxppc-user/200002/msg01471.html).
So now that the conversation's died down, it seems like everybody's
happy with "Linux" (Mark Hatle's suggestion was for "Linux_*") and
"Linux_swap".
-Hollis
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-09 7:37 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
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 [this message]
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=39682BD2.C34BE171@amulet.co.jp \
--to=hollis@amulet.co.jp \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.