linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Ethan Benson <erbenson@alaska.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: LinuxPPC and Pismo Powerbook
Date: Wed, 29 Mar 2000 15:58:34 +0200	[thread overview]
Message-ID: <20000329155834.A30559@suse.de> (raw)
In-Reply-To: <20000329043355.A27338@plato.localdomain.local>


On Wed, Mar 29, Ethan Benson wrote:

> On Tue, Mar 28, 2000 at 11:03:29PM -0800, Henry Worth wrote:
>
> > > * STEPS :
> > > 1.  partitioned the HD into three partititions: MacOS, Linux, Swap
> >
> > I'd strongly recommend a small HFS boot partition (~32MB).
>
> 32MB??  lord no, 800K is more then enough for yaboot.

What about different kernel images? 32 MB is a good value.
And it is more secure, even for older Macs with BootX.
I don't trust the hfs.o

> this partition should also be given a partition type of
> Apple_Bootstrap to prevent Macos from mounting, and subsquently
> screwing it up.  (it removes the `blessing' from anything that might
> not be a valid macos system folder)

There is nothing on that partition that can be screwed up and the user
can change the yaboot.conf and the os-chooser file from the MacOS side.

I had never problems with my faked system folder, I move it around, to
CDs, to netatalk servers and where ever I want. This can be a "feature"
of OS9 that it doesn't remove the information, I don't know.

What makes this blessing so special??

I have the Finder from MiBoot.smi, I changed the type/creator to
FNDR/MACS. The System is the same from MiBoot, unchanged. There is a
faked RomFile = yaboot and its .conf. Thats all.

You have to move the Finder file out of that folder and move it back
onto the closed folder icon and it is bootable. All you have to do now
is to open the control panel Startup volume and you are done.

I don't see the problem. What we really need is an app that creates the
os-chooser file, what we need is the partition number and the path to a
bootable SCSI device. I could do that from the Linux side via a bootable
CD, but it would be nice to do it with a Mac application.

Gruss Olaf

--
 $ man 1 current_release

BUGS
       Users never read manuals...

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

  reply	other threads:[~2000-03-29 13:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20000328115126.003377@mailhost.mipsys.com>
2000-03-28 15:49 ` LinuxPPC and Pismo Powerbook Min Shin (CS)
     [not found]   ` <38E1AAC1.A8999A9B@ncal.verio.com>
2000-03-29 13:33     ` Ethan Benson
2000-03-29 13:58       ` Olaf Hering [this message]
2000-03-29 14:05         ` Ethan Benson
2000-03-29 16:50         ` Benjamin Herrenschmidt
2000-03-29 19:42           ` Olaf Hering
2000-03-29 16:47 Benjamin Herrenschmidt
2000-03-29 19:47 ` Olaf Hering
  -- strict thread matches above, loose matches on Subject: below --
2000-03-29 19:20 Henry A. Worth
2000-03-30  3:36 ` Ethan Benson
2000-03-30  4:12   ` Ramprasad Rao
     [not found]   ` <38E2DE84.72E7297A@dana.ucc.nau.edu>
2000-03-30 12:24     ` Olaf Hering
2000-03-30 18:31 Henry A. Worth
2000-03-30 20:07 Henry A. Worth
2000-03-31  4:47 ` 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=20000329155834.A30559@suse.de \
    --to=olh@suse.de \
    --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).