forked from Minki/linux
AFS: Documentation: fix a few typos in afs.rst
Fix typos (punctuation, grammar, spelling) in afs.rst. Signed-off-by: Randy Dunlap <rdunlap@infradead.org> Cc: David Howells <dhowells@redhat.com> Cc: linux-afs@lists.infradead.org Cc: Jonathan Corbet <corbet@lwn.net> Cc: linux-doc@vger.kernel.org Link: https://lore.kernel.org/r/20210117213351.1075-1-rdunlap@infradead.org Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
parent
047a4aba71
commit
f7775c2084
@ -109,7 +109,7 @@ Mountpoints
|
|||||||
AFS has a concept of mountpoints. In AFS terms, these are specially formatted
|
AFS has a concept of mountpoints. In AFS terms, these are specially formatted
|
||||||
symbolic links (of the same form as the "device name" passed to mount). kAFS
|
symbolic links (of the same form as the "device name" passed to mount). kAFS
|
||||||
presents these to the user as directories that have a follow-link capability
|
presents these to the user as directories that have a follow-link capability
|
||||||
(ie: symbolic link semantics). If anyone attempts to access them, they will
|
(i.e.: symbolic link semantics). If anyone attempts to access them, they will
|
||||||
automatically cause the target volume to be mounted (if possible) on that site.
|
automatically cause the target volume to be mounted (if possible) on that site.
|
||||||
|
|
||||||
Automatically mounted filesystems will be automatically unmounted approximately
|
Automatically mounted filesystems will be automatically unmounted approximately
|
||||||
@ -144,7 +144,7 @@ looks up a cell of the same name, for example::
|
|||||||
Proc Filesystem
|
Proc Filesystem
|
||||||
===============
|
===============
|
||||||
|
|
||||||
The AFS modules creates a "/proc/fs/afs/" directory and populates it:
|
The AFS module creates a "/proc/fs/afs/" directory and populates it:
|
||||||
|
|
||||||
(*) A "cells" file that lists cells currently known to the afs module and
|
(*) A "cells" file that lists cells currently known to the afs module and
|
||||||
their usage counts::
|
their usage counts::
|
||||||
@ -201,7 +201,7 @@ And then run as::
|
|||||||
./klog
|
./klog
|
||||||
|
|
||||||
Assuming it's successful, this adds a key of type RxRPC, named for the service
|
Assuming it's successful, this adds a key of type RxRPC, named for the service
|
||||||
and cell, eg: "afs@<cellname>". This can be viewed with the keyctl program or
|
and cell, e.g.: "afs@<cellname>". This can be viewed with the keyctl program or
|
||||||
by cat'ing /proc/keys::
|
by cat'ing /proc/keys::
|
||||||
|
|
||||||
[root@andromeda ~]# keyctl show
|
[root@andromeda ~]# keyctl show
|
||||||
@ -211,7 +211,7 @@ by cat'ing /proc/keys::
|
|||||||
111416553 --als--v 0 0 \_ rxrpc: afs@CAMBRIDGE.REDHAT.COM
|
111416553 --als--v 0 0 \_ rxrpc: afs@CAMBRIDGE.REDHAT.COM
|
||||||
|
|
||||||
Currently the username, realm, password and proposed ticket lifetime are
|
Currently the username, realm, password and proposed ticket lifetime are
|
||||||
compiled in to the program.
|
compiled into the program.
|
||||||
|
|
||||||
It is not required to acquire a key before using AFS facilities, but if one is
|
It is not required to acquire a key before using AFS facilities, but if one is
|
||||||
not acquired then all operations will be governed by the anonymous user parts
|
not acquired then all operations will be governed by the anonymous user parts
|
||||||
|
Loading…
Reference in New Issue
Block a user