add release dir
This commit is contained in:
21
release/base/help/english/=
Normal file
21
release/base/help/english/=
Normal file
@@ -0,0 +1,21 @@
|
||||
These are the commands you can use in help:
|
||||
|
||||
. go up one level in the hierarchy
|
||||
|
||||
? display a list of valid subtopics at the current level
|
||||
|
||||
<newline>
|
||||
done, ^D, ^C quit from help entirely
|
||||
|
||||
<string> help on a topic or subtopic
|
||||
Eg.
|
||||
|
||||
"help show"
|
||||
|
||||
will give you the help screen for the "show" command
|
||||
|
||||
"help set search"
|
||||
|
||||
Will give you the help information for the "search" variable.
|
||||
|
||||
The command "manpage" will give you a complete copy of the archie manual page.
|
||||
81
release/base/help/english/about/=
Normal file
81
release/base/help/english/about/=
Normal file
@@ -0,0 +1,81 @@
|
||||
Bunyip Information Systems
|
||||
|
||||
|
||||
about archie 3.0
|
||||
--------------------
|
||||
|
||||
What is archie?
|
||||
|
||||
The archie information system is a network-based information tool
|
||||
offering proactive data retrieval and indexing for widely distributed
|
||||
collections of data.
|
||||
|
||||
The archie Data Gathering Component automates the gathering, indexing and
|
||||
maintenance of information, allowing information providers to offer
|
||||
improved resource discovery and access to information.
|
||||
|
||||
The archie User Access Component allows your users to locate and access
|
||||
your information using a variety of interfaces and search methods.
|
||||
|
||||
Given the number of hosts being used as archive sites nowadays, there can
|
||||
be great difficulty in finding needed software in a distributed
|
||||
environment. You may know that the software that you need is out there,
|
||||
but it can sometimes be difficult to find. Perhaps the best known
|
||||
application of the archie system is to maintain this Internet Archives
|
||||
database. The database, already available from a number of service
|
||||
providers across the Internet, currently contains the names of over
|
||||
2,400,000 files at over 1,000 anonymous FTP archive sites. Using this
|
||||
database, users can rapidly locate needed files without the need to log
|
||||
onto dozens or even hundreds of machines. archie servers offering this
|
||||
database currently receive over 50,000 queries per day.
|
||||
|
||||
Users can ask archie to search for specific name strings. For example,
|
||||
"prog kcl" would find all occurrences of the string "kcl" and tell you which
|
||||
hosts have entries with this string, the size of the program, its last
|
||||
modification date and where it can be found on the host along with some
|
||||
other useful information. In this example, you could thus find those
|
||||
archive sites that are storing Kyoto Common Lisp. With one central database
|
||||
for all the archive sites we know about, archie greatly speeds the task of
|
||||
finding a specific program on the net.
|
||||
|
||||
archie also maintains a 'Software Description Database' which consists
|
||||
of the names and descriptions of various software packages, documents
|
||||
and datasets that are kept on anonymous ftp archive sites all around the
|
||||
Internet. The 'whatis' command allows you to search this database.
|
||||
|
||||
But the archie system is much more than the Internet Archives database.
|
||||
With the latest release, archie has been expanded into a generalized
|
||||
information gathering and distributed database maintenance tool. Using
|
||||
archie, you can build an up-to-date, accurate directory of Internet
|
||||
services, or define new databases and gather entries from across the
|
||||
network. With archie your information collections are updated as often as
|
||||
needed.
|
||||
|
||||
The archie system has gained wide acceptance and acclaim on the Internet.
|
||||
It is now accepted as a service integral to the needs of the Internet
|
||||
user community. Gateways to the archie system have been built for a
|
||||
number of other information delivery systems, including the Wide Area
|
||||
Information System (WAIS), Gopher and the World Wide Web (W3).
|
||||
|
||||
A commercially supported version of the archie system is now available to
|
||||
Internet service providers wishing to build, maintain and offer
|
||||
collections of useful information to an Internet community.
|
||||
|
||||
Send comments, bug reports etc to
|
||||
|
||||
archie-group@bunyip.com
|
||||
|
||||
If you have a favourite anonymous ftp site that archie doesn't seem to
|
||||
maintain, or if you have additions or corrections to the Software
|
||||
Description database, send mail to
|
||||
|
||||
archie-admin@bunyip.com
|
||||
|
||||
Please note that it is our policy only to maintain information from sites
|
||||
whose system administrators have given their approval.
|
||||
|
||||
The original archie program was written by Alan Emtage (bajan@bunyip.com)
|
||||
and Bill Heelan (wheelan@cs.mcgill.ca), with some ideas and inspiration
|
||||
provided by Peter Deutsch (peterd@bunyip.com). The current version is
|
||||
a product of Bunyip Information Systems. For more information, send email
|
||||
to "info@bunyip.com".
|
||||
3
release/base/help/english/bugs/=
Normal file
3
release/base/help/english/bugs/=
Normal file
@@ -0,0 +1,3 @@
|
||||
Currently there are no known bugs with this archie interface.
|
||||
|
||||
|
||||
5
release/base/help/english/bye/=
Normal file
5
release/base/help/english/bye/=
Normal file
@@ -0,0 +1,5 @@
|
||||
|
||||
The commands 'exit', 'quit' and 'bye' allow you to exit
|
||||
from the archie system.
|
||||
|
||||
|
||||
6
release/base/help/english/compress/=
Normal file
6
release/base/help/english/compress/=
Normal file
@@ -0,0 +1,6 @@
|
||||
This command is an alias for
|
||||
|
||||
set compress compress
|
||||
|
||||
See the compress variable help ("help set compress") for further details.
|
||||
|
||||
23
release/base/help/english/domains/=
Normal file
23
release/base/help/english/domains/=
Normal file
@@ -0,0 +1,23 @@
|
||||
The 'domains' command allows you to query the current server about the
|
||||
archie 'pseudo-domains' that it supports.
|
||||
|
||||
The archie system has the concept of "pseudo-domains". This is primarily
|
||||
for the convenience of being able to specify things like
|
||||
|
||||
"usa" instead of ".gov" and ".com" and ".edu" and ".us" etc.
|
||||
|
||||
Pseudo-domains are composed of normal Domain Name System (DNS) domains
|
||||
and other pseudo-domains and each archie server administrator may define
|
||||
them aribtrarily. Ultimately all pseudo-domains should resolve into a
|
||||
list of actual DNS domains. For example, the system administrator may
|
||||
define the pseduo-domain "eastcoastu" to be "massu:nyu:princeton.edu"
|
||||
(universities in Mass., New York and Princeton University). They could
|
||||
then define "massu" to be "harvard.edu:bu.edu" (Harvard and Boston
|
||||
Universities) and "nyu" to be "nyu.edu:columbia.edu" (NY University and
|
||||
Columbia).
|
||||
|
||||
Thus "eastcoastu" would ultimately be
|
||||
|
||||
"harvard.edu:bu.edu:nyu.edu:columbia.edu:princeton.edu"
|
||||
|
||||
|
||||
7
release/base/help/english/done/=
Normal file
7
release/base/help/english/done/=
Normal file
@@ -0,0 +1,7 @@
|
||||
|
||||
The 'done' command allows you to exit the help facility,
|
||||
returning you to the general archie command processor.
|
||||
|
||||
To pop one level of help (for example, from the subtopic
|
||||
'set' to the general topic 'help'), type '.' (period).
|
||||
|
||||
14
release/base/help/english/email/=
Normal file
14
release/base/help/english/email/=
Normal file
@@ -0,0 +1,14 @@
|
||||
|
||||
For those people who do not have direct Internet access or those who
|
||||
would prefer 'batching' of their requests, archie provides an email
|
||||
interface handling a limited subset of the interactive archie commands.
|
||||
|
||||
The address of the interface is
|
||||
|
||||
archie@<archie_server>
|
||||
|
||||
Where <archie_server> is one of the currently available servers worldwide.
|
||||
Please see the "servers" command for a list.
|
||||
|
||||
Please use the "manpage" command or use the help facility for full
|
||||
details on how to use the archie system.
|
||||
5
release/base/help/english/exit/=
Normal file
5
release/base/help/english/exit/=
Normal file
@@ -0,0 +1,5 @@
|
||||
|
||||
The commands 'exit', 'quit' and 'bye' allow you to exit
|
||||
from the archie system.
|
||||
|
||||
|
||||
24
release/base/help/english/find/=
Normal file
24
release/base/help/english/find/=
Normal file
@@ -0,0 +1,24 @@
|
||||
|
||||
The 'find' command (also known as the 'prog' command)
|
||||
allows you to search the database for a specified pattern.
|
||||
|
||||
The usage is:
|
||||
|
||||
find <expression>
|
||||
|
||||
where the interpretation of <expression> depends on the
|
||||
current value of the 'search' variable. Searches may be
|
||||
performed in a number of different ways. See the help
|
||||
section on the 'search' variable for a full explanation.
|
||||
|
||||
The output of find can be sorted in different ways,
|
||||
depending on the value of the 'sortby' variable. See help
|
||||
for the 'sortby' variable for a full explanation.
|
||||
|
||||
The output format of the results can be changed through
|
||||
use of the "output_format" variable.
|
||||
|
||||
The search criteria can be further specified to be restricted
|
||||
on domain names and pathname components. See the "domains"
|
||||
comand and the "match_domain" and "match_path" variables.
|
||||
|
||||
10
release/base/help/english/general/=
Normal file
10
release/base/help/english/general/=
Normal file
@@ -0,0 +1,10 @@
|
||||
|
||||
Help gives you information about various topics, including all the
|
||||
commands that are available and how to use them. Telling archie about
|
||||
your terminal type and size (via the "term" variable) and to use the
|
||||
pager (via the "pager" variable) is not necessary to use help, but
|
||||
provides a somewhat nicer interface.
|
||||
|
||||
type 'help help' to get the valid list of help topics.
|
||||
|
||||
|
||||
17
release/base/help/english/help/=
Normal file
17
release/base/help/english/help/=
Normal file
@@ -0,0 +1,17 @@
|
||||
|
||||
archie Help facility
|
||||
Version 3.0
|
||||
|
||||
For information on a topic type:
|
||||
|
||||
help <topic>
|
||||
|
||||
A '?' at the help prompt will list the available sub-topics.
|
||||
|
||||
Type 'done' or <newline> to exit the help facility.
|
||||
|
||||
The "set" command allows you to change archie variables. Type "set" for
|
||||
further information.
|
||||
|
||||
The currently available help topics are:
|
||||
|
||||
28
release/base/help/english/list/=
Normal file
28
release/base/help/english/list/=
Normal file
@@ -0,0 +1,28 @@
|
||||
|
||||
'list' provides a list of the sites in the database and the time at
|
||||
which they were last updated. There is an optional regular expression
|
||||
argument to limit the list to specific sites.
|
||||
|
||||
Note that the numerical (IP) address associated with a site name is
|
||||
valid at the listed time, but since they do occasionally change, it is
|
||||
possible that a discrepancy may occur until that site is updated in our
|
||||
database. Furthermore, the listed IP address is the primary, as listed
|
||||
in the DNS database: secondary addresses are not stored.
|
||||
|
||||
Usage:
|
||||
|
||||
list [<regex>]
|
||||
|
||||
|
||||
Examples:
|
||||
|
||||
list
|
||||
|
||||
will list all sites in the database, while
|
||||
|
||||
list \.de$
|
||||
|
||||
lists all German sites.
|
||||
|
||||
For further information on regular expressions see the help for 'regex'.
|
||||
|
||||
29
release/base/help/english/mail/=
Normal file
29
release/base/help/english/mail/=
Normal file
@@ -0,0 +1,29 @@
|
||||
|
||||
The 'mail' command has two forms:
|
||||
|
||||
mail <e-mail-address>
|
||||
|
||||
which causes the output of the last command to be mailed to the
|
||||
specified address; or
|
||||
|
||||
mail
|
||||
|
||||
which causes the output to be sent to the address specified in the "mailto"
|
||||
variable.
|
||||
|
||||
All the various Internet addressing styles are understood. BITNET sites
|
||||
should use the convention
|
||||
|
||||
user@sitename.bitnet
|
||||
|
||||
UUCP address can be specified as
|
||||
|
||||
user@sitename.uucp
|
||||
|
||||
If you would like to mail to an Internet IP address then use '[]'.
|
||||
|
||||
Example:
|
||||
|
||||
mail yourlogin@[132.206.44.5]
|
||||
|
||||
|
||||
12
release/base/help/english/manpage/=
Normal file
12
release/base/help/english/manpage/=
Normal file
@@ -0,0 +1,12 @@
|
||||
This command allows you to obtain the archie manual
|
||||
page. The optional arguments specify the format of the
|
||||
returned document. "roff" specifies UNIX troff (or
|
||||
nroff) format (use the -man macros), while ascii
|
||||
specifies plain, preformatted ASCII output. With no
|
||||
arguments it defaults to ascii.
|
||||
|
||||
Eg.
|
||||
|
||||
manpage roff
|
||||
|
||||
will return you the manual page in UNIX troff (or nroff) format.
|
||||
5
release/base/help/english/motd/=
Normal file
5
release/base/help/english/motd/=
Normal file
@@ -0,0 +1,5 @@
|
||||
|
||||
This command prints out the login banner message from the current
|
||||
Prospero server.
|
||||
|
||||
|
||||
5
release/base/help/english/nopager/=
Normal file
5
release/base/help/english/nopager/=
Normal file
@@ -0,0 +1,5 @@
|
||||
|
||||
The functionality of the 'nopager' command has been replaced by the 'pager'
|
||||
variable -- see help for 'set pager' for more details.
|
||||
|
||||
|
||||
4
release/base/help/english/pager/=
Normal file
4
release/base/help/english/pager/=
Normal file
@@ -0,0 +1,4 @@
|
||||
|
||||
The functionality of the 'pager' command has been replaced by the 'pager'
|
||||
variable -- see help for 'set pager' for more details.
|
||||
|
||||
6
release/base/help/english/path/=
Normal file
6
release/base/help/english/path/=
Normal file
@@ -0,0 +1,6 @@
|
||||
This command allows you to Set the return address to
|
||||
<address>. This overrides the default path which the
|
||||
system automatically generates by looking at the
|
||||
incoming mail header. This is actually an alias for
|
||||
"set mailto <address>" (see the "mailto" variable).
|
||||
and is included for backwards compatability.
|
||||
24
release/base/help/english/prog/=
Normal file
24
release/base/help/english/prog/=
Normal file
@@ -0,0 +1,24 @@
|
||||
|
||||
The 'find' command (also known as the 'prog' command)
|
||||
allows you to search the database for a specified pattern.
|
||||
|
||||
The usage is:
|
||||
|
||||
find <expression>
|
||||
|
||||
where the interpretation of <expression> depends on the
|
||||
current value of the 'search' variable. Searches may be
|
||||
performed in a number of different ways. See the help
|
||||
section on the 'search' variable for a full explanation.
|
||||
|
||||
The output of find can be sorted in different ways,
|
||||
depending on the value of the 'sortby' variable. See help
|
||||
for the 'sortby' variable for a full explanation.
|
||||
|
||||
The output format of the results can be changed through
|
||||
use of the "output_format" variable.
|
||||
|
||||
The search criteria can be further specified to be restricted
|
||||
on domain names and pathname components. See the "domains"
|
||||
comand and the "match_domain" and "match_path" variables.
|
||||
|
||||
5
release/base/help/english/quit/=
Normal file
5
release/base/help/english/quit/=
Normal file
@@ -0,0 +1,5 @@
|
||||
|
||||
The commands 'exit', 'quit' and 'bye' allow you to exit
|
||||
from the archie system.
|
||||
|
||||
|
||||
341
release/base/help/english/regex/=
Normal file
341
release/base/help/english/regex/=
Normal file
@@ -0,0 +1,341 @@
|
||||
|
||||
archie uses ed(1) regular expressions in a number of
|
||||
commands.
|
||||
|
||||
A regular expression, on the one hand, is a string like
|
||||
any other; a sequence of characters. On the other
|
||||
hand, special characters within the string have certain
|
||||
functions which make regular expressions useful when
|
||||
trying to match portions of other strings. In the fol-
|
||||
lowing discussion and examples, a string containing a
|
||||
regular expression will be called the ``pattern'', and
|
||||
the string against which it is to be matched is called
|
||||
the ``reference string''.
|
||||
|
||||
Regular expressions allow one to search for "all strings
|
||||
ending with the letters 'ize'" or "all strings beginning
|
||||
with a number between 1 and 3 and ending in a comma".
|
||||
|
||||
In order to accomplish this, regular expressions co-opt
|
||||
the use of some characters to have special meaning.
|
||||
They also provide for these characters to lose their
|
||||
special meaning if the user so desires. The rules for
|
||||
regular expresssion are
|
||||
|
||||
|
||||
c Any character c matches itself unless it has been
|
||||
assigned other special meaning as listed below. Most
|
||||
special characters can be escaped (made to lose its
|
||||
special meaning), by placing the character '\' in front
|
||||
of it. This doesn't apply to '{' which is non-special
|
||||
until it is escaped. Thus although '*' normally has
|
||||
special meaning the string '\*' matches itself.
|
||||
|
||||
Example:
|
||||
|
||||
The pattern
|
||||
|
||||
acdef
|
||||
|
||||
matches
|
||||
|
||||
s83acdeffff or acdefsecs or acdefsecs
|
||||
|
||||
but not
|
||||
|
||||
accdef or aacde1f
|
||||
|
||||
That is it will any string that contains ``acdef'' any-
|
||||
where in the reference string.
|
||||
|
||||
Example:
|
||||
|
||||
Normally the characters '*' and '$' are special,
|
||||
but the pattern
|
||||
|
||||
a\*bse\$
|
||||
|
||||
acts as above. That is any reference string containing
|
||||
``*abse$'' as a substring will be flagged as a match.
|
||||
|
||||
|
||||
|
||||
. A period matches any character except the newline
|
||||
character. This is known as the wildcard character.
|
||||
|
||||
Example:
|
||||
|
||||
The pattern
|
||||
|
||||
....
|
||||
|
||||
will match any 4 characters in the reference string,
|
||||
except a newline character.
|
||||
|
||||
|
||||
^ If `^' appears at the begining of the pattern then it
|
||||
is said to ``anchor'' the match to the beginning of the
|
||||
line. That is, the reference string must start with the
|
||||
pattern following the `^'. If this character appears
|
||||
anywhere else other than at the beginning of the line,
|
||||
then it is no longer considered special, and matches
|
||||
itself as any non-special character would. Similarly if
|
||||
it starts a string but is escaped, it matches itself.
|
||||
|
||||
Example:
|
||||
|
||||
The pattern
|
||||
|
||||
^efghi
|
||||
|
||||
Will match
|
||||
|
||||
efghi or efghijlk
|
||||
|
||||
but not
|
||||
|
||||
abcefghi
|
||||
|
||||
That is the pattern will match only those reference
|
||||
strings starting with ``efghi''. Just containing the
|
||||
substring is not sufficient.
|
||||
|
||||
|
||||
$ Occurring at the end of the pattern, this character
|
||||
``anchors'' the pattern to the end of the line (refer-
|
||||
ence string). A '$' occurring anywhere else in the pat-
|
||||
tern is regarded as a non-special. Similarly if it is
|
||||
at the end of the pattern but is escaped, it is non-
|
||||
special.
|
||||
|
||||
Example:
|
||||
|
||||
The pattern
|
||||
|
||||
efghi$
|
||||
|
||||
Will match
|
||||
|
||||
efghi or abcdefghi
|
||||
|
||||
but not
|
||||
|
||||
efghijkl
|
||||
|
||||
That is the pattern will match only those reference
|
||||
strings ending with ``efghi''. Just containing the sub-
|
||||
string is not sufficient.
|
||||
|
||||
|
||||
\< This sequence in the pattern causes the one character
|
||||
regular expression following it only to match something
|
||||
at the beginning of a word: the beginning of a line or
|
||||
just before a letter, digit or underline character, or
|
||||
just after a charcter which is not one of these.
|
||||
|
||||
Example:
|
||||
|
||||
The pattern
|
||||
|
||||
\<abc
|
||||
|
||||
would match the last 'abc' in the reference string
|
||||
|
||||
@hijabc#+abc
|
||||
|
||||
but not the first since the first 'abc' did not start
|
||||
on a ``word'' boundary.
|
||||
|
||||
|
||||
\> Constrains the one-character regular expression fol-
|
||||
lowing it to be at the end of a ``word'' as defined
|
||||
above.
|
||||
|
||||
|
||||
[string]
|
||||
|
||||
One or more characters within square brackets. This
|
||||
pattern matches any single character within the brack-
|
||||
ets. The caret, '^', has a special meaning if it is the
|
||||
first character in the series: the pattern will match
|
||||
any character other than one in the list.
|
||||
|
||||
Example:
|
||||
|
||||
The pattern
|
||||
|
||||
[^abc]
|
||||
|
||||
Will match any character except 'a', 'b' or 'c'.
|
||||
|
||||
To match a right bracket, ']', in the list it must be
|
||||
put first:
|
||||
|
||||
[]ab01]
|
||||
|
||||
For a caret, '^', in the list it can appear anywhere
|
||||
but first.
|
||||
|
||||
In
|
||||
|
||||
[ab^01]
|
||||
|
||||
the caret loses its special meaning.
|
||||
|
||||
|
||||
The '-' character is special within square brackets. It
|
||||
is interpreted as a range of characters (in the ASCII
|
||||
character set) and will match any single character
|
||||
within that range. '[a-z]' matches any lower case
|
||||
letter. The '-' can be made non special by placing it
|
||||
first or last within the square brackets.
|
||||
|
||||
|
||||
The characters '$', '*' and '.' are not special within
|
||||
square brackets.
|
||||
|
||||
|
||||
Example:
|
||||
|
||||
The pattern
|
||||
|
||||
[ab01]
|
||||
|
||||
matches a single occurence of a character from the set
|
||||
'a', 'b', '0', '1'.
|
||||
|
||||
Example:
|
||||
|
||||
The pattern
|
||||
|
||||
[^ab01]
|
||||
|
||||
will match any single character other than 'a', 'b',
|
||||
'0', '1'.
|
||||
|
||||
|
||||
Example :
|
||||
|
||||
The pattern
|
||||
|
||||
[a0-9b]
|
||||
|
||||
which matches one of 'a', 'b' or a digit between 0 and
|
||||
9 inclusive.
|
||||
|
||||
Example :
|
||||
|
||||
The pattern
|
||||
|
||||
[^a0-9b.$]
|
||||
|
||||
|
||||
means any single character not 'a', 'b' '.' , '$' or a
|
||||
digit between 0 and 9 inclusive.
|
||||
|
||||
* An asterisk following a regular expression in the pat-
|
||||
tern has the effect of matching zero or more
|
||||
occurrences of that expression.
|
||||
|
||||
Example:
|
||||
|
||||
The pattern
|
||||
|
||||
a*
|
||||
|
||||
means zero or more occurrences of the character 'a'.
|
||||
|
||||
|
||||
Example:
|
||||
|
||||
The pattern
|
||||
|
||||
[A-Z]*
|
||||
|
||||
means zero or more occurrences of the upper case alpha-
|
||||
bet.
|
||||
|
||||
|
||||
|
||||
|
||||
\{m\}
|
||||
|
||||
\{m,\}
|
||||
|
||||
\{m,n\}
|
||||
|
||||
A one-character regular expression followed by one of
|
||||
the three of these constructions causes a range of
|
||||
occurrences of that regular expression to be matched.
|
||||
If it is followed by \{m\} where m is a non-negative
|
||||
integer between 0 and 255 (inclusive), then exactly m
|
||||
occurrences of that regular expression are matched. If
|
||||
followed by \{m,\}, then at least m occurrences are
|
||||
matched. Finally, if it is followed by \{m,n\} (where
|
||||
n is a non-negative integer between 0 and 255 and where
|
||||
n > m), then between m and n occurrences of the expres-
|
||||
sion are matched.
|
||||
|
||||
Example:
|
||||
|
||||
The pattern
|
||||
|
||||
ab\{3\}
|
||||
|
||||
would match any substring in the reference string of an
|
||||
'a' followed by exactly 3 'b's.
|
||||
|
||||
Example:
|
||||
|
||||
The pattern
|
||||
|
||||
ab\{3,\}
|
||||
|
||||
would match any substring in the reference string of an
|
||||
'a' followed by at least 3 'b's.
|
||||
|
||||
|
||||
Example:
|
||||
|
||||
The pattern
|
||||
|
||||
ab\{3,5\}
|
||||
|
||||
would match any substring in the reference string of an
|
||||
'a' followed by at least 3 but at most 5 'b's.
|
||||
|
||||
|
||||
Common Problems with Regular Expression
|
||||
|
||||
|
||||
(1) When matching a substring it is not necessary to use
|
||||
the wildcard character to match the part of the refer-
|
||||
ence string preceeding and following the substring.
|
||||
|
||||
Example:
|
||||
|
||||
The pattern
|
||||
|
||||
abcd
|
||||
|
||||
will match any reference string containing this pat-
|
||||
tern. It is not necessary to use
|
||||
|
||||
.*abcd.*
|
||||
|
||||
as the pattern.
|
||||
|
||||
|
||||
(2) In order to constrain a pattern to the entire reference
|
||||
pattern, use the the construction:
|
||||
|
||||
^pattern$
|
||||
|
||||
|
||||
(3) The easiest way to obtain case insensitivity in a regu-
|
||||
lar expression is to use the '[]' operator. For exam-
|
||||
ple, a pattern to match the word ``hello'' regarless of
|
||||
the case of the letters would be:
|
||||
|
||||
[Hh][Ee][Ll][Ll][Oo]
|
||||
|
||||
4
release/base/help/english/servers/=
Normal file
4
release/base/help/english/servers/=
Normal file
@@ -0,0 +1,4 @@
|
||||
|
||||
The 'servers' command prints the list of publicly available
|
||||
archie servers known to this site.
|
||||
|
||||
34
release/base/help/english/set/=
Normal file
34
release/base/help/english/set/=
Normal file
@@ -0,0 +1,34 @@
|
||||
|
||||
The 'set' command allows you to set one of archie's variables. Their
|
||||
values affect how archie interacts with the user. archie distinguishes
|
||||
between three types of variable: "boolean", which may be either set or
|
||||
unset, "numeric", representing an integer within a pre-determined range,
|
||||
and "string", whose value is a string of characters (which may or may
|
||||
not be restricted).
|
||||
|
||||
Currently, the variables that may be set are:
|
||||
|
||||
|
||||
autologout - numeric. Number of minutes before automatic log out
|
||||
compress - string. Compression algorithm to be used
|
||||
encode - string. Encoding algorithm to be used
|
||||
(with compress)
|
||||
language - string. Language of help facility
|
||||
mailto - string. Address that output is to be mailed to
|
||||
match_domain - string. List of domains of sites for matches
|
||||
match_path - string. List of filename components for matches
|
||||
maxhits - numeric. 'find' stops after this many hits
|
||||
maxhitspm - numeric. Max number of hits per given filename
|
||||
maxmatch - numeric. Max number of filenames to return
|
||||
max_split_size - numeric. Approx. max size of file part to be mailed
|
||||
output_format - string. How the output is to be displayed
|
||||
pager - boolean. If set, use the pager, otherwise don't
|
||||
search - string. How 'find' is to search the database
|
||||
sortby - string. How 'find' output is to be sorted
|
||||
status - boolean. Report how the search is progressing
|
||||
term - string. Describes your terminal
|
||||
|
||||
|
||||
Each variable has a corresponding subtopic entry under 'set'. See them for
|
||||
more details. Also, see help on 'unset' and 'show'.
|
||||
|
||||
14
release/base/help/english/set/autologout/=
Normal file
14
release/base/help/english/set/autologout/=
Normal file
@@ -0,0 +1,14 @@
|
||||
|
||||
By default, archie will exit after one hour of idle time. This value can be
|
||||
changed though the 'autologout' variable, which represents, in minutes, the
|
||||
length of idle time before you are logged out.
|
||||
|
||||
The minimum and maximum values are 1 and 300, representing one minute
|
||||
through five hours.
|
||||
|
||||
Example:
|
||||
|
||||
set autologout 45
|
||||
|
||||
will cause you to be automatically logged out after 45 minutes of idle time.
|
||||
|
||||
5
release/base/help/english/set/compress/=
Normal file
5
release/base/help/english/set/compress/=
Normal file
@@ -0,0 +1,5 @@
|
||||
|
||||
This variable determines the kind of data compression
|
||||
the user can specify when mailing back output.
|
||||
Currently allowed values are "none" and "compress"
|
||||
(standard UNIX compress program) with a default of "none"
|
||||
6
release/base/help/english/set/encode/=
Normal file
6
release/base/help/english/set/encode/=
Normal file
@@ -0,0 +1,6 @@
|
||||
This variable determins the type of post-compression
|
||||
encoding the user can specify when mailing back output.
|
||||
Currently allowed values are "none" and "uuencode", with
|
||||
a default of "none". Note that this variable is ignored
|
||||
unless compression is enabled (via the compress)
|
||||
variable.
|
||||
3
release/base/help/english/set/language/=
Normal file
3
release/base/help/english/set/language/=
Normal file
@@ -0,0 +1,3 @@
|
||||
This variable allows the user to specify the language in
|
||||
which the help, etc. is presented. Individual servers
|
||||
may be configured for a range of languages.
|
||||
30
release/base/help/english/set/mailto/=
Normal file
30
release/base/help/english/set/mailto/=
Normal file
@@ -0,0 +1,30 @@
|
||||
|
||||
'mailto' is a string variable whose value is a mail address (or
|
||||
comma-separated list of addresses). If this is set and the 'mail'
|
||||
command is issued with no arguments, then the output of the last command
|
||||
is mailed to that address.
|
||||
|
||||
Example:
|
||||
|
||||
set mailto user@frobozz.com
|
||||
|
||||
Example:
|
||||
|
||||
set mailto user1@hello.edu,user2@goodbye.com
|
||||
|
||||
All the various Internet addressing styles are understood. BITNET sites
|
||||
should use the convention
|
||||
|
||||
user@sitename.bitnet
|
||||
|
||||
UUCP addresses can be specified as
|
||||
|
||||
user@sitename.uucp
|
||||
|
||||
If you would like to mail to an Internet IP address then use '[]'.
|
||||
|
||||
Example:
|
||||
|
||||
set mailto bajan@[132.206.44.5]
|
||||
|
||||
|
||||
28
release/base/help/english/set/match_domain/=
Normal file
28
release/base/help/english/set/match_domain/=
Normal file
@@ -0,0 +1,28 @@
|
||||
'match_domain' is a string variable which allows you to restrict the scope
|
||||
of your search by only matching results at those sites which are in the
|
||||
pseudo-domain list you have set.
|
||||
|
||||
See help on the 'domains' command for an explanation of archie
|
||||
psuedo-domains.
|
||||
|
||||
The syntax for this command is:
|
||||
|
||||
set match_domain <pseudo-domain>[[':'<pseduo-domain>]...]
|
||||
|
||||
therefore you could say
|
||||
|
||||
set match_domain ca:mx:uk
|
||||
|
||||
which would restrict your search to sites in Canada ("ca"), Mexico
|
||||
("mx") and the United Kingdom ("uk")
|
||||
|
||||
Comparisons between the domain restrictions given and any site name are
|
||||
case insensitive and performed from right to left. Therefore the
|
||||
pseudo-domain list "EDU:va.us" will match any sites ending in "edu" or
|
||||
in "va.us" (educational US sites and some of those in Virginia).
|
||||
|
||||
DNS names to any level may be supplied. You may use any combination of
|
||||
real DNS domains and pseudo-domains to specify the restriction criteria,
|
||||
however, any pseudo-domain specified must be supported by the current
|
||||
server. See the "domains" command for a further explanation and list of
|
||||
domains supported.
|
||||
22
release/base/help/english/set/match_path/=
Normal file
22
release/base/help/english/set/match_path/=
Normal file
@@ -0,0 +1,22 @@
|
||||
The 'match_path' string variable allows you to restrict your search based
|
||||
on pathname components. For example, if you are only looking for DOS PC
|
||||
programs and think that site administrators may have put such files in
|
||||
directories with names like "PC", "DOS" or "IBM" then you could set the
|
||||
match_path variable as:
|
||||
|
||||
set match_path PC:DOS:IBM
|
||||
|
||||
All files returned must have one or more of these components in its
|
||||
pathname (the list of directories leading to the file or directory).
|
||||
|
||||
The general syntax is:
|
||||
|
||||
set match_path <component>[[':'<component>]...]
|
||||
|
||||
Note that the component names are always matched on a case-insensitive
|
||||
basis. Also, there is an implicit logical OR between components: in the
|
||||
example above the system matches it as "PC or DOS or IBM" so that if any
|
||||
one of the components match, then the condition is satisfied.
|
||||
|
||||
|
||||
|
||||
7
release/base/help/english/set/max_split_size/=
Normal file
7
release/base/help/english/set/max_split_size/=
Normal file
@@ -0,0 +1,7 @@
|
||||
This variable set the approximate maximum size, in
|
||||
bytes, of a file to be mailed to the user. Any output
|
||||
larger than this limit will be split in pieces of about
|
||||
this size. This can be set by the user in the range 1024
|
||||
to ~2Gb with a default of 51200 bytes. Some mail
|
||||
gateways will not allow results of over 100Kb and so
|
||||
care should be taken when setting this limit.
|
||||
55
release/base/help/english/set/maxhits/=
Normal file
55
release/base/help/english/set/maxhits/=
Normal file
@@ -0,0 +1,55 @@
|
||||
|
||||
You can control the number of results returned in the archie system by 3
|
||||
variables. 'maxhits', 'maxmatch' and 'maxhitspm'.
|
||||
|
||||
'maxhits' is a numeric variable whose value is the maximum number of
|
||||
matches you want the 'find' command to generate.
|
||||
|
||||
If archie seems to be slow, or you don't want a lot of output this can be
|
||||
set to a small value. "maxhits" must be within the range 0 to 1000. The
|
||||
default value is 1000.
|
||||
|
||||
Example:
|
||||
|
||||
set maxhits 100
|
||||
|
||||
'find' will now stop after 100 matches have been found
|
||||
|
||||
There are 2 variables which work with the 'maxhits' variable to modify
|
||||
the behavior of the search mechanism. They are 'maxmatch' and
|
||||
'maxhitspm'. The database can be viewed as follows:
|
||||
|
||||
|
||||
filename1 ----> file1 -> file2 -> file3
|
||||
|
|
||||
V
|
||||
filename2 ----> file1 -> file2 -> file3 -> file4
|
||||
|
|
||||
V
|
||||
filename3 ----> file1
|
||||
|
|
||||
V
|
||||
(etc)
|
||||
|
||||
Each filename can have several files associated with it which share that
|
||||
name. For example, the string "README" is only stored once but points to
|
||||
the information for each of the files in the database called README
|
||||
spread around all the anonymous FTP sites on the Internet (which, as you
|
||||
can imagine are numerous).
|
||||
|
||||
The maximum total number of "files" (hits) returned is determined by the
|
||||
'maxhits' variable. The maximum number of filenames that match is
|
||||
determined by the 'maxmatch' variable. Finally if you only want to
|
||||
return a limited number of files for each filename matched, use the
|
||||
'maxhitspm' variable.
|
||||
|
||||
If you do the following:
|
||||
|
||||
set maxhits 20
|
||||
set maxmatch 5
|
||||
set maxthitspm 7
|
||||
|
||||
Then you will match at most 5 filenames. For each filename you will be
|
||||
given back at most 7 files with that name. However, in total you will
|
||||
only be returned 20 hits, since maxhits operates on the total number
|
||||
regardless of the the combinations of the hits.
|
||||
55
release/base/help/english/set/maxhitspm/=
Normal file
55
release/base/help/english/set/maxhitspm/=
Normal file
@@ -0,0 +1,55 @@
|
||||
|
||||
You can control the number of results returned in the archie system by 3
|
||||
variables. 'maxhits', 'maxmatch' and 'maxhitspm'.
|
||||
|
||||
'maxhits' is a numeric variable whose value is the maximum number of
|
||||
matches you want the 'find' command to generate.
|
||||
|
||||
If archie seems to be slow, or you don't want a lot of output this can be
|
||||
set to a small value. "maxhits" must be within the range 0 to 1000. The
|
||||
default value is 1000.
|
||||
|
||||
Example:
|
||||
|
||||
set maxhits 100
|
||||
|
||||
'find' will now stop after 100 matches have been found
|
||||
|
||||
There are 2 variables which work with the 'maxhits' variable to modify
|
||||
the behavior of the search mechanism. They are 'maxmatch' and
|
||||
'maxhitspm'. The database can be viewed as follows:
|
||||
|
||||
|
||||
filename1 ----> file1 -> file2 -> file3
|
||||
|
|
||||
V
|
||||
filename2 ----> file1 -> file2 -> file3 -> file4
|
||||
|
|
||||
V
|
||||
filename3 ----> file1
|
||||
|
|
||||
V
|
||||
(etc)
|
||||
|
||||
Each filename can have several files associated with it which share that
|
||||
name. For example, the string "README" is only stored once but points to
|
||||
the information for each of the files in the database called README
|
||||
spread around all the anonymous FTP sites on the Internet (which, as you
|
||||
can imagine are numerous).
|
||||
|
||||
The maximum total number of "files" (hits) returned is determined by the
|
||||
'maxhits' variable. The maximum number of filenames that match is
|
||||
determined by the 'maxmatch' variable. Finally if you only want to
|
||||
return a limited number of files for each filename matched, use the
|
||||
'maxhitspm' variable.
|
||||
|
||||
If you do the following:
|
||||
|
||||
set maxhits 20
|
||||
set maxmatch 5
|
||||
set maxthitspm 7
|
||||
|
||||
Then you will match at most 5 filenames. For each filename you will be
|
||||
given back at most 7 files with that name. However, in total you will
|
||||
only be returned 20 hits, since maxhits operates on the total number
|
||||
regardless of the the combinations of the hits.
|
||||
55
release/base/help/english/set/maxmatch/=
Normal file
55
release/base/help/english/set/maxmatch/=
Normal file
@@ -0,0 +1,55 @@
|
||||
|
||||
You can control the number of results returned in the archie system by 3
|
||||
variables. 'maxhits', 'maxmatch' and 'maxhitspm'.
|
||||
|
||||
'maxhits' is a numeric variable whose value is the maximum number of
|
||||
matches you want the 'find' command to generate.
|
||||
|
||||
If archie seems to be slow, or you don't want a lot of output this can be
|
||||
set to a small value. "maxhits" must be within the range 0 to 1000. The
|
||||
default value is 1000.
|
||||
|
||||
Example:
|
||||
|
||||
set maxhits 100
|
||||
|
||||
'find' will now stop after 100 matches have been found
|
||||
|
||||
There are 2 variables which work with the 'maxhits' variable to modify
|
||||
the behavior of the search mechanism. They are 'maxmatch' and
|
||||
'maxhitspm'. The database can be viewed as follows:
|
||||
|
||||
|
||||
filename1 ----> file1 -> file2 -> file3
|
||||
|
|
||||
V
|
||||
filename2 ----> file1 -> file2 -> file3 -> file4
|
||||
|
|
||||
V
|
||||
filename3 ----> file1
|
||||
|
|
||||
V
|
||||
(etc)
|
||||
|
||||
Each filename can have several files associated with it which share that
|
||||
name. For example, the string "README" is only stored once but points to
|
||||
the information for each of the files in the database called README
|
||||
spread around all the anonymous FTP sites on the Internet (which, as you
|
||||
can imagine are numerous).
|
||||
|
||||
The maximum total number of "files" (hits) returned is determined by the
|
||||
'maxhits' variable. The maximum number of filenames that match is
|
||||
determined by the 'maxmatch' variable. Finally if you only want to
|
||||
return a limited number of files for each filename matched, use the
|
||||
'maxhitspm' variable.
|
||||
|
||||
If you do the following:
|
||||
|
||||
set maxhits 20
|
||||
set maxmatch 5
|
||||
set maxthitspm 7
|
||||
|
||||
Then you will match at most 5 filenames. For each filename you will be
|
||||
given back at most 7 files with that name. However, in total you will
|
||||
only be returned 20 hits, since maxhits operates on the total number
|
||||
regardless of the the combinations of the hits.
|
||||
4
release/base/help/english/set/output_format/=
Normal file
4
release/base/help/english/set/output_format/=
Normal file
@@ -0,0 +1,4 @@
|
||||
Affects the way the output of "find" and "list" is
|
||||
displayed. User settable, with valid values of "machine"
|
||||
(machine readable format), "terse" and "verbose", with a
|
||||
default of "verbose".
|
||||
11
release/base/help/english/set/pager/=
Normal file
11
release/base/help/english/set/pager/=
Normal file
@@ -0,0 +1,11 @@
|
||||
|
||||
'pager' is a boolean variable which, when set, tells archie to filter all
|
||||
output through the pager "less".
|
||||
|
||||
It improves the look of the output (but is not necessary) if you also set
|
||||
the 'term' variable to your terminal type.
|
||||
|
||||
Example:
|
||||
|
||||
set pager
|
||||
|
||||
138
release/base/help/english/set/search/=
Normal file
138
release/base/help/english/set/search/=
Normal file
@@ -0,0 +1,138 @@
|
||||
|
||||
The 'search' variable determines the kind of search performed on the
|
||||
database by the 'prog' command, providing flexibilty on search times and
|
||||
ranges.
|
||||
|
||||
'search' is a string variable whose value is one of the following:
|
||||
|
||||
(1) "sub"
|
||||
|
||||
Substring (case insensitive). A simple, everyday substring search. A
|
||||
match occurs if the the file (or directory) name in the database
|
||||
contains the user-given substring.
|
||||
|
||||
Example:
|
||||
|
||||
"is" will match "islington" and "this" and "poison"
|
||||
|
||||
(2) "subcase"
|
||||
|
||||
Substring (case sensitive). As above but the case of the
|
||||
strings involved becomes significant.
|
||||
|
||||
Example:
|
||||
|
||||
"TeX" will match "LaTeX" but not "Latex" or "TExTroff".
|
||||
|
||||
|
||||
(3) "exact"
|
||||
|
||||
Exact match. The fastest search method of all. The restriction is
|
||||
that the user string (the argument to the 'prog' command) has to
|
||||
_exactly_ match (including case) the string in the database. This is
|
||||
provided for those of who who know just what you are looking for.
|
||||
|
||||
For example, if you wanted to know where all the "xlock.tar.Z" files
|
||||
were, this is the kind of search to use.
|
||||
|
||||
(4) "regex" This is the DEFAULT search method.
|
||||
|
||||
ed(1) regular expressions. Searches the database with the user
|
||||
(search) string which is given in the form of an ed(1) regular
|
||||
expression.
|
||||
|
||||
NOTE: Unless specifically anchored to the beginning (with ^) or end
|
||||
(with $) of a line, ed(1) regular expressions have ".*" prepended and
|
||||
appended to them. For example, it is NOT NECESSARY to say
|
||||
|
||||
prog .*xnlock.*
|
||||
|
||||
since
|
||||
prog xnlock
|
||||
|
||||
will suffice. Thus the regex match becomes a simple substring match.
|
||||
|
||||
There are also compound searches made up of combinations
|
||||
of the above search methods in sequence:
|
||||
|
||||
exact_sub Try "exact". If no matches found use
|
||||
"sub".
|
||||
exact_subcase Try "exact". If no matches found use
|
||||
"subcase"
|
||||
exact_regex Try "exact". If no matches found use
|
||||
regex.
|
||||
|
||||
|
||||
An "ed(1) regular expression" (from here on called RE) is the particular
|
||||
type of regular expression used in the "ed" editor under Unix. For those
|
||||
who are interested in all the gory details of REs see the help for
|
||||
"regex" (which is incomplete, at the moment :-(), otherwise what follows
|
||||
should be sufficient for most needs.
|
||||
|
||||
A regular expression is a convenient way to search for a set of specific
|
||||
strings matching a pattern. To be able to specify such a pattern with
|
||||
only the ordinary set of printable character we have to co-opt some of
|
||||
them. For example in a RE the period means _any_ single character,
|
||||
while an asterisk, '*', means zero or more occurences of the *PRECEDING*
|
||||
RE.
|
||||
|
||||
For example:
|
||||
|
||||
knob - matches any string containing the substring 'knob'
|
||||
|
||||
a*splat - matches strings that contain zero or more a's followed by the
|
||||
string 'splat'
|
||||
|
||||
#.*# - would match anything containing a '#' followed by zero or more
|
||||
occurences of _any_ character, followed by another '#'
|
||||
|
||||
Other special characters that may be useful are '[' and ']', which are
|
||||
used together. They can be used to specify either a set of characters
|
||||
to match or a set of characters to not match. An example of the first
|
||||
case is:
|
||||
|
||||
[abcd]
|
||||
|
||||
which matches any of one of the four letters, while an example of the
|
||||
second case is:
|
||||
|
||||
[^abcd]
|
||||
|
||||
in which the '^' _in_the_first_position_ means that any character _not_
|
||||
in the list will be matched. As well, ranges can be specified with a
|
||||
'-'.
|
||||
|
||||
[a-z]
|
||||
|
||||
matches any lower case letter and,
|
||||
|
||||
[^a-z]
|
||||
|
||||
matches any character other than a lower case letter. Furthermore, you
|
||||
can specify multiple ranges such as:
|
||||
|
||||
[%@a-z0-9]
|
||||
|
||||
or
|
||||
|
||||
[^A-Za-z]
|
||||
|
||||
meaning: match '%' or '@' or any lower case letter or digit, and match
|
||||
any character other than a letter, respectively.
|
||||
|
||||
When you want to match a character which has a special meaning you should
|
||||
precede it by a backslash, '\'.
|
||||
|
||||
Some final examples of REs are:
|
||||
|
||||
[Mm]ac\.txt - match anything containg the string "Mac.txt" or
|
||||
"mac.txt"
|
||||
|
||||
[^aeiou][^aeiou]* - match any string consisting entirely of non-vowels
|
||||
|
||||
foo-v[0-9]\.tar\.Z - match "foo-v0.tar.Z" through "foo-v9.tar.Z"
|
||||
|
||||
|
||||
Good luck, and remember that many things can be found with only a simple
|
||||
substring (e.g. latex).
|
||||
|
||||
4
release/base/help/english/set/server/=
Normal file
4
release/base/help/english/set/server/=
Normal file
@@ -0,0 +1,4 @@
|
||||
This variable determines archie/Prospero server to which
|
||||
the email interface connects when "find" or "list"
|
||||
commands are used. Usually defaults to "localhost" on
|
||||
most archie systems.
|
||||
49
release/base/help/english/set/sortby/=
Normal file
49
release/base/help/english/set/sortby/=
Normal file
@@ -0,0 +1,49 @@
|
||||
|
||||
The 'sortby' variable describes how the output from the 'prog' command
|
||||
is to be ordered. It can have one of 5 values (and their associated
|
||||
reverse orders). For each method, the "natural" sort order (or at least,
|
||||
what we consider to be the natural order) is the default.
|
||||
|
||||
The reverse sorting orders from those described here are obtained by
|
||||
prepending "r" to the 'sortby' value given. (Eg. reverse hostname order
|
||||
"hostname" is "rhostname").
|
||||
|
||||
|
||||
(1) "hostname"
|
||||
|
||||
Output is sorted on the archive hostname in lexical order.
|
||||
|
||||
Reverse order "rhostname".
|
||||
|
||||
(2) "time"
|
||||
|
||||
Output is sorted with the most recent modifcation times of the found
|
||||
file/directory names coming first (youngest -> oldest).
|
||||
|
||||
Reverse order "rtime".
|
||||
|
||||
(3) "size"
|
||||
|
||||
Output is sorted by the size of the found files/directories, largest
|
||||
first.
|
||||
|
||||
Reverse order "rsize".
|
||||
|
||||
(4) "filename"
|
||||
|
||||
Sorted in file/directory name lexical order.
|
||||
|
||||
Reverse order "rfilename".
|
||||
|
||||
(5) "none" This is the DEFAULT order.
|
||||
|
||||
Unsorted. There is no reverse order although "rnone" is accepted for
|
||||
symmetry.
|
||||
|
||||
|
||||
Typing the keyboard interrupt character ( Ctl-C for most people on UNIX)
|
||||
during a search will cause the search to aborted. The results up to that
|
||||
time will be sorted (determined by the value of the sortby variable) and
|
||||
the results output. This output phase may be aborted by typing the abort
|
||||
character a second time.
|
||||
|
||||
22
release/base/help/english/set/status/=
Normal file
22
release/base/help/english/set/status/=
Normal file
@@ -0,0 +1,22 @@
|
||||
The 'status' variable is a boolean value:
|
||||
|
||||
set status
|
||||
|
||||
turns it on and
|
||||
|
||||
unset status
|
||||
|
||||
turns it off. When set in interactive mode, it will display the queue
|
||||
position of your request and the estimated time for completion of the
|
||||
request in minutes and seconds.
|
||||
|
||||
The estimated time is an average of the time taken for the previous 10
|
||||
similar requests completed by the current server. The queue position is
|
||||
determined by the type of request. For example, "exact" matches have
|
||||
priorities over all other match types since they are the fasted to
|
||||
complete.
|
||||
|
||||
The variable also turns on a moving 'marker' which indicates that the
|
||||
system is processing your request.
|
||||
|
||||
Setting this variable has no effect in the email interface.
|
||||
22
release/base/help/english/set/term/=
Normal file
22
release/base/help/english/set/term/=
Normal file
@@ -0,0 +1,22 @@
|
||||
|
||||
The 'term' variable tells archie what type of terminal you are using, and
|
||||
optionally its size in rows and columns. This information is used by the
|
||||
pager.
|
||||
|
||||
The usage is:
|
||||
|
||||
set term <terminal-type> [<#rows> [<#columns>]]
|
||||
|
||||
That is, the terminal type is required, but the number of rows and
|
||||
columns is optional. You may specify a value for rows only, but if you
|
||||
want to change the number of columns you must give a value for _both_
|
||||
rows and columns. The default values for rows and columns are 24 and 80.
|
||||
|
||||
Examples:
|
||||
|
||||
set term vt100
|
||||
|
||||
set term xterm 60
|
||||
|
||||
set term xterm 24 100
|
||||
|
||||
17
release/base/help/english/show/=
Normal file
17
release/base/help/english/show/=
Normal file
@@ -0,0 +1,17 @@
|
||||
|
||||
'show' is used to display the value of a particular variable, or all
|
||||
variables. Its usage is:
|
||||
|
||||
show <variable-name>
|
||||
|
||||
to display the value of a particular variable, or
|
||||
|
||||
show
|
||||
|
||||
to display the value of all variables.
|
||||
|
||||
Example:
|
||||
|
||||
show maxhits
|
||||
|
||||
|
||||
5
release/base/help/english/site/=
Normal file
5
release/base/help/english/site/=
Normal file
@@ -0,0 +1,5 @@
|
||||
|
||||
Due to ongoing changes in the archie system, the "site" command is no
|
||||
longer available. We hope to re-enable this command in the near future.
|
||||
|
||||
|
||||
11
release/base/help/english/stty/=
Normal file
11
release/base/help/english/stty/=
Normal file
@@ -0,0 +1,11 @@
|
||||
stty [<option> <character>] ...
|
||||
|
||||
This command allows the user to change the interpretation of specified
|
||||
characters, in order to match their particular terminal type. At the
|
||||
moment only `erase' is recognized as an <option>. (Typically,
|
||||
<character> is a control character and may be specified as a pair of
|
||||
characters (e.g. control-h as the pair ^h), the character itself
|
||||
(literal), or as a quoted pair or literal.
|
||||
|
||||
Without any arguments the command displays the current values of the
|
||||
recognized options.
|
||||
4
release/base/help/english/term/=
Normal file
4
release/base/help/english/term/=
Normal file
@@ -0,0 +1,4 @@
|
||||
|
||||
This command has been superceded by the 'term' variable and will go away
|
||||
in the near future. See help for 'set term' for details.
|
||||
|
||||
16
release/base/help/english/unset/=
Normal file
16
release/base/help/english/unset/=
Normal file
@@ -0,0 +1,16 @@
|
||||
|
||||
Usage:
|
||||
|
||||
unset <variable-name>
|
||||
|
||||
'unset' causes the specified variable to _have_no_value_. This means that
|
||||
it will not be used by archie until it has been given a value with the 'set'
|
||||
command.
|
||||
|
||||
|
||||
Note: this may cause "counter-intuitive" behaviour in some cases (e.g. in
|
||||
the case of "maxhits"). Although one might expect 'prog' to print
|
||||
matches without regard for any limit, this is not the case. If the
|
||||
value of "maxhits" is not available it will merely fall back to some
|
||||
internal default.
|
||||
|
||||
6
release/base/help/english/version/=
Normal file
6
release/base/help/english/version/=
Normal file
@@ -0,0 +1,6 @@
|
||||
|
||||
The version command prints out the current version number
|
||||
for this program.
|
||||
|
||||
|
||||
|
||||
42
release/base/help/english/whatis/=
Normal file
42
release/base/help/english/whatis/=
Normal file
@@ -0,0 +1,42 @@
|
||||
|
||||
Usage:
|
||||
|
||||
whatis <substring>
|
||||
|
||||
The 'whatis' command searches the archie Software Description database
|
||||
for the given substring, with case being ignored. This database consists
|
||||
of names and short descriptions of many of the software packages,
|
||||
documents (like RFCs and educational material) and datafiles that are
|
||||
stored on the Internet.
|
||||
|
||||
Example:
|
||||
|
||||
whatis uucp
|
||||
|
||||
in part gives as a result:
|
||||
|
||||
|
||||
RFC 976 Horton, M.R. UUCP mail interchange format
|
||||
standard. 1986 February; 12 p.
|
||||
cu-shar Allows kermit, cu, and UUCP to all share the
|
||||
same lines
|
||||
detm-unbatch Cleans up TM files left in the UUCP spool
|
||||
directory by the news batching software
|
||||
fido-usenet-gw Implement a gateway between UUCP/Usenet/Mail
|
||||
and Fidonet
|
||||
findpath.sh UUCP Pathfinder
|
||||
logfile-stats UUCP LOGFILE analyzer
|
||||
mapstats UUCP map statistics program
|
||||
nmail Do UUCP mail routing using the output of the
|
||||
pathalias(1) program
|
||||
|
||||
|
||||
We welcome and encourage additions and corrections to this database and
|
||||
depend on the archie user community to keep it uptodate. To make your
|
||||
contribution to this database, mail to
|
||||
|
||||
|
||||
archie-admin@bunyip.com
|
||||
|
||||
For new additions, please keep the description to 25 words or less.
|
||||
|
||||
Reference in New Issue
Block a user