On Apr 05 2002, Chris Tillman wrote:
> On Tue, Mar 19, 2002 at 04:21:24AM -0300, Rogério Brito wrote:
> > I would like to thank everybody that replied. I have now read
> > a good deal of documentation on generating the bootable CD,
> > but I still have some questions:
> >
> > 1 - After I create a blessed directory (with the -hfs-bless
> > option of mkisofs) containing yaboot, yaboot.conf, vmlinux
> > and a ramdisk suitable, how will OpenFirmware know that
> > upon pressing "c" it will have to load yaboot? Is it
> > because the pair type/creator of yaboot is boot/UNIX?
> >
> > 2 - is the ofboot.b file necessary for booting?
>
> Did you ever figure this all out, and do you have a working script?
Hi there, Chris.
I'm sorry for this taking so long, but only now I had the
opportunity to fiddle with this once more.
The answer is "well, more or less".
First of all, ofboot.b _is_ necessary for booting and it has
to have the proper type/creator code. It is a (text) file
containing an open firmware script. It is this file that tells
OpenFirmware to load yaboot for the boot process to continue.
I'm unfortunately still not able to create a bootable CD and I
don't know why.
Here is what I am using (and I would appreciate any help other
people can give) to create the cd:
mkisofs -hfs -map src/hfs.map -part -hfs-bless ./ppc/ -r -o cd.iso
./ppc/
The hfs.map is taken from the debian-cd project. The ppc
directory is the contents of the cd and here is what it looks
like:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
dumont:/tmp> ls -lAF ppc/
total 5100
-rw-rw-r-- 1 rbrito rbrito 3573285 Apr 20 21:11 linux.bin
-rw-r--r-- 1 rbrito rbrito 219 Apr 20 21:14 ofboot.b
-rw-rw-r-- 1 rbrito rbrito 1474560 Apr 20 21:11 root.bin
-rw-rw-r-- 1 rbrito rbrito 150020 Apr 20 21:13 yaboot
-rw-rw-r-- 1 rbrito rbrito 235 Apr 20 21:15 yaboot.conf
dumont:/tmp>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
All binary files were taken from the current boot-floppies, to
make my proof-of-concept CD. The only files that I changed
were ofboot.b and yaboot.conf:
ofboot.b:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
<CHRP-BOOT>
<COMPATIBLE>
MacRISC
</COMPATIBLE>
<DESCRIPTION>
Rescue CD, based on Debian's debian-cd
</DESCRIPTION>
<BOOT-SCRIPT>
" screen" output
load-base release-load-area
boot cd:,\yaboot
</BOOT-SCRIPT>
</CHRP-BOOT>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
yaboot.conf:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
## This yaboot.conf is for CD booting only, do not use as reference.
# It is important not to have a comma after cd:
device=cd:
default=install
timeout=100
image=/linux.bin
label=linux
initrd=/root.bin
initrd-size=8192
read-only
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
My problem is that, for some reason, yaboot is not being
automatically loaded when I press "c" after the chime. If, on
the other hand, I enter OF and type: "boot cd:,\yaboot", then
everything works fine as I would expect (and, the Debian
install starts).
So, here is where I am, and I'd love to know what I'm doing
incorrectly here. Perhaps, I'm telling mkisofs to bless the
wrong path?
I've tried many variations (my first attempts were to leave
everything well organized and put all boot related files in a
boot directory inside the CD, but it didn't work also).
Any help here is more than welcome.
Hope this helps you to help me, Roger...
P.S.: I mounted the generated CD image with hmount and saw that all
files have the (seemingly) correct types/creator whatever.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rogério Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
