# /usr/local/share/removable/removableaction usr/local/share/removable/removableaction Limited to the initial X user only (no fast user switching)Īction “/bin/sleep 3 /usr/local/share/removable/removableaction attach” Īction “/usr/local/share/removable/removableaction detach” Update fstab, mount points on boot to catch cold-swapping $device-name argument was unused by umassaction (now named removableaction) ‘grep :0’ in ‘umassaction’ was changed to ‘grep “]:0″‘ to avoid matching time output from ‘who’ Removed reference to nonexistent ‘auto’ fstype (a Linuxism) in /etc fstab Handle firewire (untested, but should work) Integrate with the KDE media:/ protocol handler It’s based on a project ( ) by Jason But at CAIA ( ), with a number of changes and additions. This is a little set of shell scripts that I wrote to automount removable storage in KDE on FreeBSD HAL was ported just after I finished it, so it’s obsolete. I wrote a similar set of scripts years ago that preserved the normal limits on usermounting (quoting from my old web page): ![]() It negates the mount(8) permission issues, but I don’t like how it does it (security-wise). Here’s one example, which you should be able to install with pkg(8): ![]() That’s the bad news the good news is that FreeBSD and OpenBSD both had functional kernel device-notification systems well before udev came out, and it’s not too hard to script them. FreeBSD had HAL support, but that’s deprecated now (even on Linux), and there’s no udev port. It’s discussed about halfway down the page in this link:Īnother issue is HAL/udev. On FreeBSD, the vfs.usermount kernel parameter needs to be set to 1, you need to be a member of the operator group, and you also need to own the mount point. ![]() Most (all?) of the BSDs limit normal users’ access to mount(8). Most will work just as they would when running on Linux.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |