Is amd automount still supported in 13.0 or not?

Bob Willcox bob at
Mon Mar 9 17:26:50 UTC 2020

On Mon, Mar 09, 2020 at 08:35:58AM -0700, Cy Schubert wrote:
> On March 9, 2020 7:49:34 AM PDT, Ed Maste <emaste at> wrote:
> >On Sun, 8 Mar 2020 at 13:23, Bob Willcox <bob at> wrote:
> >>
> >> Thanks for the tip! That worked for me. I guess from reading the
> >documentation
> >> I didn't pick up on staying with the symlinks and simply changing
> >host to net.
> >
> >Glad it's working for you! Is there anything else that you found
> >tricky or surprising in migrating? Perhaps we could produce a
> >quick-reference transition guide.
> >_______________________________________________
> >freebsd-current at mailing list
> >
> >To unsubscribe, send any mail to
> >"freebsd-current-unsubscribe at"
> /net and indirect maps should be simple conversations. Direct maps may or may not be easy. Autofs doesn't support nested direct maps like amd does. You may need to mount elsewhere or use /net with symlinks.
> We do have a port as well. The port will be retired after a reasonable amount of time to allow people to convert. Amd upstream has told me he no longer supports amd. His advice is to use autofs.

Yes, and I considered installing the amd port but that just seemed like I'd be postponing
the inevitable. Since I had a simple use case of just using symlinks to about four of my
remote filesystems, switching from using the /host symlink to the /net symlink was pretty

Bob Willcox    | It's possible that the whole purpose of your life is to
bob at | serve as a warning to others.
Austin, TX     |

More information about the freebsd-current mailing list