Bug 50589 - mount doesn't honor "mode" option
Summary: mount doesn't honor "mode" option
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: util-linux   
(Show other bugs)
Version: 7.1
Hardware: All Linux
medium
low
Target Milestone: ---
Assignee: Elliot Lee
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-08-01 13:31 UTC by edgester
Modified: 2007-04-18 16:35 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-04-05 09:37:15 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description edgester 2001-08-01 13:31:24 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.2-2 i686)

Description of problem:
Redhat 7.0/7.1  in mount versions: 2.10r-5 and 2.11b-3 repectively, mount
doesn't honor the mode option. however, it does honor the umask option.
either the mode option needs to be fixed, or removed from the command and
man pages.
Tested in Redhat 7.0/7.1 with the mount versions specified.

How reproducible:
Always

Steps to Reproduce:
1.mount /dev/fd0 -o mode=111 /mnt/floppy
2.
3.
	

Actual Results:  tried with vfat disks only. ls -l /mnt/floppy shows all
files have mode 755  no matter what mode is specified.

Additional info:

workaround, use the umask option for mount.
this problem is also present in autofs. but i suspect that fixing mount
would fix autofs.
Comment 1 Habig, Alec 2001-12-02 18:45:37 UTC 
Still here with RH 7.2's mount-2.11g-5 package.
Comment 2 Christopher Holmes 2002-03-01 21:57:47 UTC 
*** Bug 60548 has been marked as a duplicate of this bug. ***
Comment 3 Elliot Lee 2002-04-15 15:33:06 UTC 
The current man page mentions nothing about the mode= option for fat/vfat
filesystems. Seems fixed.
Note You need to log in before you can comment on or make changes to this bug.