mirror of
https://git.openafs.org/openafs.git
synced 2025-01-18 06:50:12 +00:00
spelling corrections in readme files
Fix spelling errors in readme files. Change-Id: I62348372d5e226f2b2a3a7732b4a5f8c7331b2ff Reviewed-on: http://gerrit.openafs.org/8876 Tested-by: BuildBot <buildbot@rampaginggeek.com> Reviewed-by: Ken Dreyer <ktdreyer@ktdreyer.com>
This commit is contained in:
Michael Meffie
Ken Dreyer
parent
81dd4878e7
commit
4042667388
@ -191,7 +191,7 @@ STEP C. Install SDK header files.
|
||||
|
||||
Files from Microsoft's Platform SDK for Windows Server 2003 SP1 are
|
||||
required to complete a build on Windows 2000/XP/2003. At a minimum the
|
||||
following componets are known to be required:
|
||||
following components are known to be required:
|
||||
|
||||
* Core
|
||||
* Data Access
|
||||
|
||||
@ -21,7 +21,7 @@ way to do this?)
|
||||
|
||||
-- Prototyping and Style --
|
||||
Prototypes for all source files in a given dir DDD should be placed
|
||||
int the file DDD/DDD_prototypes.h. All externally used (either API
|
||||
in the file DDD/DDD_prototypes.h. All externally used (either API
|
||||
or used by other source files) routines and variables should be
|
||||
prototyped in this file.
|
||||
|
||||
|
||||
10
doc/README
10
doc/README
@ -1,20 +1,20 @@
|
||||
What's in the "doc" subdirectory
|
||||
|
||||
** doc/html
|
||||
original ibm html doc, no longer used
|
||||
original IBM html doc, no longer used
|
||||
|
||||
** doc/man-pages
|
||||
pod sources for man pages (converted from original ibm html source).
|
||||
pod sources for man pages (converted from original IBM html source).
|
||||
|
||||
** doc/xml
|
||||
xml sources for manuals (converted from original ibm html source). there is
|
||||
xml sources for manuals (converted from original IBM html source). there is
|
||||
some generated pdf/html content as well for the curious.
|
||||
|
||||
Note that doc/xml/AdminReference uses doc/xml/AdminReference/pod2refentry to
|
||||
convert the pod man pages to xml for printing. pod goes directly to html
|
||||
just fine.
|
||||
|
||||
The reference guide is now built by converting the existing pod documention
|
||||
The reference guide is now built by converting the existing pod documentation
|
||||
to xml. however, the indexing information was lost during the initial pod
|
||||
conversion. Someone we will need to try to get that back.
|
||||
|
||||
@ -36,7 +36,7 @@ current behavior of OpenAFS (for example, there's no documentation of
|
||||
dynroot, no mention of Kerberos v5, many fileserver options are
|
||||
undocumented, the afsd switch documentation is out of date, and so forth).
|
||||
I've collected as many of those deficiencies as I know of in
|
||||
doc/man-pages/README. Any contributions to correct any of those deficiences
|
||||
doc/man-pages/README. Any contributions to correct any of those deficiencies
|
||||
are very welcome. This is one easy place to start.
|
||||
|
||||
The other reference manuals (the Administrator's Guide, the Quick Start
|
||||
|
||||
@ -31,7 +31,7 @@ It has been integrated into OpenAFS 1.5.x.
|
||||
clients to reevaluate directory lookups any time the sysname changes.
|
||||
- Fixed several bugs related to sysname handling
|
||||
- Fixed a bug preventing 'fs exportafs' from changing the flag which
|
||||
controlls whether callbacks are made to NFS clients to obtain tokens
|
||||
controls whether callbacks are made to NFS clients to obtain tokens
|
||||
and sysname lists.
|
||||
- Starting in this version, when the PAG manager starts up, it makes a
|
||||
call to the translator to discard any tokens belonging to that client.
|
||||
@ -70,7 +70,7 @@ in order to prevent the common NFS server code from performing unwanted
|
||||
access checks, and an fsid option must be provided to set the filesystem
|
||||
identifier to be used in NFS filehandles. Note that for live migration
|
||||
to work, a consistent filesystem id must be used on all translator systems.
|
||||
The export may be accomplised with a line in /etc/exports:
|
||||
The export may be accomplished with a line in /etc/exports:
|
||||
|
||||
/afs (rw,no_subtree_check,fsid=42)
|
||||
|
||||
@ -155,7 +155,7 @@ changes such that it is talking to a different translator.
|
||||
This feature is automatically supported by the PAG manager if it has
|
||||
been configured to forward system calls to an NFS translator. However,
|
||||
requests will be honored only if they come from port 7001 on the NFS
|
||||
translator host. In addition, this feature must be enabld on the NFS
|
||||
translator host. In addition, this feature must be enabled on the NFS
|
||||
translator system as described above.
|
||||
|
||||
|
||||
@ -168,7 +168,7 @@ with credential caching and retrieval is enabled as described above.
|
||||
|
||||
The PAG manager maintains a system-wide sysname list, which is used to
|
||||
satisfy callback requests from the NFS translator. This list is set
|
||||
intially to contain only the compiled-in default sysname, but can be
|
||||
initially to contain only the compiled-in default sysname, but can be
|
||||
changed by the superuser using the VIOC_AFS_SYSNAME pioctl or the
|
||||
'fs sysname' command. Any changes are automatically propagated to the
|
||||
NFS translator.
|
||||
@ -197,7 +197,7 @@ This feature is available whenever the dynamic AFS root is enabled.
|
||||
On Linux systems, it is also available even when dynroot is not enabled,
|
||||
to support the NFS translator. It is presently not possible to disable
|
||||
this feature, though that ability may be added in the future. It would
|
||||
be difficult to make this feature unavailble to users and still make the
|
||||
be difficult to make this feature unavailable to users and still make the
|
||||
Linux NFS translator work, since the point of the check being performed
|
||||
by the NFS server is to ensure the requested file would be reachable by
|
||||
the client.
|
||||
|
||||
@ -168,14 +168,14 @@
|
||||
|
||||
5. BUILDING
|
||||
|
||||
The build process is fairly starightforward. The source is set up
|
||||
The build process is fairly straightforward. The source is set up
|
||||
to build using 'nmake', a build tool distributed with the Platform
|
||||
SDK as well as with Visual Studio.
|
||||
|
||||
1. Open a command prompt with a suitable build environment.
|
||||
|
||||
From a plain command prompt, you can set up a debug build
|
||||
environment targetting Windows XP (32-bit) with:
|
||||
environment targeting Windows XP (32-bit) with:
|
||||
|
||||
> "%PROGRAMFILES%\Microsoft Platform SDK\SetEnv.Cmd" /XP32 /DEBUG
|
||||
|
||||
|
||||
@ -74,6 +74,6 @@ about the Apache Web Server and SSL.
|
||||
|
||||
* Apache Home Page http://www.apache.org
|
||||
* Stronghold Home http://www.c2.net
|
||||
* Stronhold International http://www.int.c2.net
|
||||
* Stronghold International http://www.int.c2.net
|
||||
* Apache-SSL Home http://www.apache-ssl.org
|
||||
* SSLeay FAQ http://www.psy.uq.edu.au:8080/~ftp/Crypto/
|
||||
|
||||
@ -24,7 +24,7 @@ In addition to these you should know the location of the AFS library
|
||||
The mod_afs.c file should be in the apache src directory with all the other
|
||||
module files. weblog and weblog_starter should be in the same directory - this
|
||||
could be any directory (preferably outside AFS - if it is in AFS then
|
||||
system:anyuser should have the appropriate ACL on that directiry).
|
||||
system:anyuser should have the appropriate ACL on that directory).
|
||||
|
||||
Editing the following files in the apache src and conf directories:-
|
||||
|
||||
|
||||
@ -310,7 +310,7 @@ characters if desired.)
|
||||
|
||||
(Optional) To customize the authorization dialog box that is displayed
|
||||
when a user attempts to access the AFS file space via a web browser,
|
||||
add the follwing line to the Location directive added in the previous
|
||||
add the following line to the Location directive added in the previous
|
||||
step. The Location directive then appears as follows:
|
||||
|
||||
AFSLoginPrompt [Custom Text]
|
||||
@ -369,6 +369,6 @@ about the Apache Web Server and SSL.
|
||||
|
||||
* Apache Home Page http://www.apache.org
|
||||
* Stronghold Home http://www.c2.net
|
||||
* Stronhold International http://www.int.c2.net
|
||||
* Stronghold International http://www.int.c2.net
|
||||
* Apache-SSL Home http://www.apache-ssl.org
|
||||
* SSLeay FAQ http://www.psy.uq.edu.au:8080/~ftp/Crypto/
|
||||
|
||||
@ -12,7 +12,7 @@ mutex at the entry point of every public function in the library.
|
||||
|
||||
However, not all public functions are made thread safe since not all
|
||||
functions are needed by the NT admin work. In particular, there are
|
||||
many public functions that make up decendants of the functions
|
||||
many public functions that make up descendants of the functions
|
||||
we wish to use that weren't modified, since these functions will be
|
||||
protected by the locking at a higher level function.
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
A note on BSD licensing of the software contained herin.
|
||||
A note on BSD licensing of the software contained herein.
|
||||
|
||||
This software includes software previously released in 2003 under a
|
||||
GPL license, but released by the original copyright holder, Keir
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
Included in this directory are copies of the files used to create OpenAFS
|
||||
binary packages. It will be endeavoured to keep them up to date, however,
|
||||
binary packages. It will be endeavored to keep them up to date, however,
|
||||
the files in the binary packaging system used by the vendor (the debian
|
||||
directory as used by Debian or the srpm for RedHat packages) is currently
|
||||
canonical. These should be treated as reference material only.
|
||||
|
||||
@ -1,22 +1,22 @@
|
||||
#
|
||||
# This code depends on heimdal's asn1_compile generated krb5 decoding
|
||||
# stuff. The code is orignally from rxkad that Björn Grönvall
|
||||
# stuff. The code is originally from rxkad that Björn Grönvall
|
||||
# <bg@sics.se> for kth-krb and was included in Arla.
|
||||
#
|
||||
# The first file, v5der.c are part for of support functions
|
||||
# that all generated files depends on.
|
||||
#
|
||||
# The second file (v5gen.h) is the headerfile that is generated for
|
||||
# The second file (v5gen.h) is the header file that is generated for
|
||||
# the decoding functions.
|
||||
#
|
||||
# The third file (v5gen.c) is the subset of the genrated functions we
|
||||
# The third file (v5gen.c) is the subset of the generated functions we
|
||||
# need to decode the authenticator.
|
||||
#
|
||||
# The forth file (v5gen-rewrite.h) is used to make sure we don't
|
||||
# polute the namespace.
|
||||
# pollute the namespace.
|
||||
#
|
||||
# All files are modified to build within OpenAFS enviroment without
|
||||
# any external dependencies. Below is the shellscript that is used to
|
||||
# All files are modified to build within OpenAFS environment without
|
||||
# any external dependencies. Below is the shell script that is used to
|
||||
# import the code into the four files.
|
||||
#
|
||||
# All internal symbols are rewritten to _rxkad_v5_.
|
||||
|
||||
@ -56,7 +56,7 @@ B) Basic functionality
|
||||
|
||||
C) Mountpoint tests
|
||||
10) Create and remove a good mountpoint. (mkm-rmm)
|
||||
20) Create a mountpoint to a nonexistant volume. (mountpoint)
|
||||
20) Create a mountpoint to a nonexistent volume. (mountpoint)
|
||||
|
||||
D) ACL tests
|
||||
10) Add a valid PTS user to an ACL. (acladduser)
|
||||
|
||||
@ -1,2 +1,2 @@
|
||||
This is a (potentially) modified verion of the AFSTools perl suite.
|
||||
This is a (potentially) modified version of the AFSTools perl suite.
|
||||
You should visit grand.central.org for the official version.
|
||||
|
||||
@ -64,7 +64,7 @@ accepts the following commands:
|
||||
|
||||
vcp Copy a file from the dump, by the vnode. The first
|
||||
argument is the vnode number, optionally followed by
|
||||
the uniqifier. E.g:
|
||||
the uniquifier. E.g:
|
||||
|
||||
vcp 126278 /tmp/file1
|
||||
vcp 126278.43289 /tmp/file2
|
||||
@ -79,14 +79,14 @@ Dumptool supports a number of command-line options. They are detailed
|
||||
below:
|
||||
|
||||
-v Verbose mode. Output additional information during dump
|
||||
processing. Each -v will increate output.
|
||||
processing. Each -v will increase output.
|
||||
|
||||
-f Force dump processing. Attempt to continue processing
|
||||
a dump even when some errors are detected. Not completely
|
||||
tested.
|
||||
|
||||
-i Inode dump. Dump a list of all files in the volume,
|
||||
with their volume/vnode/uniqifier information.
|
||||
with their volume/vnode/uniquifier information.
|
||||
|
||||
|
||||
SUPPORT FOR MR-AFS
|
||||
@ -149,4 +149,4 @@ think it's only polite for you to do the same.
|
||||
CONTACT INFORMATION
|
||||
|
||||
As always, please send comments, suggestions, or new features to me,
|
||||
Ken Hornstein <kenh@cmf.nrl.navy.mil>. Shar and enjoy.
|
||||
Ken Hornstein <kenh@cmf.nrl.navy.mil>. Share and enjoy.
|
||||
|
||||
@ -21,9 +21,9 @@ With the -lsl option, it prints out metadata about all file/symlink.
|
||||
This metadata includes the inode number(Ind), UNIX mode bits(Mod),
|
||||
link count(Lnk), the owner(Own), the group(Grp) and the file size(Siz).
|
||||
|
||||
With the -ld option, it prints out metadata about all directoies
|
||||
With the -ld option, it prints out metadata about all directories
|
||||
in this volume. This metadata includes the directory inode(Ind) and
|
||||
the directory vnode(Vnd) along woth the directory name. The root
|
||||
the directory vnode(Vnd) along with the directory name. The root
|
||||
directory of the volume is indicated as ~.
|
||||
|
||||
With the -dir <directory inode> option, this tool prints out the
|
||||
|
||||
Loading…
Reference in New Issue
Block a user