diff options
Diffstat (limited to 'contrib/amd/doc/am-utils.texi')
| -rw-r--r-- | contrib/amd/doc/am-utils.texi | 155 |
1 files changed, 111 insertions, 44 deletions
diff --git a/contrib/amd/doc/am-utils.texi b/contrib/amd/doc/am-utils.texi index 8d2493d..65d1af3 100644 --- a/contrib/amd/doc/am-utils.texi +++ b/contrib/amd/doc/am-utils.texi @@ -1,6 +1,6 @@ \input texinfo @c -*-texinfo-*- @c -@c Copyright (c) 1997-2003 Erez Zadok +@c Copyright (c) 1997-2004 Erez Zadok @c Copyright (c) 1989 Jan-Simon Pendry @c Copyright (c) 1989 Imperial College of Science, Technology & Medicine @c Copyright (c) 1989 The Regents of the University of California. @@ -38,7 +38,7 @@ @c @c %W% (Berkeley) %G% @c -@c $Id: am-utils.texi,v 1.21.2.28 2003/04/14 01:23:10 ezk Exp $ +@c $Id: am-utils.texi,v 1.21.2.32 2004/01/21 04:04:58 ib42 Exp $ @c @setfilename am-utils.info @@ -60,7 +60,7 @@ (Originally by Jan-Simon Pendry and Nick Williams) @page -Copyright @copyright{} 1997-2003 Erez Zadok +Copyright @copyright{} 1997-2004 Erez Zadok @* Copyright @copyright{} 1989 Jan-Simon Pendry @* @@ -93,7 +93,7 @@ For version @value{VERSION}, @value{UPDATED} @* (Originally by Jan-Simon Pendry and Nick Williams) -Copyright @copyright{} 1997-2003 Erez Zadok +Copyright @copyright{} 1997-2004 Erez Zadok @* Copyright @copyright{} 1989 Jan-Simon Pendry @* @@ -232,17 +232,25 @@ Revision 5.2 was part of the 4.3BSD Reno distribution. Revision 5.3bsdnet, a late alpha version of 5.3, was part of the BSD network version 2 distribution -Revision 6.0 was made independently by @email{ezk@@cs.columbia.edu,Erez -Zadok} at the @uref{http://www.cs.columbia.edu/,Computer Science -Department} of @uref{http://www.columbia.edu/,Columbia University}, as -part of his @uref{http://www.cs.columbia.edu/~ezk/research/tp/thesis_proposal.html,PhD thesis work}. @xref{History}, for more details. +Revision 6.0 was made independently by +@email{ezk@@cs.columbia.edu,Erez Zadok} at the Computer Science +Department of @uref{http://www.cs.columbia.edu/,Columbia University}, +as part of his +@uref{http://www.cs.columbia.edu/~ezk/research/tp/thesis_proposal.html,PhD +thesis work}. Am-utils (especially version 6.1) continues to be +developed and maintained at the +@uref{http://www.cs.sunysb.edu/,Computer Science Department} of +@uref{http://www.stonybrook.edu/,Stony Brook University}, as a service +to the user community. + +@xref{History}, for more details. @unnumberedsec Bug Reports @cindex Bug reports Before reporting a bug, see if it is a known one in the @uref{http://www.am-utils.org/BUGS.txt,bugs} file. -Send all bug reports to @email{amd-dev@@majordomo.cs.columbia.edu} +Send all bug reports to @email{am-utils@@am-utils.org} quoting the details of the release and your configuration. These can be obtained by running the command @samp{amd -v}. It would greatly help if you could provide a reproducible procedure for detecting the bug you are @@ -253,10 +261,10 @@ incorporated, however small, will get its author an honorable mention in the @uref{http://www.am-utils.org/AUTHORS.txt,authors file}. -@unnumberedsec Mailing List -@cindex Mailing list +@unnumberedsec Mailing Lists +@cindex Mailing lists -There are two mailing lists for people interested in keeping up-to-date +There are several mailing lists for people interested in keeping up-to-date with developments. @c ############### @@ -264,15 +272,7 @@ with developments. @enumerate @item -The older list, @samp{amd-workers} is for general "how to" questions and -announcements. To subscribe, send a note to -@email{amd-workers-request@@majordomo.glue.umd.edu}.@footnote{Note that -the older address, @email{amd-workers-request@@acl.lanl.gov}, is -defunct.} To post a message to this list, send mail to -@email{amd-workers@@majordomo.glue.umd.edu}. - -@item -The developers only list, @samp{amd-dev} is for +The users mailing list, @samp{am-utils} is for @itemize @minus @item @@ -285,22 +285,63 @@ discussions of new features for am-utils implementation and porting issues @end itemize -To subscribe, send a note to @email{majordomo@@majordomo.cs.columbia.edu} -with the single body text line @samp{subscribe amd-dev}. To post a -message to this list, send mail to -@email{amd-dev@@majordomo.cs.columbia.edu}. To avoid as much spam as +To subscribe, visit +@url{http://lists.am-utils.org/mailman/listinfo/am-utils}. After +subscribing, you can post a message to this list at +@email{am-utils@@am-utils.org}. To avoid as much spam as possible, only subscribers to this list may post to it. -Subscribers of @samp{amd-dev} are most suitable if they have the time -and resources to test new and buggy versions of amd, on as many -different platforms as possible. They should also be prepared to learn -and use the GNU Autoconf, Automake, and Libtool packages, and of course, -be very familiar with the complex code in the am-utils package. In -other words, subscribers on this list should be able to contribute -meaningfully to the development of amd. +Subscribers of @samp{am-utils} are most helpful if they have the time +and resources to test new and development versions of amd, on as many +different platforms as possible. They should also be prepared to +learn and use the GNU Autoconf, Automake, and Libtool packages, as +needed; and of course, become familiar with the complex code in the +am-utils package. In other words, subscribers on this list should +hopefully be able to contribute meaningfully to the development of +amd. + +Note that this @samp{am-utils} list used to be called @samp{amd-dev} +before January 1st, 2004. Please use the new name, @samp{am-utils}. + +@item +The announcements mailing list, @samp{am-utils-announce} is for +announcements only (mostly new releases). To subscribe, visit +@url{http://lists.am-utils.org/mailman/listinfo/am-utils-announce}. +This list is read-only: only am-utils developers may post to it. + +@item +We distribute nightly CVS snapshots in +@url{ftp://ftp.am-utils.org/pub/am-utils/snapshots/daily/}. If you +like to get email notices of commits to the am-utils CVS repository, +subscribe to the CVS logs mailing list, @samp{am-utils-cvs} at +@url{http://lists.am-utils.org/mailman/listinfo/am-utils-cvs}. + +@item +The older list which was used to user discussions, @samp{amd-workers}, +is defunct as of January 2004. (Its last address was +@email{amd-workers@@majordomo.glue.umd.edu}.) Don't use +@samp{amd-workers}: use the newer, more active @samp{am-utils} list. + +@item +For completeness, there's a developers-only closed list called +@samp{am-utils-developers@@am-utils.org}. @end enumerate +@unnumberedsec Am-utils Book +@cindex Am-utils book +@cindex Amd book +@cindex Automounter book +@cindex book + +@email{ezk@@cs.sunysb.edu,Erez Zadok} wrote a +@uref{http://www.fsl.cs.sunysb.edu/docs/amd-book/,book}, titled @i{Linux NFS and +Automounter Administration}, ISBN 0-7821-2739-8, (Sybex, 2001). The +book is full of details and examples that go beyond what this manual +has. The book also covers NFS in great detail. Although the book is +geared toward Linux users, it is general enough for any Unix +administrator and contains specific sections for non-Linux systems. + @c ################################################################ @node Intro, History, Distrib, Top @unnumbered Introduction @@ -337,7 +378,7 @@ The @i{Amd} package has been without an official maintainer since 1992. Several people have stepped in to maintain it unofficially. Most notable were the `upl' (Unofficial Patch Level) releases of @i{Amd}, created by me (@email{ezk@@cs.columbia.edu,Erez Zadok}), and available from -@url{ftp://ftp.cs.columbia.edu/pub/amd/}. The last such unofficial +@url{ftp://ftp.am-utils.org/pub/amd/}. The last such unofficial release was `upl102'. Through the process of patching and aging, it was becoming more and more @@ -4430,6 +4471,7 @@ The following parameters are applicable to the @samp{[global]} section only. * local_domain Parameter:: * log_file Parameter:: * log_options Parameter:: +* nfs_allow_insecure_port Parameter:: * nfs_proto Parameter:: * nfs_retransmit_counter Parameter:: * nfs_retry_interval Parameter:: @@ -4658,7 +4700,7 @@ is generally a bad idea to use those reserved for other services such as @samp{kern}, @samp{lpr}, @samp{cron}, etc. @c ---------------------------------------------------------------- -@node log_options Parameter, nfs_proto Parameter, log_file Parameter, Global Parameters +@node log_options Parameter, nfs_allow_insecure_port Parameter, log_file Parameter, Global Parameters @comment node-name, next, previous, up @subsection @t{log_options} Parameter @cindex log_options Parameter @@ -4695,7 +4737,25 @@ warnings @end table @c ---------------------------------------------------------------- -@node nfs_proto Parameter, nfs_retransmit_counter Parameter, log_options Parameter, Global Parameters +@node nfs_allow_insecure_port Parameter, nfs_proto Parameter, log_options Parameter, Global Parameters +@comment node-name, next, previous, up +@subsection @t{nfs_allow_insecure_port} Parameter +@cindex nfs_allow_insecure_port Parameter + +(type=string, default=@samp{no}). Normally amd will refuse requests +coming from unprivileged ports (i.e. ports >= 1024 on Unix systems), +so that only privileged users and the kernel can send NFS requests to +it. However, some kernels (certain versions of Darwin, MacOS X, and +Linux) have bugs that cause them to use unprivileged ports in certain +situations, which causes amd to stop dead in its tracks. This +parameter allows amd to operate normally even on such systems, at the +expense of a slight decrease in the security of its operations. If you +see messages like ``ignoring request from foo:1234, port not +reserved'' in your amd log, try enabling this parameter and give it +another go. + +@c ---------------------------------------------------------------- +@node nfs_proto Parameter, nfs_retransmit_counter Parameter, nfs_allow_insecure_port Parameter, Global Parameters @comment node-name, next, previous, up @subsection @t{nfs_proto} Parameter @cindex nfs_proto Parameter @@ -8285,13 +8345,19 @@ XXX: This section needs to be updated @comment node-name, next, previous, up @unnumbered Acknowledgments & Trademarks -Many thanks to the @email{amd-dev@@majordomo.cs.columbia.edu,Amd -Developers} mailing list through the months developing am-utils. These -members have contributed to the discussions, ideas, code and -documentation, and subjected their systems to alpha quality code. -Special thanks go to those -@uref{http://www.am-utils.org/AUTHORS.txt,authors} who -have submitted patches. +Many thanks to the @email{am-utils@@am-utils.org,Am-Utils Users} +mailing list through the months developing am-utils. These members +have contributed to the discussions, ideas, code and documentation, +and subjected their systems to alpha quality code. Special thanks go +to those @uref{http://www.am-utils.org/AUTHORS.txt,authors} who have +submitted patches, and especially to the maintainers: + +@itemize @bullet +@item @email{ezk@@cs.sunysb.edu,Erez Zadok} +@item @email{ib42@@cs.columbia.edu,Ion Badulescu} +@item @email{ro@@techfak.uni-bielefeld.de,Rainer Orth} +@item @email{nick.williams@@morganstanley.com,Nick Williams} +@end itemize Thanks to the Formal Methods Group at Imperial College for suffering patiently while @i{Amd} was being developed on their machines. @@ -8300,8 +8366,9 @@ Thanks to the many people who have helped with the development of @i{Amd}, especially Piete Brooks at the Cambridge University Computing Lab for many hours of testing, experimentation and discussion. -Thanks to the @email{amd-workers@@majordomo.glue.umd.edu,Amd Workers} -mailing list members for many suggestions and bug reports to @i{Amd}. +Thanks to the older @email{amd-workers@@majordomo.glue.umd.edu,Amd +Workers} mailing list (now defunct) members for many suggestions and +bug reports to @i{Amd}. @itemize @bullet @item |
