https://bugzilla.novell.com/show_bug.cgi?id=331667
User nfbrown@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=331667#c11
Neil Brown changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nfbrown@novell.com, ro@suse.de
AssignedTo|nfbrown@novell.com |bnc-team-screening@forge.provo.novell.com
Component|Other |YaST2
QAContact|qa@suse.de |jsrain@novell.com
--- Comment #11 from Neil Brown 2008-08-11 18:14:59 MDT ---
I don't think that is the problem or at least not the original problem.
The problem description says that :
The /home mountpoint has been configured with yast's partioner and it's
NFS option.
You (Rudi) say (comment #15)
it should be enabled if you configure nfs-mounts via yast.
which makes sense.
Comment #3 clearly says:
nfs 0:off 1:off 2:off 3:off 4:off 5:off 6:off
So while it "should be", it clearly "is not".
As Comment #6 say:
looks like a bug, isn't it?
Certainly does. Maybe it has been fixed since 10.3, I don't know.
But I'll reassign to YaST maintainers.
[[
As to whether nfs mounts should be enabled by default: I really don't
know. That is largely a policy question and I don't know much about
policy (who do I ask? where do I read?).
It would seem to make sense for /etc/init.d/nfs to run by default, but
for it to not start anything unless there was at least one nfs mount
mentioned in /etc/fstab. I could possibly do that but it isn't clear to
me how to enable a service by default. nfs-utils.spec seems to enable
the 'nfsserver' service, but when I install it, nothing is enabled.
]]
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.