Re: How to configure yaboot for initrd? I need help...
> > And the yaboot man pages explicitly say not to do that, ever ... Please
> > don't advertise your hack for the general public (few people know what
> > 'blessing' the yaboot image means, or what the funky hd:,\tbxi does, for
> > instance).
>
> I think you mean "hd:,\\:tbxi", but yes, definitely agreed, since MacOS
Yep, that's it - couldn't look it up but you got the gist.
> very much likes to unbless partitions that don't belong to it - having a
> rash of "I can't boot Linux on my Power Mac! I did [blah foo bar], make
> it work!" is what made Ethan Benson say "don't install yaboot on a MacOS
> partition, OR ELSE" and other such stern warnings.
The OP wasn't clamoring "make it work", rather offering the "mount and
fix" suggestion for disaster recovery. As a last resort it's definitely
OK. But you should have multiple easier ways for recovery:
<FAQ>
* NEVER touch the Label=linux / linux.old sections. Rather, add new
sections to play around. You can use the same kernel/initrd in the
experimental sections even. I haven't managed to mess up yaboot.conf to
the point that it wouldn't even boot the default sections anymore, so
that should help in most cases.
* ALWAYS have a bootable Linux recovery CD to mount and fix your
installation the right way. The install CD should be enough for that if
you know how to run binaries off the mounted /target fs. Know your
partition scheme to pick the right partition to work on.
* Keep a working kernel and BootX on the MacOS side, or even kernel and
yaboot; you should be able to run that copy of yaboot from OF by giving
the full path, like hd:10,\linux\recovery\yaboot ... Again, know your
partition layout. BootX won't work for OS X IIRC, and I haven't tried
booting yaboot off an OS X partition.
Last of all, manually mount and edit your bootstrap partition - you will
have to know the partition number for that, and that'll help booting the
now de-blessed yaboot from OF.
</FAQ>
Re: ybin code to parse the yaboot.conf syntax: this should in fact be sent
to the Debian package maintainer for yaboot.
Michael
Reply to: