From: Michel Lanners <mlan@cpu.lu>
To: bierman@apple.com
Cc: erbenson@alaska.net, linuxppc-dev@lists.linuxppc.org
Subject: Re: New booter (about quik)
Date: Thu, 16 Sep 1999 09:42:09 +0200 (CEST) [thread overview]
Message-ID: <199909160742.JAA00362@piglet.cpu.lu> (raw)
In-Reply-To: <v0313030ab405d00a6b8a@[17.202.21.235]>
On 15 Sep, this message from Peter Bierman echoed through cyberspace:
>>the bootblock method works on most OF machines since there are plenty
>>of people using quik to do it, its the newworld machines that are
>>either different or broken, however they have a flashable ROM so
>>apple can fix this oversight.
>
> I haven't used quik, but I'm guessing it patches OF so that OF can read a
> booter somewhere? This would be similar to System Disk for OldWorld
> machines, which patches OF, and then points it at a loader partition which
> contains an expanded XCOFF binary (the same binary as the booter, just in a
> format that OldWorld OF can load and execute.)
No, quik is a two-part boot process. quik installs a first-stage boot
loader in the boot block of a disk partition. I admit I am not sure if
this partition needs to be a HFS partition, or if it can be an ext2
partition... (Paul?)
The first-stage then loads the second-stage based on its physical block
assignment on disk, not based on any filesystem code. It's only the
second-stage that includes filesystem code, and which loads the kernel
from the root ext2 partition.
Apart from the HFS partition that might be needed for the bootblock
installation (i.e. it can be a partition as small as your tools allow
you to create it), I think this is a clean boot method... the
second-stage can include any filesystem code you want, and you can
update that part independantly of all the others.
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-09-16 7:42 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <v04011701b404e6cd4493@[199.174.193.101]>
[not found] ` <v04210105b404ed46f043@[192.168.0.1]>
1999-09-15 9:39 ` New booter Benjamin Herrenschmidt
1999-09-15 9:58 ` Ethan Benson
1999-09-15 17:53 ` Kevyn Shortell
1999-09-15 18:03 ` David A. Gatwood
1999-09-15 22:40 ` Ethan Benson
1999-09-15 22:56 ` Tom Rini
1999-09-16 7:50 ` New booter-New world Sean
1999-09-16 11:46 ` David Riley
1999-09-16 17:05 ` Kevyn Shortell
1999-09-16 23:46 ` Sean
1999-09-15 23:03 ` New booter Dan Burcaw
1999-09-15 22:37 ` Ethan Benson
1999-09-15 23:02 ` Peter Bierman
1999-09-16 3:18 ` Ethan Benson
1999-09-16 3:37 ` David D. Kilzer
1999-09-15 23:10 ` Wolfgang Denk
1999-09-16 8:16 ` Geert Uytterhoeven
1999-09-16 8:38 ` Ethan Benson
1999-09-16 10:47 ` Benjamin Herrenschmidt
1999-09-16 17:01 ` David A. Gatwood
1999-09-16 18:48 ` Michel Lanners
1999-09-15 23:15 ` erik cameron
1999-09-16 3:50 ` Ethan Benson
1999-09-16 4:21 ` Dan Burcaw
1999-09-15 17:22 ` David A. Gatwood
1999-09-15 22:41 ` Ethan Benson
1999-09-15 17:39 ` Peter Bierman
1999-09-15 22:27 ` Ethan Benson
1999-09-15 22:47 ` David N. Welton
1999-09-15 23:01 ` Dan Burcaw
1999-09-15 22:48 ` Peter Bierman
1999-09-15 23:19 ` Ethan Benson
1999-09-15 23:48 ` Tom Rini
1999-09-16 0:23 ` David A. Gatwood
1999-09-16 4:02 ` Sean
1999-09-16 5:42 ` David A. Gatwood
1999-09-16 3:59 ` Ethan Benson
1999-09-16 7:42 ` Michel Lanners [this message]
1999-09-17 0:32 ` New booter (about quik) Paul Mackerras
1999-09-17 1:46 ` Ethan Benson
1999-09-17 15:06 ` Benjamin Herrenschmidt
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=199909160742.JAA00362@piglet.cpu.lu \
--to=mlan@cpu.lu \
--cc=bierman@apple.com \
--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).