Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 157432 - RFE: Make it easier to select a valid NFS directory when selecting which server/directory to install from
RFE: Make it easier to select a valid NFS directory when selecting which serv...
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2005-05-11 12:09 EDT by Dave Malcolm
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-11 16:56:22 EDT
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 Dave Malcolm 2005-05-11 12:09:40 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050504 Fedora/1.0.3-4 Firefox/1.0.3

Description of problem:
I'm attempting to install RHEL3 U5 from an NFS directory, given a boot CD.

I reach a screen: "NFS Setup" that requires me to give an NFS server name, and a Red Hat directory.

Getting the server correct is quite easy in our internal setup, but the "Red Hat directory" involves a complex path below an NFS share, with much to get wrong (underscores vs dashes, code numbers etc)

Would it be possible to implement some kind of browsing (maybe just tab-completion) in that field, so that this stage is easier?

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

How reproducible:

Steps to Reproduce:
1. Burn a boot CD
2. Install from "NFS Image"
3. Step through "Configure TCP/IP": screen (use dynamic IP)
4. NFS Setup screen: try valiantly to type the directory name precisely correctly

Actual Results:  I copy over the path as carefully as possible from another machine, get itslightly wrong and get this 
Error - That directory could not be mounted from the server

I don't know exactly where my typo is.

Expected Results:  Some kind of assistance at getting the directory name - maybe just tab completion in that field?  Can we browse all NFS exports from a given server?  (Could we even browse all NFS servers?)

Additional info:
Comment 1 Dave Malcolm 2005-05-11 12:12:47 EDT
Ah - typing fragments of the path that are valid gets a different error message:
Error - That Directory does not seem to contain a <name> installation tree.

So it's possible to build up the full path in stages and deduce where the typo
occurs this way.
Comment 2 Jeremy Katz 2005-05-11 16:56:22 EDT
Unfortunately, this isn't really possible given the way NFS works.  It's
entirely possible that the only thing exported is /some/long/path/to/a/tree.

What we do have as an rfe adding support for using mirror lists (somehow).  This
is more likely to happen.

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