Mailinglist Archive: opensuse (3031 mails)

["Rajko M." <rmatov101@xxxxxxxxxxx>]

On Thursday 07 February 2008 06:33:20 pm Carlos E. R. wrote:
> The Thursday 2008-02-07 at 09:32 -0800, Vahe Avedissian wrote:
> > I booted from the 64b installation DVD and chose boot installed system,
> > and that only tried to boot the "bad" kernel (i.e. system hangs with same
> > errors).
>
> No, you need to start the live system in the rescue dvd, mount your root
> filesystem, and chown to it.
>
> As somebody else wrote (Anders Johansson):
>
> ] In the past few releases, you can't just do a chroot from the rescue
> ] system. You have to (assuming the root partition is mounted on /mnt)
> ]
> ] mount -o bind /proc /mnt/proc
> ] mount -o bind /sys /mnt/sys
> ] mount -o bind /dev /proc/dev
> ]
> ] then you can do the chroot
>
> Once you do the chroot, you can fire up yast and force a reinstall of the
> kernel.
>
> In theory, the automatic rescue thing should work, but... :-?
>
> > Is there a way to configure yast to not delete an old kernel when a new
> > one is installed?
>
> No.

The easiest way for me is to copy old kernel modules in /lib/modules to safe 
place, the same with /boot and restore what I want after update and before 
reboot. Add old kernel to /boot.grub/menu.lst and than reboot. I actually 
have symlinks vmlinuz-old and initrd-old so I update them insted of menu.lst. 
Than everybody is happy, YaST has new kernel and I have old. 


-- 
Regards, Rajko.
See http://en.opensuse.org/Portal
-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx