From: Tom Vier <thomassr@erols.com>
To: Benjamin Herrenschmidt <bh40@calva.net>
Cc: linuxppc-dev@lists.linuxppc.org,
yellowdog-devel@lists.yellowdoglinux.com
Subject: Re: RFC: Changing default partition type for linux/ppc
Date: Sun, 9 Jul 2000 20:33:16 -0400 [thread overview]
Message-ID: <20000709203316.A12712@zero> (raw)
In-Reply-To: <20000709213309.30020@192.168.1.10>; from bh40@calva.net on Sun, Jul 09, 2000 at 11:33:09PM +0200
On Sun, Jul 09, 2000 at 11:33:09PM +0200, Benjamin Herrenschmidt wrote:
> >i'd vote for "ext2", "hfs", etc. call them what they are, and keep it simple,
> >instead of "Linux_Ext2fs" or something similar.
>
> That won't work for 2 reasons:
>
> - MacOS and MacOS X won't mount HFS partitions if the type is not Apple_HFS
you're right. i was just giving examples of names and hfs popped into my
head.
> - If we put the fs type (like Linux_ext2) in the partition type, it's
> not updated
> by the various linux mkxxxx tools, and can be confusing. I would
> rather keep
> a simple "Linux" type, along with "Linux_swap" to help skipping swap
> partition
> in bootloaders (and installers)
i'm not sure what you're saying. mkfs doesn't touch partition tables.
i was thinking of partition types as more of a description of the fs, rather
than naming them after the OS that uses them. on pcs, linux uses the same
partition type for all file systems (except for swap). it wouldn't be a bad
idea to do the same, as you seem to be saying. "Linux_swap" as a type does
seem a little redundant to me, since the partition name can be set to
"swap". on pc/dos style partitions they use a seperate type for for swap,
but they also don't have a seperate name field.
--
Tom Vier <thomassr@erols.com>
DSA Key id 0x27371A2C
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-10 0: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
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 [this message]
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=20000709203316.A12712@zero \
--to=thomassr@erols.com \
--cc=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--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).