To what Philipp wrote I would add: Include the what, when and how for System.map, and for that file /boot/map. I haven't found a description of lilo that shows how to designate a specific system map. When I first installed SuSE 7.1 I saw vmlinuz.suse System.map-2.2.18 I haven't removed them because I don't know if the boot floppy uses them or not, but I have taken references to vmlinuz.suse out of lilo. When I recompiled the kernel I copied 'System.map' and my new kernal as vmlinuz-jlk to the /boot dir. But, NO reference is made to 'System.map' in lilo.conf. so I don't know how SuSE referenced System.map-2.2.18 and I also don't know if my System.map is being used. And I have no clue as to what /boot/map does, although it is stampted with a date-time indentical to my last compiled kernel. Having a better explaination of the whys, whens and hows of the initrd file, and what to include in it when one uses mk_initrd. The explaination in the SuSE manual assumes the reader has a lot of background knowledge that it appears only a kernel coder would possess. JLK On Saturday 10 March 2001 09:23, you wrote:
Philipp Thomas wrote:
Nope, you can't. Modules have the version of the kernel they're compiled for hardcoded into them. This will necessitate to load them with the -f flag for different kernels.
This is all rather confusing which leads me to my question. I have bought every version of SuSE since 6.2. Though just beginning I was able to easily compile the kernel with the instructions in the SuSE manual. Now it seems that with the SuSE 7.1, simplicity is no longer the case. The SuSE 7.1 manual hasn't changed much in the kernel chapter area but compiling has changed a lot. I was hoping to find my answers in this group but I only see that there are other people who are confused too.
I found under the /usr/src tree there are three sources for /linux-2.2.18, /linux-2.4.0-4GB and /linux-2.4.0.SuSE. The /linux symbolic link points to /linux-2.4.0.SuSE yet there isn't much of anything there. Under /lib/modules I find /2.2.18 and /2.4.0-4GB. What is really strange is that the only source branch that actually contains source is the /linux-2.4.0.SuSE while there is no corresponding /lib/modules. It seems that none of them are complete.
Worse yet is that the graphical lilo presents 3 options that arent't obvious in their matching the 3 kernel sources. instead of linux, linux 2.4 and suse, why not present names that actually correspond with the kernels.
IT seems that SuSE didn't accomodate the 3 kernels in the SuSE manual. Searching the SuSE support database didn't help me either. Would you or some other SuSE person please provide a simple addendum to the SuSE 7.1 manual that covers dealing with the 3 kernels with information such as: 1. files/packages needed for each kernel build 2. do I change the /usr/src/linux symbolic link to the kernel that I intend to build? 3. any other variations from the standard SuSE 7.1 manual procedure for building a kernel
I have seen several threads on this subject including this one but none of them have really made the solution any more clear for me. If a beginner like me can learn to build kernels in previous versions, it can't be a difficult process and I would really appreciate SuSE's to make it simple once again. I am really impressed with 7.1 in spite of these small errors and I hope that SuSE won't mind making this more clear to its fans.
Damon Register