Bug 80778 - Can't run mknod when booted from Phoebe install CD
Can't run mknod when booted from Phoebe install CD
Status: CLOSED RAWHIDE
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda (Show other bugs)
phoebe
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Mike McLean
:
: 80372 (view as bug list)
Depends On:
Blocks: 79578
  Show dependency treegraph
 
Reported: 2002-12-31 03:16 EST by Mark McClelland
Modified: 2007-04-18 12:49 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-01-02 18:01:03 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 Mark McClelland 2002-12-31 03:16:10 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021203

Description of problem:
When booted from Phoebe CD #1 (in rescue mode or by switching to tty0 during
install), the "mknod" command doesn't work. The problem seems to be a missing
Python component.


How reproducible:
Always


Steps to Reproduce:
1. Boot from install CD into rescue mode
2. Proceed through various anaconda screens until you get to a shell propmt
3. Run mknod
    

Actual Results:  
-/bin/sh-2.05b# mknod
Traceback (most recent call last):
  File "/usr/bin/mknod", line 4, in ?
    import isys
ImportError: No module named isys


Expected Results:  When booted from RH 8.0 install CD:
-/bin/sh-2.05b# mknod
usage: mknod <path> [b|c] <major> <minor> or mknod <path>
Comment 1 Jeremy Katz 2002-12-31 10:53:49 EST
Already fixed in CVS
Comment 2 Mike McLean 2003-01-02 18:01:03 EST
fix confirmed. -re0102.1
Comment 3 Mike McLean 2003-01-02 18:02:33 EST
*** Bug 80372 has been marked as a duplicate of this bug. ***

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