![](https://seccdn.libravatar.org/avatar/0adfef0e7580fa676e2f7258dbd597ea.jpg?s=120&d=mm&r=g)
Thanks for the info. And yes I understand the kernels are experimental, but I am testing a feature that is broken in the released kernel. I understand it is fixed in the experimental kernels. The machine is purely a test machine, but I hope the upgrade works because I don't want to have to re-install. Greg ===== Greg Freemyer Internet Engineer Deployment and Integration Specialist Compaq ASE - Tru64 Compaq Master ASE - SAN Architect The Norcross Group www.NorcrossGroup.com
On Wednesday 15 May 2002 18.30, Greg Freemyer wrote:
I have just downloaded a kernel from ftp://ftp.suse.com/pub/people/mantel/next/RPM/
These are experimental kernels. Use with caution. Don't use at all on production systems.
If this were a normal package I would use rpm to install it with no hesitation.
Being the kernel, I want to make sure I don't kill my machine.
What are the recommended steps for installing the above, and for booting from the current kernel if I have problems.
It's a little tricky, since they're both 2.4.18. They will want to use the
same modules directory. Normally, when you go to a different revision number, you'd do
mv /boot/vmlinuz.suse /boot/vmlinuz.suse.bak mv /lib/modules/<current version> /lib/modules/<current version>.bak rpm -Uvh k_deflt.rpm (or whatever the filename was) mv /boot/vmlinuz.suse.bak /boot/vmlinuz.suse mv /lib/modules/<current version>.bak /lib/modules/<current version> /sbin/mk_initrd /sbin/lilo
When you upgrade to a later build of the same revision level, there is no easy way to keep the old and the new modules directory at the same time. As far as I can see, you're forced to recompile one or the other and set a different
version lable
regards Anders
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com