MandrivaThis Forum is for the discussion of Mandriva (Mandrake) 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'm stuck with a problem accessing a DVD-RW media, with my Pionner DVR-107D writer, on Mandriva LE2005 system. The media was written by my new movie DVD recorder, a Samsung DVD-R120.
The problem was already explain in another thread, reference below, but the number of posts & the new direction i get to solve this problem deserve a new thread.
It appears that when i insert a DVD-RW media, from the SAMSUNG's DVD-R120, the Mandriva LE2005 indicate that the directory isn't accessible (not executable, at the directory level), of course this make the media not accessible. Important thing, the root user CAN access it, not regular user.
How can I change this behavior, perhaps within FSTAB, can we force him to make the media accessible? Of course, i already tried the option "exec" before and after the option "user" and "users" since those one seems to make it not executable. But i'm not sure if the term "executable" in mount space means only binaries execution or if include directory execution as in linux securoty space. Anyway, all tries with "exec" always failed.
Note: LE 2005, seems to use gnome volume manager to mount those drives-media.
Is there a knowledgeable person who can help me dig, probably in depth, this problem?
umask=000 modifies the 'permissions' on non-linux filesystems (iso9660,vfat,etc.). It makes the permissions 777 & ~umask (aka, 777 in this case). It should give full permissions.
Ref: http://www.linuxsecurity.com/content/view/117255/141/
------------------------------------------------------------
The umask can be used to control the default file permission on newly-created files. The umask command controls the default file and directory creation mode for newly-created files and directories. It is recommended that you make root's umask 077, which will disable read, write, and execute permission for other users, unless explictly changed using chmod.
The umask command can be used to determine the default file creation mode on your system. It is the octal complement of the desired file mode. If files are created without any regard to their permissions settings, a user could inadvertently give read or write permission to someone that should not have this permission.
The umask for the creation of new executable files is calculated as follows:
777 Default Permissions
-022 Subtract umask value, for example
-----
755 Allowed Permissions
So in this example we chose 022 as our umask. This shows us that new executables that are created are given mode 755, which means that the owner can read, write, and execute the binary, while members of the group to which the binary belongs, and all others, can only read and execute it.
The umask for the creation of new text files is calculated as follows:
666 Default Permissions
-022 Subtract umask mask, for example
-----
644 Allowed Permissions
This example shows us that given the default umask of 666, and subtracting our sample umask value of 022, new text files are created with mode 644, which states that the owner can read and write the file, while members of the group to which the file belongs, and everyone else can only read the new file. Typically umask settings include 022, 027, and 077, which is the most restrictive. Normally the umask is set in /etc/profile, so it applies to all users on the system. The file creation mask must be set while keeping in mind the purpose of the account. Permissions that are too restrictive may cause users to start sharing accounts or passwords, or otherwise compromise security. For example, you may have a line that looks like this:
# Set the user's default umask
umask 033
----------------------------------------------------------------
But, this explanantion works for executable & text files, but i'm not sure about mounted directory. Is umask applied the same way to directory as files?
umask is applied in the same way. Note that a users umask and a umask specified in fstab are different things. See the fstab man page for details on its umask.
Even if I set umask to 0000 i have the permission 666 which looks like the default permission for new directory, I read this somewhere.
Now, is it possible to change directory default permission from 666 to 777 ? We should not forget that this directory represents the DVD media, in my specific case, it's a DVD-RW. And as a removable media, it's mounted automatically.
For info, when i put a standard DVD Movie in this drive, i got the following permission:
dr-xr-xr-x 8 4294967295 4294967295 716 avr 12 2001 DVD_Writer/
Is it because the hypothesis of default directory permission as 666 don't keep the road? I looked in /etc/profile and found a umask of 022 which doesn't explain why i loose the enter/execute privilege.
With the DVD-ROM, Kaffeine started automatically playing... 102 Dalmatians (my daughter movie)
With the DVD-RW, only root user can access the media.
I lookeg on the side of gnome-volume-manager to search if there is some options to configure somewhere related with privileges of mounted media. I found nothing.
You know, I've never seen that udf,iso9660 filesystem syntax before. I'm not saying it's wrong, but I am wondering if it is right. Perhaps it's just my turn to learn.
This however would preclude write to the drive in anything other than udf (for data CDs and data DVDs) and iso9960 (which is used for creating CDs and possibly DVDs from downloaded .iso files).
Perhaps if you don't mind auto-mounting with the equivalent of auto-play you should use 'auto' rather than 'fs=udf,iso9960' and again perhaps this will avoid the root only blockage that you, Ben, are encountering.
And one would set rw on an optical drive... why? Yes, there are a few where you could use dvd+rw for arbitrary filesystems, but that doesn't seem to be the case here. Trying rw with other media is just asking for issues.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.