Bug 82149 - kernel-2.4.20-2.21 rpm scripts assume use of kernel with software raid compiled in
kernel-2.4.20-2.21 rpm scripts assume use of kernel with software raid compil...
Status: CLOSED RAWHIDE
Product: Red Hat Raw Hide
Classification: Retired
Component: mkinitrd (Show other bugs)
1.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Erik Troan
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-18 02:51 EST by Nathan G. Grennan
Modified: 2007-04-18 12:50 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-01-20 16:22: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 Nathan G. Grennan 2003-01-18 02:51:45 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20021216

Description of problem:
I downloaded kernel-2.4.20-2.21 and installed it. During the install process I
got the error message below. I am running a custom recompile of
kenrel-2.4.20-2.12 without raid support.

awk: cmd. line:2: fatal: cannot open file `/proc/mdstat' for reading (No such
file or directory)


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Boot kernel without raid support
2. Install kernel-2.4.20-2.21
3.
    

Actual Results:  awk: cmd. line:2: fatal: cannot open file `/proc/mdstat' for
reading (No such file or directory)


Expected Results:  no error message

Additional info:

RedHat seems to be getting pretty bad about assume use of their kernel, and even
their compile options. I think this is something that should be recongized and
stopped.

On a bright note RedHat does seem to be willing to fix such assumptions when
they come up.
Comment 1 Bill Nottingham 2003-01-20 16:22:22 EST
Fixed in 3.4.36-1.

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