Bug 80778

Summary: Can't run mknod when booted from Phoebe install CD
Product: [Retired] Red Hat Public Beta Reporter: Mark McClelland <mark>
Component: anacondaAssignee: Michael Fulbright <msf>
Status: CLOSED RAWHIDE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: phoebeCC: redhat-bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-01-02 23:01:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 79578    

Description Mark McClelland 2002-12-31 08:16:10 UTC
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 15:53:49 UTC
Already fixed in CVS

Comment 2 Mike McLean 2003-01-02 23:01:03 UTC
fix confirmed. -re0102.1

Comment 3 Mike McLean 2003-01-02 23:02:33 UTC
*** Bug 80372 has been marked as a duplicate of this bug. ***