svn commit: r301899 - in vendor/amd/dist: . amd amq conf/checkmount conf/fh_dref conf/hn_dref conf/mount conf/mtab conf/nfs_prot conf/sa_dref conf/transp conf/trap conf/umount doc fixmount fsinfo h...

[Cy Schubert]

In message <129d6f78-e3c6-5d18-9466-a97ca1b11f76 at FreeBSD.org>, Pedro Giffuni wr
ites:
> Hello;
> 
> On 06/15/16 01:14, Konstantin Belousov wrote:
> > On Tue, Jun 14, 2016 at 11:41:08PM +0000, Pedro F. Giffuni wrote:
> >> Author: pfg
> >> Date: Tue Jun 14 23:41:07 2016
> >> New Revision: 301899
> >> URL: https://svnweb.freebsd.org/changeset/base/301899
> >>
> >> Log:
> >>   am-utils: Disable keyword expansion.
> >>
> >>   As recommended in the Committers guide section 5.4.4.1.2.
> > Wouldn't it be better to remove amd before 11 ?
> >
> 
> Yes, that would be better.
> 
> FWIW, I was only investigating a README.autofs file in
> the upstream distribution but I have *no* plans to
> touch any of this, especially not during a code freeze.

It doesn't look like there is anything FreeBSD specific in our amd that is not
in am-utils.

I spent many years as a Solaris (and many other platforms which don't exist
any more) admin. I've always found amd, which I ran on SunOS 4, to be superior to
automount as implemented by Sun and currently in use on Linux. (Amd supported NIS
but not NIS+). It looks like our autofs is a re-implementation of that. For example,
in an NIS (or LDAP) map one could have,

*	host==cwsys;type:=link;fs:=/export/home/${key} \
	host==slippy;type:=link;fs:=/export/home/${key} \
	host==oslippy;type:=link;fs:=/export/home/${key} \
host==beastie;rhost:=slippy6;rfs:=/export/home/${key};type:=nfs;fs:=${autodir}/${key} \
	host==bob;rhost:=cwsys;rfs:=/export/home/${key};type:=nfs;fs:=${autodir}/${key} \
	host==bob;rhost:=cwsys2;rfs:=/export/home/${key};type:=nfs;fs:=${autodir}/${key} \
	host==bob;rhost:=slippy;rfs:=/export/home/${key};type:=nfs;fs:=${autodir}/${key}

(Hopefully exmh won't munge the above beyond recognition.)

The above allows for failover and also allows an admin to specify different 
mappings for different client systems. Unfortunately automount as originally
implemented by Sun never allowed such flexibility unless maps were copied to
individual servers, even if multiple servers shared the same maps.

I suppose we could extend our automount daemons support this but unfortunately
it wouldn't be compatible with anything Solaris or Linux. IIRC many Linux distros
have replaced automountd with systemd whereas IMO looking at the direction Solaris
is going I'd put money on it being irrelevant in the mid future so, this may not be
a big argument against extending our autofs to support this.

I will lament the loss of such a powerful tool from base.


-- 
Cheers,
Cy Schubert <Cy.Schubert at cschubert.com>
FreeBSD UNIX:  <cy at FreeBSD.org>   Web:  http://www.FreeBSD.org

	The need of the many outweighs the greed of the few.