On Sat, Jul 14, 2007 at 05:37:49PM +0200, Frans Pop wrote:
> Shouldn't the relevant change be delayed until initscripts _does_ support
> this then? And after that nfs-common should be given a proper versioned
> dependency before activating the change?
It was not discovered before after-the-fact, unfortunately.
> Please revert this breakage! just Passing it off to initscripts does not
> seem like the right solution here.
I don't really understand you here. Mounting NFS volumes without rpc.statd
has been semi-broken for ages (ie. works by accident), util-linux is removing
NFS mount support, and something has to take over. Is then the right fix to
a) Add a line or two to initscripts to start rpc.statd in addition to
portmap, or
b) Remove mount.nfs, against upstream's explicit intentions, and let _all_
NFS mounts break when the new util-linux hits unstable?
Given how easy a) is, and how hard b) will break at some later stage, I'm
quite sure I'd prefer a). Actually, you can simply remove the current check
for $gss_or_idmap, and do "/etc/init.d/nfs-common start" as soon as you see
an NFS mount (currently signaled by signaled by signaled by signaled by
"portmap=yes").
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
