Bug 61203

Summary:	mount umask option octal number
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <wegmann>
Component:	mount	Assignee:	Elliot Lee <sopwith>
Status:	CLOSED RAWHIDE	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-03-15 12:32:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Need Real Name 2002-03-15 12:32:22 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9+) Gecko/20020313

Description of problem:
The manual page lacks the information,
that you need to add a leading 0 to the octal umask option value.

Version-Release number of selected component (if applicable): mount-2.11b-3


How reproducible:
Always

Steps to Reproduce:
1. mount -t ntfs -orw,umask=222 /dev/hda1 /mnt/win
2. ls -l /mnt/win


Actual Results:  The umask octal value is 366, because 222 gets interpreted dezimal.


Expected Results:  dunno, but the manualpage should state that you'll need to
start the number with 0 to get expected result.

Comment 1 Elliot Lee 2002-03-27 19:31:16 UTC

The entries for most of the filesystems already specify that the values for
umask or modes must be in octal, which implies a leading zero. I will add notes
to the ntfs filesystem and any others that are missing.