Bug 166727

Summary: RFE: GUI should support configuration of diskless client /home directory mount point
Product: [Fedora] Fedora Reporter: Jason Vas Dias <jvdias>
Component: system-config-netbootAssignee: Jaroslav Reznik <jreznik>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: pkmartin
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-14 13:40:48 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:

Description Jason Vas Dias 2005-08-24 22:31:18 UTC
Description of problem:

---- Additional Comments From pkmartin.com  2005-08-24 16:48 EDT -------
>Only thing I would like to quibble about at this time is the /home directory is
>mounted as R/O, so a vanilla user (non root) will be unable to log in with this
>default config, even though he would probably have the home dir mounted else
>where in an NFS environment.

The system-config-netboot GUI should support configuration of the per-client 
/etc/fstab files in the snapshot directories and enable easy configuration of
nfs /home mount points.

Comment 1 Jason Vas Dias 2005-08-25 15:42:43 UTC
The implementation should give users the opportunity to either use NFS 
or to configure automount maps for the /home directories.


Comment 2 Fabio Olive Leite 2007-11-12 20:48:32 UTC
Reassigning to component owner.

Comment 3 Radek Brich 2007-11-13 11:12:33 UTC
Currently whole /home is mounted read-write (I added it to default snapshot
files), so users can normally log in and write to their home. Is this a wrong
solution for some reason? Or can I just close this bug now?

Comment 5 Jaroslav Reznik 2010-04-14 13:40:48 UTC
System-config-netboot is entering maintainance-only phase and the whole package will be deprecated soon. There are no plans for active development, only high severity issues bugfixing.