linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Cc: Ethan Benson <erbenson@alaska.net>
Subject: Re: Multi-boot advice.
Date: Fri, 07 Jul 2000 09:46:04 +0100	[thread overview]
Message-ID: <200007070846.JAA05142@hyperion.valhalla.net> (raw)


On Fri, Jul 7, 2000 Ethan Benson  wrote:
> On Fri, Jul 07, 2000 at 07:52:10AM +0100, Iain Sandoe wrote:
>> On Fri, Jul 7, 2000 Ethan Benson wrote:
>> > On Thu, Jul 06, 2000 at 09:38:38AM +0100, Iain Sandoe wrote:
>> >> Yea Hey first to Apple Drive setup (which at least these days will allow
>> >> most stuff to be set up) - and then to pdisk - to check it out.
>> >
>> > just don't create any linux partitions with apples drive setup, it
>> > won't work.  instead add up the sizes of all the planned linux
>> > parittions and create a placeholder HFS partition with apple drive
>> > setup, then delete it with pdisk and populate the freed space with the
>> > linux and bootstrap partitions.
>>
>> This is interesting.  I've seen (several times) the comment that the Apple
>> Drive Setup tool doesn't work for Linux.
>>
>> However, it certainly did for me (on the Lombard & on a 9600/233)... under
>> what circumstances does it fail?
>
> every time i tested it the following occured:
>
> * drive setup crashed
> * the partition tables were corrupt.
>
> its just good policy to use the native fdisk to create an OS'es
> partitions, on intel we must use DOS fdisk to create DOS/Win*
> partitions and linux fdisk for linux partitions, same with OpenBSD,
> FreeBSD etc.  powerpc is no different.

This is OK for the people on this list.  We are happy with text-only command
line interfaces (hell, I once wrote an entire app in assembler... but I
wouldn't want to do that ever again.)

However, if we want Linux to be extended to a wider audience the kind of
intuitive set up tool (like drive set-up) is going to be essential.

Someone should tell Apple if there's a problem - they seem to be willing to
support (at least) the existence of Linux & other OSs - unlike certain other
companie$

Iain.

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

             reply	other threads:[~2000-07-07  8:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-07  8:46 Iain Sandoe [this message]
2000-07-07  9:11 ` Drive Setup (was Multi-boot) Hollis Blanchard
2000-07-07 12:39   ` Drive Setup Hollis Blanchard
  -- strict thread matches above, loose matches on Subject: below --
2000-07-07  6:52 Multi-boot advice Iain Sandoe
2000-07-07  4:00 ` Nelson Abramson
2000-07-07  7:08 ` Ethan Benson
     [not found] <200007052323.AAA07099@hyperion.valhalla.net>
2000-07-05 20:40 ` Nelson Abramson
2000-07-05 23:30 ` Dan Foster
2000-07-06  9:37   ` Holger Bettag
2000-07-06  8:39 ` Olaf Hering
2000-07-06 14:38 ` Matt Brubeck
2000-07-06 14:57 ` Matt Brubeck
2000-07-07  5:41   ` Ethan Benson

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=200007070846.JAA05142@hyperion.valhalla.net \
    --to=iain@sandoe.co.uk \
    --cc=erbenson@alaska.net \
    --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).