tjh.dev
Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
docs: filesystems: convert adfs.txt to ReST
- Add a SPDX header;
- Add a document title;
- Adjust section titles;
- Mark literal blocks as such;
- Add it to filesystems/index.rst.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Link: https://lore.kernel.org/r/15ee92f03ec917e5d26bd7b863565dec88c843f6.1581955849.git.mchehab+huawei@kernel.org
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
authored by
Mauro Carvalho Chehab
and committed by
Jonathan Corbet
34873900
07d241fd
+20
-10
+19
-10
Documentation/filesystems/adfs.txt
Documentation/filesystems/adfs.rst
+19
-10
Documentation/filesystems/adfs.txt
Documentation/filesystems/adfs.rst
···
1
+
.. SPDX-License-Identifier: GPL-2.0
2
+
3
+
===============================
4
+
Acorn Disc Filing System - ADFS
5
+
===============================
6
+
1
7
Filesystems supported by ADFS
2
8
-----------------------------
3
9
···
31
25
Mount options for ADFS
32
26
----------------------
33
27
28
+
============ ======================================================
34
29
uid=nnn All files in the partition will be owned by
35
30
user id nnn. Default 0 (root).
36
31
gid=nnn All files in the partition will be in group
···
43
36
ftsuffix=n When ftsuffix=0, no file type suffix will be applied.
44
37
When ftsuffix=1, a hexadecimal suffix corresponding to
45
38
the RISC OS file type will be added. Default 0.
39
+
============ ======================================================
46
40
47
41
Mapping of ADFS permissions to Linux permissions
48
42
------------------------------------------------
49
43
50
44
ADFS permissions consist of the following:
51
45
52
-
Owner read
53
-
Owner write
54
-
Other read
55
-
Other write
46
+
- Owner read
47
+
- Owner write
48
+
- Other read
49
+
- Other write
56
50
57
51
(In older versions, an 'execute' permission did exist, but this
58
-
does not hold the same meaning as the Linux 'execute' permission
59
-
and is now obsolete).
52
+
does not hold the same meaning as the Linux 'execute' permission
53
+
and is now obsolete).
60
54
61
-
The mapping is performed as follows:
55
+
The mapping is performed as follows::
62
56
63
57
Owner read -> -r--r--r--
64
58
Owner write -> --w--w---w
···
74
66
Possible other mode permissions -> ----rwxrwx
75
67
76
68
Hence, with the default masks, if a file is owner read/write, and
77
-
not a UnixExec filetype, then the permissions will be:
69
+
not a UnixExec filetype, then the permissions will be::
78
70
79
71
-rw-------
80
72
81
73
However, if the masks were ownmask=0770,othmask=0007, then this would
82
-
be modified to:
74
+
be modified to::
75
+
83
76
-rw-rw----
84
77
85
78
There is no restriction on what you can do with these masks. You may
86
79
wish that either read bits give read access to the file for all, but
87
-
keep the default write protection (ownmask=0755,othmask=0577):
80
+
keep the default write protection (ownmask=0755,othmask=0577)::
88
81
89
82
-rw-r--r--
90
83