Bug 892 - Suggestion for allowing multiple kernels of the same version
Summary: Suggestion for allowing multiple kernels of the same version
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
(Show other bugs)
Version: 5.2
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
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:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-01-20 23:07:05 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


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 https://github.com/openshift/source-to-image

https://github.com/openshift/source-to-image/commit/bc5fa283a2c6c6eb815f2d0e370198f53a770cc0
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.