Bug 7663 - custom upgrade ignores package deselection and fails to detect NTFS
custom upgrade ignores package deselection and fails to detect NTFS
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
6.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-12-07 15:55 EST by simra
Modified: 2015-01-07 18:39 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-09 15:25:29 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 simra 1999-12-07 15:55:00 EST
Today I upgraded a dual NT/linux box from RH 6.0 to 6.1.  I was concerned
about the effect lilo would have on the NT boot loader, so I elected to
select the packages to upgrade, and deselected all the kernel packages.
When the upgrade continued, it went ahead and installed the kernel packages
anyway and ran lilo, wiping out the NT bootloader on the master boot
record.
(PS how can I get NT booting again?)
Comment 1 Jay Turner 2000-02-09 15:25:59 EST
The kernel is not something that the user can choose to not upgrade, so . . .
We have removed this selection from the Individual Package Selection screen in
the latest installer.  In addition, we have added the Lilo Config screen to the
Upgrade path so that the user can choose where and whether to install Lilo.
Comment 2 simra 2000-02-10 11:35:59 EST
Are you sure this is wise?  Suppose I have a custom-compiled kernel on my
machine that's newer than the one on the upgrade- I should have the choice to
not install it.

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