SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You could open your file browser, find the patch you have downloaded, and click on it. You should be presented with the option to install via YaST. YaST will install the patch, and run any config file updates that are necessary.
However, it the kernel number changes as a result of the patch, I have three questions that I do not know the answers.
a) does YaST make a new compressed kernel image (bzImage)?
b) does YaST put a copy of that image in /boot as vmlinuz-<kernel number>?
c) does YaST make the necessary changes to /boot/grub/menu.lst?
If a) is NO, then so are b) and c). In which case, you will boot into the unpatched kernel image in boot, instead of the patched kernel.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Original Poster
Rep:
Quote:
Originally Posted by bigrigdriver
You could open your file browser, find the patch you have downloaded, and click on it. You should be presented with the option to install via YaST. YaST will install the patch, and run any config file updates that are necessary.
Ummm. It is a kernel rpm not a patch to be applied to the sources. So it would have to be handled like any other piece of software I'd install (I'd guess). I'll click on it and see. BTW "yast -i <the-rpm>" does just that, i.e. install and run the necessary configs.
Quote:
Originally Posted by bigrigdriver
However, it the kernel number changes as a result of the patch, ...
It does.
Quote:
Originally Posted by bigrigdriver
...I have three questions that I do not know the answers.
a) does YaST make a new compressed kernel image (bzImage)?
I'd assume, that the bzImage is in the rpm (which is only of the size of 20 MB)?!?
Quote:
Originally Posted by bigrigdriver
b) does YaST put a copy of that image in /boot as vmlinuz-<kernel number>?
That would be the proper way of installing the kernel-"program"...
Quote:
Originally Posted by bigrigdriver
c) does YaST make the necessary changes to /boot/grub/menu.lst?
Good question but easy to check .
Quote:
Originally Posted by bigrigdriver
If a) is NO, then so are b) and c). In which case, you will boot into the unpatched kernel image in boot, instead of the patched kernel.
That makes the whole difference if it changes the boot loader, and the other stuff.
(but from my experience, suse rpms contain scripts to change the boot loader.
when creating a custom kernel and using "make rpm"
everything is done execpt making the boot ram disk and the boot loader.)
oh, and it doesn't really "change on the fly." The new kernel, in order to activate, must be rebooted.
Last edited by lambchops468; 04-25-2008 at 04:52 PM.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Original Poster
Rep:
It is from Frank Seidel, a guy who works for SuSE / Novell Germany. So it does have an optimistic outlook. I'll try soonest (forgot my memory stick over the weekend ).
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Original Poster
Rep:
Grrr. The boot partition is too small, the new kernel needs a little more than 8 MB. I'll have to get a Knoppix CD and move the other partitions and resize /boot. I'll be back after that...
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Original Poster
Rep:
Solved
Okay, I moved them (why does Gparted copy twice with differing block sizes?!?) and installed the kernel-rpm via one click on it in Konqueror -- and lo and behold everything went well.
YAST even changed the entries in menu.lst (so GRUB didn't find the older instances of SuSE 10.0 -- hrmmph) and told me to reboot. After that uname -a showed the new kernel version (and the font in the GRUB boot menu was changed). So I edited menu.lst and all is well.
This is a HowTo for building kernel-rpms on and for SuSE systems for those who are interested:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
.
.
).
