Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 133850

Summary: NFS install with ISO's does not work
Product: Red Hat Enterprise Linux 4 Reporter: Jos Vos <jos>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED NOTABUG QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: barryn, nobody+pnasrat
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-10-04 09:18:11 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: 123268    

Description Jos Vos 2004-09-27 21:32:19 UTC
Description of problem:
When using NFS install, using a directory with ISO's does not work, it
just complains that it can't find a base/... file. Using NFS with an
extracted tree does work.

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

Comment 1 Jeremy Katz 2004-09-28 01:44:30 UTC
What exactly is in the directory?  What messages are there on tty3?

Comment 2 Barry K. Nathan 2004-09-29 11:26:27 UTC
FWIW I am unable to reproduce this bug (I'm typing this from an
NFS-installed RHEL4 WS beta 1).

Comment 3 Barry K. Nathan 2004-09-29 11:27:54 UTC
BTW, my NFS server is a Debian "sarge" box running an unpatched
mainline 2.6.8.1 kernel, configured to serve NFS v2/v3 over TCP/UDP,
but not NFS v4. Just mentioning this in case it's relevant...

Comment 4 Jos Vos 2004-10-04 09:18:11 UTC
Arghh... stupid user error.  The directory was not world-readable :-(.
After fixing that it seems to work fine.