Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 892 - Suggestion for allowing multiple kernels of the same version
Suggestion for allowing multiple kernels of the same version
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-01-20 10:53 EST by tschenk
Modified: 2018-07-26 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-01-20 18:07:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description tschenk 1999-01-20 10:53:37 EST
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 18:07:59 EST
Thank you for the suggestion. It has been noted and will be considered
for upcoming releases.
Comment 2 openshift-github-bot 2018-07-26 11:37:55 EDT
Commit pushed to master at https://github.com/openshift/source-to-image

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.