[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: boot-time kernel selection and /System.map mismatch


	This discussion is getting very silly. 
>>"Bill" == Bill Mitchell <mitchell@mozcom.com> writes:

Bill> On 31 Jul 1997, Manoj Srivastava wrote:

Bill> If /vmlinuz is then changed to /vmlinuz-->/boot/vmlinuz-2.0.30,
Bill> but lilo is (for whatever reason) _not_ re-run, then choosing
Bill> "Linux" at the lilo boot prompt will _still_ boot
Bill> /boot/vmlinuz-2.0.27, _not_ /boot/vmlinuz-2.0.30.  Looking in
Bill> /etc/lilo.conf, though, would show image=/vmlinuz, and looking
Bill> at /vmlinuz would show /vmlinuz-->/boot/vmlinuz-2.0.30, but
Bill> `uname -r` would show 2.0.27.

	Could you please at least *LOOK* at kernel-package before
 further discussion? or is this now unrelated to kernel-package and
 you are making general atetements? If kernel-package scripts change
 the links, they also offer to run LILO. You refuse to run LILO,
 despite warnings, you asked for it.

Bill> Neither of these, however, seem to address an expressed need
Bill> from kernel hackers to have several alternative flavors of a
Bill> single kernel version around.

	IMHO, the only way one may have different kernels of the same
 version around is if the kernels do not use modules, or the
 modules are common, since the modules are generally kept under
 /lib/modules/<version>. (Do people really jack module path lookup?) 

Bill> Perhaps the proper way to address this need would be for the
Bill> kernel hackers to modify the SUBLEVEL definition in
Bill> /usr/src/kernel/linux/Makefile to read e.g., "SUBLEVEL =
Bill> 30-speed_hack" (or some such) before building the kernel.  That
Bill> should get the kernel installed as
Bill> /boot/vmlinuz-2.0.30-speed_hack, and get `uname -r` to say
Bill> "2.0.30-speed_hack", and should allow differentiation between
Bill> alternative kernels.  (I haven't tried this because I'm
Bill> currently unable to build kernels, but it looks to me like
Bill> that's the way it would work).

	If this works, then kernel-package shall also cater to it
 seamlessly. If you hack the sublevel, kernel-package will put the
 image in /boot/vmlinuz-2.0.30-speed_hack, and the modules in

	I wonder where uname gets it's information from. The kernel
 may well think that the version is 2.0.30-speed_hack.

>From kernel Makefile:
include/linux/version.h: ./Makefile
    @echo \#define UTS_RELEASE \"$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)\" > .ver
    @echo \#define LINUX_VERSION_CODE `expr $(VERSION) \\* 65536 + $(PATCHLEVEL)\
           \\* 256 + $(SUBLEVEL)` >> .ver
    @mv -f .ver $@

	Hmm. I think I'll try this. If it works, I'll add it to the
 README files. (I expect at least the non-novices to read

 Medicare and Medicaid are the greatest measures yet devised to make
 the world safe for clerks.
Manoj Srivastava               <url:mailto:srivasta@acm.org>
Mobile, Alabama USA            <url:http://www.datasync.com/%7Esrivasta/>

TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .

Reply to: