Bug 80372 - mknod doesn't work because PYTHONPATH isn't set
mknod doesn't work because PYTHONPATH isn't set
Status: CLOSED DUPLICATE of bug 80778
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
:
Depends On:
Blocks: 79578
  Show dependency treegraph
 
Reported: 2002-12-25 00:58 EST by Nathan G. Grennan
Modified: 2008-01-17 12:49 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:50:34 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 2002-12-25 00:58:00 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20021216

Description of problem:
mknod doesn't work in the shell during the installer or during rescue mode
because PYTHONPATH isn't being set. So when mknod looks for the isys module
which is in /usr/lib/anaconda it isn't found.

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


How reproducible:
Always

Steps to Reproduce:
1. Boot disc1 cd
2. Type linux rescue at the boot: prompt
3. Skip mount
4. mknod /tmp/hde1 b 33 1
    

Actual Results:  Traceback about inability to import the module isys

Expected Results:  It to make /tmp/hde1

Additional info:
Comment 1 Nathan G. Grennan 2002-12-25 01:26:53 EST
isys is actually in /mny/runtime/usr/lib/anaconda

I tried  export PYTHONPATH=/mnt/runtime/usr/lib/anaconda  in the shell during
the install and it made mknod work.
Comment 2 Jeremy Katz 2002-12-25 22:55:05 EST
Noticed this when I was testing something before I left for the holidays, so
it's already fixed in CVS
Comment 3 Mike McLean 2003-01-02 18:02:29 EST

*** This bug has been marked as a duplicate of 80778 ***
Comment 4 Red Hat Bugzilla 2006-02-21 13:50:34 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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