[net-next-2.6.git] / Documentation / filesystems / adfs.txt

Mount options for ADFS
----------------------

  uid=nnn	All files in the partition will be owned by
		user id nnn.  Default 0 (root).
  gid=nnn	All files in the partition will be in group
		nnn.  Default 0 (root).
  ownmask=nnn	The permission mask for ADFS 'owner' permissions
		will be nnn.  Default 0700.
  othmask=nnn	The permission mask for ADFS 'other' permissions
		will be nnn.  Default 0077.

Mapping of ADFS permissions to Linux permissions
------------------------------------------------

  ADFS permissions consist of the following:

	Owner read
	Owner write
	Other read
	Other write

  (In older versions, an 'execute' permission did exist, but this
   does not hold the same meaning as the Linux 'execute' permission
   and is now obsolete).

  The mapping is performed as follows:

	Owner read				-> -r--r--r--
	Owner write				-> --w--w---w
	Owner read and filetype UnixExec	-> ---x--x--x
    These are then masked by ownmask, eg 700	-> -rwx------
	Possible owner mode permissions		-> -rwx------

	Other read				-> -r--r--r--
	Other write				-> --w--w--w-
	Other read and filetype UnixExec	-> ---x--x--x
    These are then masked by othmask, eg 077	-> ----rwxrwx
	Possible other mode permissions		-> ----rwxrwx

  Hence, with the default masks, if a file is owner read/write, and
  not a UnixExec filetype, then the permissions will be:

			-rw-------

  However, if the masks were ownmask=0770,othmask=0007, then this would
  be modified to:
			-rw-rw----

  There is no restriction on what you can do with these masks.  You may
  wish that either read bits give read access to the file for all, but
  keep the default write protection (ownmask=0755,othmask=0577):

			-rw-r--r--

  You can therefore tailor the permission translation to whatever you
  desire the permissions should be under Linux.
Commit	Line	Data
1da177e4 LT	1	Mount options for ADFS
	2	----------------------
	3
	4	uid=nnn All files in the partition will be owned by
	5	user id nnn. Default 0 (root).
4ae0edc2	6	gid=nnn All files in the partition will be in group
1da177e4 LT	7	nnn. Default 0 (root).
	8	ownmask=nnn The permission mask for ADFS 'owner' permissions
	9	will be nnn. Default 0700.
	10	othmask=nnn The permission mask for ADFS 'other' permissions
	11	will be nnn. Default 0077.
	12
	13	Mapping of ADFS permissions to Linux permissions
	14	------------------------------------------------
	15
	16	ADFS permissions consist of the following:
	17
	18	Owner read
	19	Owner write
	20	Other read
	21	Other write
	22
	23	(In older versions, an 'execute' permission did exist, but this
	24	does not hold the same meaning as the Linux 'execute' permission
	25	and is now obsolete).
	26
	27	The mapping is performed as follows:
	28
	29	Owner read -> -r--r--r--
	30	Owner write -> --w--w---w
	31	Owner read and filetype UnixExec -> ---x--x--x
	32	These are then masked by ownmask, eg 700 -> -rwx------
	33	Possible owner mode permissions -> -rwx------
	34
	35	Other read -> -r--r--r--
	36	Other write -> --w--w--w-
	37	Other read and filetype UnixExec -> ---x--x--x
	38	These are then masked by othmask, eg 077 -> ----rwxrwx
	39	Possible other mode permissions -> ----rwxrwx
	40
	41	Hence, with the default masks, if a file is owner read/write, and
	42	not a UnixExec filetype, then the permissions will be:
	43
	44	-rw-------
	45
	46	However, if the masks were ownmask=0770,othmask=0007, then this would
	47	be modified to:
	48	-rw-rw----
	49
	50	There is no restriction on what you can do with these masks. You may
	51	wish that either read bits give read access to the file for all, but
	52	keep the default write protection (ownmask=0755,othmask=0577):
	53
	54	-rw-r--r--
	55
	56	You can therefore tailor the permission translation to whatever you
	57	desire the permissions should be under Linux.