Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 892 - Suggestion for allowing multiple kernels of the same version
Summary: Suggestion for allowing multiple kernels of the same version
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 5.2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-01-20 15:53 UTC by tschenk
Modified: 2018-07-26 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-01-20 23:07:05 UTC

Attachments (Terms of Use)

Description tschenk 1999-01-20 15:53:37 UTC
We have found a simple mechanism for maintaining multiple
kernels of the same version on a system through a simple
lilo trick.

Say for example, that you have three kernels built from the
2.0.36 source code, but configured differently.  I will call
them 2.0.36.noapm, 2.0.36.apm and 2.0.36.generic.  By using
the append keyword in lilo.conf and a simple script, you can
then have the rc.sysinit script create the appropriate
preferred link, create a link from /boot/vmlinuz to the
current kernel or anything else that you have to do that is
kernel specific.

I will send the script that we use and the cooresponding
lilo.conf via e-mail.

Comment 1 David Lawrence 1999-01-20 23:07:59 UTC
Thank you for the suggestion. It has been noted and will be considered
for upcoming releases.

Comment 2 openshift-github-bot 2018-07-26 15:37:55 UTC
Commit pushed to master at
Merge pull request #910 from wozniakjan/issue892/build/keep_symlinks

Merged by openshift-bot

Note You need to log in before you can comment on or make changes to this bug.