UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I would just create a group (say "users) and then, once mounted, run
Code:
chgrp users /media/multimedia
chmod -R 775
then add all the users you want to have access to the "users" group. Rather than just allowing all to read/write without restriction.
Both these solutions will work for you, just pick the one with the "best fit" for you.
HMMM---why would "mount" be trying to create a link?
Do you already have an entry in /etc/fstab for /media/multimedia? If so, please post it here. Also, before trying to mount, just issue the "mount" command with no arguments to be sure the thing is not already mounted.
In general, umask sets the default permissions on newly created files. It has particular relevance for setting the rw permissions on FAT32 or vfat filesystems. Unlike native linux filesystems, FAT32 has no native rwx permission structure. However, everything in linux must have rwx permissions. In order to get around this problem, linux grafts or superimposes rwx permissions onto FAT32 filesystems when they are mounted. The internally set umask default rwx perms for FAT32 are generally set to read only. To get around that, you have to reset the umask value in the fstab entry for a FAT32 filesystem. It's the only way to change permissions on FAT32.
For native linux filesystems, umask options inserted fstab are not used or needed. You change the rwx permissions on a native linux partitions by using the chmod command to reset the permissions on the partition mount point which must be done with the partition mounted. This method will not work with FAT32 due to the limitations of that filesystem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.