Re: About yabootconfig
Hello, Nic
not sure if this helps, but I think installing the kernel-image.deb
file (created with make-kpkg kernel-image) just moves the new vmlinux
kernel to /boot/vmlinux-2.X.XX (along with the corresponding config
file) then updates the symlink between /vmlinux and the current kernel
(i.e. /vmlinux ---> /boot/vmlinux-2.X.XX, the new kernel).
thanks for getting the trouble to drop me some advice:
I new about the symlink and how to restore manually the whole thing in
case we are not happy with a working kernel (and linuxbox).
Question was really how to operate at the early stage, prior to booting
into the kernel as my computer was freezing solid just after booting.
As a matter of fact I have tried to check out also your suggestion only
to find out that most probably you are not using a new-world mac...
On a recent (made after 2000) applemac, Bootstrap is controlled through
OpenFirmware and I guess it is possibile to manually point directly to
a working kernel (not so sure yet) in fact Yaboot is very cleverly
using a combination of bootstrap, OpenFirmware and linux to get the job
done.
I got some useful info by searching google for the yaboot how-to and
will keep it on my desk as the key tool in future emergency case,
luckily I got also another workaround to solve the problem on my
triple-booting iMac:
Today I had lost keyboard use when in Linux.
I went back into OSX by holding pressed the X on my keyboard during
reboot and was able to cancel the /vmlinux symlink and rename the
/vmlinux.old into /vmlinux. This was possible as I had direct access to
my ext2 Linux partition from OSX thanks to a very useful fs utility
that works under OSX and enables mounting on the finder desktop a ext2
partition.
As for the remaining part of your post, I think make-kpkg works just
great: long life to it!
If I where you, I would trust more on the Debian (stable) distribution
and the make-kpkg command as after all it doesn't really change much in
your installation. :-))
Chances are that apt-get sometime is much more dangerous especially
when it comes to libraries and other important packages coming from
unstable or testing.
But, of course, this is my personal opinion as I should always keep in
mind that:
"when the going gets tough...."
Happy computing!
Pieter
Reply to: