<https://www.freshports.org/sysutils/automount/#message> Please, can the message be expanded a little? To emphasise the need to avoid conflicts. For example, from <https://forums.freebsd.org/posts/542034> > … If you decide to use this utility, to not interfere with automountd(8), > disable all configurations made to work with automountd(8), in special in > /boot/loader.conf (autofs_load) and /etc/rc.conf (autofs_enable). Also, commentary <https://vermaden.wordpress.com/2018/10/11/freebsd-desktop-part-17-automount-removable-media/#comment-18391>: >> Given the trio of sysutils/automount, sysutils/dsbmd and autofs(8): >> is it ever sane to have more than one enabled? > > Use just one of them at any time. > > The only exception I know is using sysutils/automount or sysutils/dsbmd > for removable media automounting and autofs(8) for automatic NFS mounting. Thank you.
Hi, you mean I should add that to the pkg-message file? Regards.
I think so. Wording maybe something like this: ---- If you use this devd(8)-based automounter: as a general rule, you should _not_ also use the autofs(8)-based automount(8) that is integral to FreeBSD. Exceptions to this rule include use of autofs for NFS. Generally: whatever you choose to use, enable only one solution (avoid conflicts with DSBMD; with automatic mounting features of KDE Plasma; and so on).
As DSBMD or KDE Plasma does not show any messages about conflicts why should I?
(In reply to Slawomir Wojciech Wojtczak from comment #3) Well, you don't *have to*, but Graham's suggestion seems reasonable. Even if you leave the KDE warning out, the rest of the information might be very valuable for end users :-)
It's intended for people who do not intuitively know to _not_ enable multiple solutions. I confess: for a long time, maybe a year or so, I had problems that I quietly ignored. From the blog post commentary in February, I learnt of the potential for conflicts, then I realised that prior problems were almost certainly due to (or exacerbated by) conflicts. ---- We might equally make enhancement requests for package messages for the other solutions, but I thought first of sysutils/automount because it seems to be the most popular. Thanks
OK, I will add such information to the pkg-message file.
I will add these in the next automount(8) release to the pkg-message file. | There are several ways to use automounting on FreeBSD. | | Make sure you are using only one at any given time. We can close this bug I think?
(In reply to Slawomir Wojciech Wojtczak from comment #7) Thank you Slawomir, Do you think we can keep it open and close it when it is actually committed? This PR might reference the PR in which the actual update is done. Cheers.
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=d1b86dc8c66c8928a2ccf4f58abff5771e0f8738 commit d1b86dc8c66c8928a2ccf4f58abff5771e0f8738 Author: Slawomir Wojciech Wojtczak <vermaden@interia.pl> AuthorDate: 2022-05-13 18:14:50 +0000 Commit: Dmitri Goutnik <dmgk@FreeBSD.org> CommitDate: 2022-05-13 18:19:03 +0000 sysutils/automount: Update to 1.7.8 While here, also add note to pkg-descr about conflicts. PR: 263763 PR: 259844 sysutils/automount/Makefile | 2 +- sysutils/automount/distinfo | 6 +++--- sysutils/automount/pkg-descr | 8 ++++++-- sysutils/automount/pkg-message | 6 ++---- 4 files changed, 12 insertions(+), 10 deletions(-)
(In reply to commit-hook from comment #9) Neat! Thank you.