Bug 3645 - rc.sysinit tries to load st module even though st is not a module
Summary: rc.sysinit tries to load st module even though st is not a module
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts   
(Show other bugs)
Version: 6.0
Hardware: i386 Linux
medium
low
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-06-22 19:54 UTC by Jay Berkenbilt
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-06-22 21:01:06 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Jay Berkenbilt 1999-06-22 19:54:28 UTC
In RedHat 6.0, it appears that the kernel packages no longer
include st as a module but instead have st compiled into the
kernel.  However, /etc/rc.d/rc.sysinit still runs modprobe
st if /proc/devices indicates the presence of st and
USEMODULES is true.  This is harmless, but does result in an
extra error message at boot time.  I don't know whether it
would be better to throw away the error message or to try to
determine whether st is a module or not.

Comment 1 Bill Nottingham 1999-06-22 21:01:59 UTC
in the latest initscripts in Raw Hide, it won't try to load the module
if it's compiled in into the kernel. We might also start
shipping it as a module again anyways...


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