Gentoo ships only autofs-3.1.7 package. Meanwhile autofs 4.0 has become stable (ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/). The unstable branch is autofs-4.1.0-beta. I have created an overlay ebuild for autofs-4.0.0 and use it successfully with Solaris and Linux NFS servers to mount filesystems to the /net and /home directories. So far autofs-4.0.0 works without problems for me. This ebuild doesn't include any patches from 3.1.7 version. Reproducible: Always Steps to Reproduce: Expected Results: Expected that at least ~x86 branch would have autofs of 4.x version which is up to date with autofs development.
Created attachment 19811 [details] My overlay ebuild of autofs-4.0.0 package
Committed
Created attachment 19892 [details] Beta version of autofs - looks unstable I've created an ebuild for the beta version of autofs 4.1.0-beta2, but when I tried to use it, somehow half of my /usr tree became unavailable. I didn't setup any automounter on /usr, so I think this was autofs bug. Anyway, I didn't investigate this thoroughly because the system became quite unusable. Anyway, in this ebuild I did some corrections to default config files because those that are provided with as autofs samples look better, and I added samples to the doc files.
Yes I saw a new ebuild appear in cvs. I thought that maybe someone would put beta versions ebuilds as well, someone might debug my weird problem with /usr.
Created attachment 20954 [details] Ebuild for unstable autofs branch 4.1.0-beta3, see comments I've made autofs-4.1.0-beta to work. It appears to have a bug when there are embedded NIS maps inside of auto_master map or maybe a bug with two or more level mount directories (in my case it was /usr/dist mountpoint, for some reason autofs decided it is actually /usr which made my /usr tree empty). So I've made a change in /etc/init.d/autofs script which is kind of a workaround for the directory tree that I have in my network, the reference to another NIS map from auto_master is done by "/-" mountpoint, so I just excluded it from the considered mountpoints in startup script and called my version autofs.rc9. The diff is here: --- /usr/portage/net-fs/autofs/files/autofs.rc8 2003-07-26 14:10:03.000000000 +0300 +++ autofs 2003-11-10 20:48:34.000000000 +0200 @@ -73,9 +73,10 @@ while read dir map options do # These checks screen out duplicates and skip over directories - # where the map is '-'. + # where the map is '-' or directory is '/-' if [ ! -z "$dir" -a ! -z "$map" \ -a x`echo "$map" | cut -c1` != 'x-' \ + -a x`echo "$dir" | cut -c-2` != 'x/-' \ -a "`echo "$knownmaps" | grep $dir/`" = "" ] then # If the options include a -t or --timeout parameter, then
Created attachment 24489 [details] Ebuild for autofs-4.1.0 stable version This is a ebuild for autofs-4.1.0 stable version. It only requires a patch file autofs-4.1.0-lookup.patch that I am attaching next. So far this build fixed my problems with /- mountpoints and nested NIS maps so I am very happy and could consider it as stable by now.
Created attachment 24490 [details, diff] Patch file for autofs-4.1.0 ebuild This is a patch taken from ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/autofs-4.1.0-2.src.rpm which seems to fix some lookup issues. My ebuild requires this patch file.
Since autofs version has changed to 4.1.0 and it is a stable release I am reopening this bug with new submitted ebuild.s
I bumped this one to 4.1.3
Confirmed, autofs 4.1.3 is the latest version.
