Bug 1990 - Linuxconf refuses to allow /dev/hde as boot device for LILO
Linuxconf refuses to allow /dev/hde as boot device for LILO
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
6.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-04-04 19:55 EDT by Adam Thompson
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-04-08 15:16:58 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)

  None (edit)
Description Adam Thompson 1999-04-04 19:55:51 EDT
Linuxconf refuses to allow /dev/hde as boot device for LILO.

Under Config->Boot Mode->Lilo->LILO defaults, simply
bringing up the dialog and selecting Accept (with "Install
boot sector on" *alreay* set to /dev/hde) produces the
following error:

"Invalid partition or device for boot sector installation"

Unfortunately, I really do boot off /dev/hde -- it's a
Promise Ultra/33 IDE PCI controller card.
Apparently /dev/hd[a-d] are reserved for ide0/1, DESPITE
the fact the the onboard CMD640 interface is turned off in
the BIOS.  [Despite being turned off, the PCI bus scan
still finds it.]

Anyway, based on what I can figure out, there must be
something hardcoded to prevent anything beyond /dev/hd[a-d]
from beins used.  Running and configuring LILO by hand
for /dev/hde works just fine.  Incidentally, the RH5.9
installer also dealt with /dev/hde correctly.  Just
linuxconf that breaks :-(
Comment 1 Michael K. Johnson 1999-04-05 16:22:59 EDT
Added Jacques to CC line
Comment 2 Michael K. Johnson 1999-04-05 16:38:59 EDT
Jacques, what would you think about changing this from an error
to a warning message?  We still want to warn "Joe Average" that
/dev/hdb is not a very good place to put a master boot record,
as a general rule, but a warning would suffice, and would let
folks like this use their relatively unusual configurations
without linuxconf getting in their way...

------- Email Received From  Jacques Gelinas <jack@solucorp.qc.ca> 04/06/99 22:57 -------
Comment 3 Michael K. Johnson 1999-04-08 15:16:59 EDT
Should be fixed in 1.14r3

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