Search results for query: automount

It means that such a message is displayed when automount cannot mount the device. For example, an external (dongle) usb modem...

That's how a lot of bugs are discovered ;) No, that seems "by design", not because of an incorrect configuration. Automount looks for da devices, as that's usually a USB stick or external drive. Most desktop machines typically use ada drives internally, so there's no "confusion" between...

As for me, I start X with startx. And as for the situation with automount, I discovered it by accident. I have a Broadcom LSI SAS 9300-8i on my system and the HDDs on it show up as 'da0...da1...' in FreeBSD. When the system boots, automount tries to mount them in /media/daX... So I removed...

Yep, it is. https://github.com/vermaden/automount Wrong man page ;) After a bit of digging, procstat is used exactly once in /usr/local/sbin/automount. for I in ${GROUP_USERS} do [ "${I}" = "root" ] && continue DISPLAY_ID=$( procstat pargs $( pgrep Xorg ) | grep...

Hmm, I honestly did not know that this was the development of the esteemed vermaden. And yes, I meant automount

vermaden 's sysutils/automount?

I also got the same message. It disappeared after removing the automount package.

Yep, probably whatever the file manager is called. I think default settings automount especially external drives.

I was able to mount fat32, and find its contents. But every other type of drive does not work. I tried automount and it never worked for anything but fat32. It works on KDE, but not i3

It works, but there's a few problems with it. One is that, it's not good to automount them, because another utility has to be used to check their filesystems, for instance if there's an improper shutdown. I tried ext2 with the ext4 filesystem, and every so often, my files would get corrupted...

Use the port/package: sysutils/automount

vermaden/automount

I have having problems trying to have auotomount. and most tutorials I see either dont work for me, or are many years old. anything would be nice thank you

If you want to be as secure as possible, it strikes me that having USB devices automount is a huge security hole and one of the first things to avoid when hardening a system.

KDE works fine, unless you use nfs automount and don't always have your nfs server running, in which case plasmashell crashes spectacularly. It used to just take a very long time to start up, but now it's far worse. I have no idea why it's trying to access the automounted stuff as I don't ask it to.

Yes I added an automount script because bsd wasn't detecting usbs. Added a line a few hours ago, after which dolphin automounted USB, even when unmounted, dolphin shows the USB. Don't remember where I added, and don't remember what file I changed.Will try to locate what I changed. Update...

...[driver, bug, configuration], or the device of the card has changed from da. Is it anything like or prefixed with mmcsd? https://docs.freebsd.org/en/books/handbook/disks/#_automounting_removable_media The applications and configuration files shown there are in the base system of FreeBSD 13.1.

I don't imagine a reply from aragon (not seen for more than eight years); and the port no longer has a maintainer. 23105 was: https://forums.freebsd.org/threads/auto-mounting-in-openbox.23105/ 161977 – New port: sysutils/volman FreeBSD specific volume manager – Closed FIXED

Thank You for port. So what about automount as plamaiziere commands wrote ?