Re: G4 Cube FWUpdate -->boot fiasco
Quoting Ethan Benson (erbenson@alaska.net):
> On Thu, Jun 07, 2001 at 04:18:00AM +0200, Karl-Heinz Haag wrote:
>
> if you have a newworld your best way to fix that right now is:
>
> apt-get --purge remove quik
okay
> you should use make-kpkg from the kernel-package to build a kernel
> .deb its much simpler and straighforward then all of this.
I'll do so.
I suppose this home-brewn kernel image will not ask whether activating a
boot block with 'quik' as the image did I fetched with apt-get yesterday...
> > How do you activate a boot block overtaking the new kernel file?
> > Is it sufficent to cp System.map and new-built kernel file to /boot/...
> > and linking /vmlinux to it?
>
> yes, but kernel-package makes this eaiser.
>
> > Commandig mkofboot and/or ybin after that?
> update /etc/yaboot.conf and rerun ybin. just like you would do on x86
> with lilo.
All clear to me so far.
Next question: Creating a boot 'fallback' to the new kernel?
On i386 you can stop the lilo bootup by pressing the 'shift' key, and
'Tab' shows boot alternatives you created in /etc/lilo.conf. With this
you can boot different Linux kernel images and other OS on the HDD.
How enabling to boot the new kernel by default and -by choice- elder
ones as well? The new one could be broken or bad configured....
My situation now is that I'm booting into Debian via OF:
boot hd:9,yaboot
Where can I find some stuff to read about that besides man yaboot/ybin?
Karl-Heinz
Reply to: