For the
/etc/devfs.rules
Code:
add path 'da[0-9]\*' mode 666
I have used this on my system.
Please notice that
'da[0-9]\*' applies the permission scheme only to nodes from 0 to 9, while
'da*' applies it to any. However, since I think nobody here's going to to plug more than 9 mass storage peripherals into his/her own computer at a time, this wouldn't make any difference, unless you use a USB port extender, and insert more than 9 usb/SD devices all at once, in which case, the the tenth would be read-only.
I would offer only a small additional note, just trying to help here, /etc/devfs.rules
the number specified in
/etc/devfs.rules corresponds to the number ruleset you want to create, technically, it does not change anything, aside from the fact that each ruleset need its own unique number. More than 1 ruleset can be specified at a time inside
/etc/devfs.rules (this comes in handy for example when needing to create a ruleset for a chroot env, a jail, a different user, a different mountpoint). Ruleset number can be specified with
-s
option and mount_point with
-m
. For instance:
devfs -m ~/jail/dev rule -s 5 applyset
applies ruleset 5, to devices listed under jail's
/dev directory.
To list a ruleset:
devfs rule -s 5 show
Now, if no ruleset is specified in
/etc/rc.conf the rules applied at boot are the ones from
/etc/defaults/devfs.rules. This file already takes ruleset numbers from 1 to 4. If a number between 1 and 4 is appended to any of the user's local ruleset in
/etc/devfs.rules, the latter takes precedence and overrides the corresponding ruleset in
/etc/defaults. If local rulesets are numbered higher than 4, and loaded in
/etc/rc.conf, then local user's rules are merged with defaults.
and that "mode 666", not "mode 0660"
This actually gives read/write permission to
"others"
: as long as the user belongs to the group which devices' ownership is granted to in
/etc/devfs.conf, then this is shoudn't be needed
chgrp operator /mnt
chmod g+w /mnt
I'm almost sure this would be reset to default at the next boot no sooner devd is started, hence could be used only for the current session
If you make a localrule, you need to activate it explicitly
Snurg, OP stated he tried to do so the moment he opened the thread
I didn't find how to reload devfs rules, and I do not want to reboot just now, so I'll check it out later myself.
I mentioned it above, but for a proper knowledge see
devfs(8)
To apply my standard ruleset at boot (which is
[localrules=5]
) I have, in
/etc/rc.conf:
Code:
devfs_load_ruleset="YES"
devfs_rulesets="/etc/devfs.rules"
devfs_system_ruleset="localrules"
To learn more, see
rc.conf(5)...since it's a long man page, just type
man rc.conf | less -Sip "rulesets"
If you want to user mount on /mnt, it would probably be helpful to have it also group operator and group-writable.
This is definitely true
bcomputerguy, user needs ownership + read/write permissions for the mount point,
The suggestion Snurg gave to you:
chgrp operator /mnt
chmod g+w /mnt
is undoubtedly good. However, since you're experiencing problems, why don't you try to mount devices somewhere inside your
$HOME first?
For example I'm used to mount things inside
~/Devices.
Finally please beware that, just basing on my experience, if file system to be mounted is slightly corrupted, you won't be able to mount it as standard user. A
fsck
, to dispel any doubt, wouldn't harm.
Speaking of the
ls -l /dev/da*
output you pasted above, for me it's appears ruleset is not being applied for some reason.
Side note: you'll need fuse only for EXT4, exFAT, NTFS and XFS