Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 79003 - rc.sysinit never runs isapnp as ! -f /proc/isapnp is false
rc.sysinit never runs isapnp as ! -f /proc/isapnp is false
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-12-04 10:34 EST by James T Evans
Modified: 2014-03-16 22:32 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-12-04 10:34:44 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description James T Evans 2002-12-04 10:34:35 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.0.1) Gecko/20020823

Description of problem:
I rely on isapnp to configure an ISA ISDN card. rc.sysinit contains the check 

"if [ -x /sbin/isapnp -a -f /etc/isapnp.conf -a ! -f /proc/isapnp ] then" ..... 
run isapnp if $PNP = yes. 

/proc/isapnp always seems to be there at the time this runs, so my isdn hardware
was never configured and the later "isdn start" would fail to find the card.

I removed the last term, checking for ! /proc/isapnp and the problem is resolved
though I am unclear as to the implications of this or why this has caused no-one
else a problem! maybe /proc/isapnp is not normally created at this time.

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

How reproducible:

Steps to Reproduce:
1.err start the system??

Additional info:
Comment 1 Bill Nottingham 2002-12-04 12:29:12 EST
Running the userland isapnp tools while the kernel mode ISAPnP support
(/proc/isapnp) is active can be dangerous in some cases; that's why the check is

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