linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis@amulet.co.jp>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: linuxppc-dev@lists.linuxppc.org, Benjamin Herrenschmidt <bh40@calva.net>
Subject: Re: RFC: Changing default partition type for linux/ppc
Date: Fri, 07 Jul 2000 21:49:28 +0900	[thread overview]
Message-ID: <3965D1D8.C7B9F28E@amulet.co.jp> (raw)
In-Reply-To: 200007071125.MAA02302@hyperion.valhalla.net


Iain Sandoe wrote:
>
> > Currently, the default partition type used by Linux/PPC on mac partition
> > maps is Apple_UNIX_SVR2. This is historically the type used by Apple's A/
> > UX for its own partitions. However, I don't like it since it gives no
> > indication on the type of filesystem on the partition, and I see no
> > reason to keep it.

[snip]

> What chance of getting Apple to support this move?

I would estimate the odds are somewhere between slim and none. Feel free
to email leadership@apple.com.

Of course I think we all know it's not that important either. Drive
Setup's Linux support came a few years late, and still is lacking a bit.
With Apple's new interest in Unix it's possible they might care (but
also possible that they'd have no interest in interoperating with
inferior Unices ;). Of course, I imagine they're pretty busy with their
own Unix - not much time to worry about working with other people's.

> > 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 think "Linux" and "Linux_swap" would be a good idea, especially since
some ext2 alternatives seem to be getting closer.

> What prospect of sharing swap space between MacOS X and linux in dual/multi
> boot machines?

I don't know the details, but I know that you must run mkswap on a new
swap partition. Since I don't imagine any particular effort has been put
in to keeping Linux and BSD mkswap's compatible, I doubt it would be
possible.

-Hollis

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-07-07 12:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-07 11:22 RFC: Changing default partition type for linux/ppc Iain Sandoe
2000-07-07 12:49 ` Hollis Blanchard [this message]
2000-07-07 14:13   ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2000-07-07 10:59 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
2000-07-10  1:49           ` Matt Brubeck

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=3965D1D8.C7B9F28E@amulet.co.jp \
    --to=hollis@amulet.co.jp \
    --cc=bh40@calva.net \
    --cc=iain@sandoe.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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).