Assigning "unique name" to "Extraversion" when upgrading Kernal
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Assigning "unique name" to "Extraversion" when upgrading Kernal
Hey gang,
I am upgrading my kernal to 2.6.8.1 and I am following a "How To" manual I found The Link, How to Upgrade Kernal As one of the preliminary steps, it instructs to assign in the "Makefile" of the new linux kernal a new unique name for the field of "Extraversion." I have no idea what this means, but if you scroll down on the link I gave you, you will be able to see what I mean. Can anyone explain this and tell me what to do? Am I just reading to much into this?
Not going to follow the link, but if you makemodifications
to a running kernel the extra-version is a splendid idea.
Assume that you need some particular driver... now, if
you compile the new kernel without it but use the same
name a preserving the driver won't work even if you
keep the original vmlinuz if the driver was a module.
Modules are stored under
/lib/module/<kernel-version>
which is where the extra version comes into the
picture.
If you start with a
2.4.26 and make an extraversion of matthew you'll
have
/lib/module/2.4.26
and
/lib/module/2.4.26-matthew
New Problem: Need to Edit GrUB but SuSE will not let me
As you are all well aware (or maybe you do it another way) after the long compile and module install, I need to modify GrUB to load the new kernel by default. SuSE 9.0, however, will not allow me to so manually, and will not allow me do so via its Yast2 interface. It seems they have locked the "menu.1st" file so that I can not manually edit the file, and frankly I could not navigate Yast2 if my life depended on it (user friendly my *cough*). Any ideas?
Yeah I was in root, Yast2 just hangs up when it tries to save changes, as for manually editing the menu.1st file, which program do you suggest? Do you suggest doing it from terminal?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.