diff options
author | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-04-16 18:20:36 -0400 |
---|---|---|
committer | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-04-16 18:20:36 -0400 |
commit | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (patch) | |
tree | 0bba044c4ce775e45a88a51686b5d9f90697ea9d /Documentation/filesystems/adfs.txt |
Linux-2.6.12-rc2v2.6.12-rc2
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.
Let it rip!
Diffstat (limited to 'Documentation/filesystems/adfs.txt')
-rw-r--r-- | Documentation/filesystems/adfs.txt | 57 |
1 files changed, 57 insertions, 0 deletions
diff --git a/Documentation/filesystems/adfs.txt b/Documentation/filesystems/adfs.txt new file mode 100644 index 000000000000..060abb0c7004 --- /dev/null +++ b/Documentation/filesystems/adfs.txt | |||
@@ -0,0 +1,57 @@ | |||
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). | ||
6 | gid=nnn All files in the partition willbe in group | ||
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. | ||