ANU News Setup and Site Maintenance Manual

compiled by Charles Bailey (bailey@genetics.upenn.edu)
with contributions from the ANU News user community

This manual was written as part of the revised documentation to be released with version 6.1 of ANU News. Because it contains information which may be useful immediately, it has been included in earlier releases as an independent document. It may refer occasionally to other portions of the News documentation (e.g. detailed descriptions of News commands) not included in this release. In this case, you should use the corresponding sections of the old News documentation as a guide.

Within this document, the following conventions are used:

• File specifications and logical names are written in mixed case to make them easier to read and remember (e.g. News_Root and News.Exe instead of NEWS_ROOT and NEWS.EXE). This is done only in the documentation; in actual practice, News follows the usual VMS conventions regarding case. For example, in order to define the logical name News_NNTP_Log, you could say
  $ Define/System/Exec News_NetPost News_Post_OK
  or
  $ define/system/exec news_netpost news_post_ok
  or
  $ DEFINE/SYSTEM/EXEC NEWS_NETPOST NEWS_POST_OK
  When the case of a string used as a command or configuration constant is significant, this is noted in the text.
• Boldface type is used to denote text which is displayed by News, or which should be entered by the user as shown.
• Italic type is used to denote expressions for which the user should substitute values appropriate to specific circumstances, as described in the text. (Note: This may appear as underlined text on terminal screens and some printers.)
• Within descriptions of commands and configuration files, items enclosed in square brackets ([]) are optional, and may be omitted if unneeded. This is not the case, of course, where square brackets are used to indicate the directory portion of a file specification.

next: 1 What is News Management?
Table of Contents