Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
when you figure that out, please let me know. i have the same issue with debian on the 2.6.11 kernel. i have rw permissions in my /etc/fstab, but it does not matter only root has those permissions and it still gives me plenty of error msg, but does what i tell it to do.
user can not to squat other then read my USBstick.
submountd tends to replace mountd I suppose for the main Linux distributors. see submount.sourceforge.net/ to check that I correctly understood this. That means changing interpretation of fstab file (noauto,umask .... not processed anymore)
The new option procuid does not help
the option user and users are different but not usefull with this new interpretation of fstab.
I know the two options are different, I'm not exactly sure how 'users' work but I know 'user' will make all the files owned by the user that mounts the device aswell as allowing a normal user to mount/umount that device
Oh, and do you know for sure that the option 'rw' does have an affect if others like 'users' don't? I don't have much knowledge about mountd and submountd to be able to be able to help much further, sorry
I changed my fstab and saw the results on mtab after having unplugged and replugged the USB disk.
It seems that the kernel ( chkconfig --list | grep mount shows nothing) calls submountd which is an executable located in /sbin.
You should never have to reboot for changed settings in fstab to take effect, unless they apply to a drive that can't be unmounted. A drive can only be (safely) unmounted when it is not being used [see fuser(1)]. That said, when you plug in your USB stick, the hotplugger sees a new device, which registers as something like usb-mass-storage. If necessary, appropriate kernel modules are loaded, and the automounter daemon (tipped off by the hotplugger that something is going on) checks the kernel-assigned drive designation against fstab to find out how it should be mounted. I think that's more or less how it works. But fstab changes will take effect on the next mount, regardless.
I've found a solution for me:
Formatting the external disk with FAT32 makes it writable with automount. In other words, if I connect a CFcard or an external hard disk formatted ext3 I have a user read only access and a read/write root access, but without changing anything else, when I reformat my CFCARD or HD with FAT, I get a user read/write access. So I keep the FAT32 filesystem on my external HD.