Red Hat Bugzilla – Bug 172111
latest coreutils breaks autofs's /etc/auto.net
Last modified: 2007-11-30 17:11:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7
Description of problem:
The latest coreutils update removes the long-deprecated `sort +N' syntax in favor of `sort -k n', where n = N + 1. /etc/auto.net still used the old syntax, so it breaks, and /net doesn't work any more. The fix follows:
-$SHOWMOUNT | LC_ALL=C sort -k 1 | \
+$SHOWMOUNT | LC_ALL=C sort +0 | \
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Update to latest autofs and coreutils in the development tree
2.Enable /net mounting in autofs
3.Try to use it to mount anything from any server that exports filesystems over NFS to your box (or even yourself)
Actual Results: It won't mount anything, even though showmount -e shows the exported directories correctly. /var/log/messages says:
Oct 31 14:15:02 fri automount: >> sort: open failed: +0: No such file or directory
Oct 31 14:15:02 fri automount: lookup(program): lookup for fri failed
Oct 31 14:15:02 fri automount: failed to mount /net/fri
These messages are for self (bind) mounts, but it breaks for NFS as well.
Expected Results: It should mount the directories exported from fri.
Is this a regression in coreutils, or is this a known interface breaker?
*** Bug 172028 has been marked as a duplicate of this bug. ***
*** Bug 172239 has been marked as a duplicate of this bug. ***
The change commited does "sort" instead of "sort -k 1", which is probably not
what you really want. "sort -k 1" means the same as "sort +0" used to mean.
This is indeed a change of interface -- but it happened a long long time ago and
we have been patching coreutils to accept the old syntax of +n for ages.
Whatever packages still use the old syntax should be updated, regardless of
whether we eventually decide to patch sort again to still accept +n.
OK. It's now changed to use -k 1.
*** Bug 174015 has been marked as a duplicate of this bug. ***
I'm closing this bug, as it should be addressed in rawhide.