Bug 172 - Separate /boot partition means vmlinux and System.map links aren't set up
Separate /boot partition means vmlinux and System.map links aren't set up
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
5.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1998-11-23 11:37 EST by Michael Meissner
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1998-12-09 17:29:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michael Meissner 1998-11-23 11:37:25 EST
If you have a separate /boot partition (in part to deal with
the BIOS limited range of boot sectors), and you upgrade
to RedHat 5.2 from RedHat 5.1, then the installed will
create the vmlinux and System.map symlinks in the /boot
directory after unmounting the /boot partition, rather
than in the /boot partition file.
Comment 1 Matt Wilson 1998-12-09 17:29:59 EST
The installer does not twiddle with things like that.  The partitions
are mounted before installing RPMS and are not unmounted until reboot.

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