Bug 3119 – Upgrade doesn't tell you where it has put the kernel

Bug 3119 - Upgrade doesn't tell you where it has put the kernel

Summary:	Upgrade doesn't tell you where it has put the kernel

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	installer (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	alpha Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-05-28 09:04 EDT by rhbugs
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-06-02 18:42:39 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description rhbugs 1999-05-28 09:04:40 EDT

On upgrading a RH5.2 alpha system to RH6.0 the installer
had created a new kernel which it had put on the system
in the /boot directory.  However it didn't tell me
what the path name of the new kernel was and thus I didn't
know what to tell my MILO.

(The problem was compounded by the fact that the old kernel
- 2.2.1 - hung while running some of the daemons the upgrade
had installed)

Comment 1 David Lawrence 1999-06-02 18:42:59 EDT

We should probably have some message pop up during the alpha installer
stating the new path for booting in milo. Until that time, you can use
ls in milo to get directoy listings on you drives or even better is to
upgrade your current milo to the version provided on the 6.0 CD that
allows for a few new features. These are explained at
http://www.redhat.com/corp/support/manuals/RHL-6.0-Manual/alpha-inst/booklet/doc010.html#s1.5.5.1.
Thank you for the suggestion.

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