--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/adduser.man	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,132 @@
+
+
+     ADDUSER                          UUCP                          ADDUSER
+
+
+     PROGRAM   
+
+          adduser
+
+     CALLING SEQUENCE: 
+
+          adduser
+          adduser <username>
+          adduser <username> <userid>
+          adduser -r <username>
+          adduser -s
+          adduser -s <username>
+
+     SUMMARY:  
+
+          Add user to or remove user from the system
+
+     DESCRIPTION:   
+
+          ADDUSER is used to add a new user or remove a current user from 
+          the system with a minimum of input from the system administrator 
+
+          When adding a user to the system a new entry is created in the 
+          /DD/SYS/password file for the new user as is a mail and home 
+          directory.  A user login file, <username>.login, is created in 
+          /DD/LOG. Next, the user's login script 'ulogin' is created in the 
+          user's home directory.  ADDUSER will ask if you wish to create a 
+          customized ulogin script or use the default version.  If you 
+          choose to create a customized script, ADDUSER will prompt you for 
+          the entries.  
+
+          If the command line contains no arguments, ADDUSER will prompt 
+          you for the username and then a user ID number.  You may choose a 
+          user ID or allow ADDUSER to pick the lowest unused user ID.  
+          Specifying -s on the command line allows ADDUSER to consider 
+          super user ID's if there is room; otherwise, user IDs above the 
+          super user range will be considered.  (OS-9/68K systems can have 
+          256 super users, from 0.0 to 0.255). If ADDUSER is allowed to 
+          choose the user ID, it will pick the lowest unused ID.  
+
+          If the command line contains a user name, ADDUSER will use this 
+          name and prompt for the user's ID.  
+
+          If the command lines contains both name and user ID, ADDUSER will 
+          use these.  
+
+          In all cases, ADDUSER will inform you if the name or ID is 
+          already being used and prompt to try again.  
+
+          When removing a user, ADDUSER will remove the password file 
+          entry, the /DD/LOG/<username>.login file as well as the user home 
+          and mail directories.  All files and subdirectories in the user's 
+          home and mail directories will be deleted as well.  
+
+
+
+
+
+                                                                           
+
+
+
+
+     ADDUSER                          UUCP                          ADDUSER
+
+
+     RESTRICTIONS   
+
+          Only the superuser (user ID 0) can use this utility 
+
+     BUGS   
+
+          The removing a user feature is not implemented yet.  
+
+          If ADDUSER aborts because of an error, you will probably need to 
+          manually remove the user's password file entry as well as the 
+          user's /DD/LOG/<user>.login as well the home and mail directories 
+          entries before trying again.  If you don't, ADDUSER may tell you 
+          the user already exists.  
+
+     FILES   
+
+          /DD/LOG/<user>.login
+          /DD/<user_home_dir>/ulogin
+          /DD/<mail_directory>/<user>
+          /DD/SYS/password
+
+     SEE ALSO 
+
+          uusetup, login 
+
+     THANKS   
+
+          This program was original written by Mark Griffith for his OS-9 
+          UUCP package.  Thanks to Mark for his okay-dokey to modify the 
+          code to work with this UUCP package as well.  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/aliases.doc	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,132 @@
+
+
+     aliases                          UUCP                          aliases
+
+
+     FILE   
+
+          /DD/<homedir>/<user>/UUCP/aliases      (CoCo)
+          /DD/<homedir>/<user>/.aliases          (OSK)
+
+     SUMMARY:   
+
+          This file contains a list of commonly-used mail addresses.
+
+     DESCRIPTION:   
+
+
+          Each user may put an "aliases" file in their home directory.  On 
+          the CoCo the file goes in the UUCP directory in the user's home 
+          directory.  Under OSK the alias file goes in the user's root home 
+          directory and is called .aliases (note the initial period 
+          character).  The alias file is used to keep track of 
+          commonly-used mail addresses.  Each alias is entered in the file 
+          one to a line.  The format for an entry is: 
+
+               alias [name_string] uucp_address 
+
+          The name_string field is optional.  The simplest alias entry is a 
+          simple name for the alias such as "fred", "barney", "joe" etc.  
+          This is followed by one or more spaces and then the UUCP mail 
+          address of that person, such as: gigsys!evil!purple!barney.  
+
+          The second form is a simple name followed by one or more spaces 
+          with a string followed by one or more spaces and the UUCP mail 
+          address.  name_string can be put in double quotes, but this not 
+          necessary.  The name_string field is for compatibility with Jeff 
+          Shepler's mailer, Palm. Both Mailx and Palm share the same 
+          aliases file.  This version of Mailx ignores the name_string 
+          field.  Only the leftmost and rightmost fields are used.  The 
+          uucp_address field may either be a bang path or domain style 
+          address.  Lines starting with either a '#', '*', or a carriage 
+          return, are considered comment lines and ignored.  
+
+          Each user maintains their own "aliases" file, at their 
+          discretion.  They may then use the alias name rather than the 
+          full UUCP mail address when sending mail.  The mail program will 
+          automatically look up the given address in the user's alias file, 
+          looking for substitutions to be made.  The full UUCP address is 
+          used in the mail header.  Once a match is found, no further 
+          searches are made.  Thus, if you have two entries: 
+
+               bob  postmaster
+               [lots more entries]
+               bob  wa2egp@delphi.com
+
+          The mail will end up going to 'postmaster' even though you 
+          thought it would go to 'wa2egp@delphi.com 
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     aliases                          UUCP                          aliases
+
+
+          EXAMPLE: 
+
+               #This is an sample aliases file:
+               
+               * CoCo BITNET list
+               coco coco@pucc.princeton.edu
+               
+               * CoCo listserver
+               listserv fdurt1!pucc.princeton.edu!LISTSERV
+               
+               bob  Bob Billson  bob@kc2wz.bubble.org
+               #
+               # test path
+               #
+               loopback fico!ccentral!rickadams
+               boisy  "Boisy Pitre"  boisy@os9er.waukee.ia.us
+               wa2egp wa2egp@delphi.com
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/chown.man	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,66 @@
+
+
+     CHOWN                                                            CHOWN
+
+
+     PROGRAM   
+
+          chown
+
+     CALLING SEQUENCE: 
+
+          chown <username_or_ID>  <file_or_dir>  [<file_or_dir>...]
+
+     SUMMARY   
+
+          Change ownership of a file or directory to that of another user 
+
+     DESCRIPTION   
+
+          CHOWN allows a user to change the ownership of a file and/or 
+          directory belonging to them to that of another user.  The user 
+          cannot change the ownership of a file or directory if it does not 
+          belong to them.  The only exception to this is the superuser.  
+          He/she can change the ownership of anyone's file or directory to 
+          that of anyone else 
+
+          Either the user's name or the decimal value of the user's ID as 
+          listed in the password file maybe be given.  File and directory 
+          names may be mixed on the command line.  
+
+     FILES   
+
+          /DD/SYS/password
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/cnvrtmail.man	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,198 @@
+
+
+     CNVRTMAIL                        UUCP                        CNVRTMAIL
+
+
+     PROGRAM   
+
+          cnvrtmail
+
+     CALLING SEQUENCE: 
+
+          cnvrtmail [opt]
+          
+          opt:  -k   = delete user's old mail file
+
+     SUMMARY:   
+
+          Convert Rick's Adams spool mail format v4.2 and earlier to new 
+          format used by UUCPbb package.  
+
+     DESCRIPTION:   
+
+          Rick Adams' original mail format keeps all the mail in one 
+          directory.  Each user's mailbox is a separate file in this mail 
+          directory.  The disadvantage with this format is it slow on the 
+          CoCo. If the mail file grew too large, there was the danger of 
+          file segment error.  Deleting and saving mail was slow as well.  
+
+          The new mail format keeps the original mail directory.  However, 
+          the mailbox file is replaced with a mailbox directory for each 
+          user.  Each message is stored as an individual file.  The file's 
+          name is 'mYYYYMMDDHHMMSS' where YYYYMMDDHHMMSS is the year, 
+          month, day, hour, minute and second that RMAIL processed the 
+          message.  Using this format it is much easier to manipulate each 
+          message.  
+
+          There is another file in each user's mailbox directory called 
+          'mail..list'.  This file keeps an ordered list of the mailbox 
+          contents.  mail..list is used by MAIL to keep track of 
+          information about each message.  RMAIL updates this file as mail 
+          is processed.  MAIL also updates this file when mail is deleted 
+          or if it detects an error in the file.  
+
+          CNVRTMAIL makes it easier to convert from Rick's old format to 
+          the new one.  If you have never previous run Rick's original UUCP 
+          program, there is no reason to use CNVRTMAIL. CNVRTMAIL assumes 
+          the current mailbox is in the old format.  
+
+          When first run, CNVRTMAIL asks to verify which users in the 
+          password file are valid mail users on the system.  This prevents 
+          creating mailboxes for remote UUCP systems as well as valid 
+          users.  After verifying users, CNVRTMAIL goes through each user 
+          creating a mailbox directory and splitting each message into 
+          individual files with unique consective timestamps.  The 
+          mail..list file is then created.  
+
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     CNVRTMAIL                        UUCP                        CNVRTMAIL
+
+
+          CNVRTMAIL defaults to saving the user's original mail in the root 
+          directory of /DD in the file named '<username>.oldmail' as a 
+          "just in case".  Once proper operation of the new mail is 
+          verified, the old mail files can be deleted.  If the commmand 
+          line option -k is used, the old mail file is deleted after the 
+          new mailbox is created.  
+
+
+     BUGS   
+
+          CNVRTMAIL is not terribly smart.  It does occasionally get 
+          confused when changing from the old to the new format.  CNVRTMAIL 
+          looks for a line starting with either the string ">From " or 
+          "From " to signal the start of a message.  If a sentence in the 
+          message body starts with either string, CNVRTMAIL thinks it is a 
+          new message.  
+
+          The easiest way to spot and fix this error is to change mailbox 
+          directory defined in the /DD/SYS/UUCP/Parameters file.  The 
+          parameter 'maildir' points to the mailbox directory.  Look in 
+          each user's mailbox directory at the file 'mail..list' when 
+          CNVRTMAIL is finished.  These two lines from a mail..list file 
+          will illustrate the procedure: 
+
+     Nm19930613000917|UICVM.UIC.EDU!BRAMSAT%BRFA|RS14/AO21 2nd Bull|122|7290
+     Nm19930613000924| | |20|1478
+     ^|_____________| ^ ^  ^  ^
+     |      |         | |  |  |___ file size
+     |      |         | |  |______ number of lines
+     |      |         | |_________ Subject:
+     |      |         |___________ From:
+     |      |_____________________ file name
+     |____________________________ message status
+
+               Line #2 above is missing both the From: and Subject: 
+               fields.  While the Subject: field may occasionally be empty, 
+               the From: never should be.  If you list file 
+               'm19930613000924 you will probably find the line reads, for 
+               example: 
+
+               >From the dawn of time, this mail was waiting...
+
+               This "message" actually belongs to the file in the line 
+               above, i.e.  m19930613000917.  With a text editor combine 
+               the second message with the first, be sure to removed the 
+               '>' from '>From'. Save the restored message out and delete 
+               the incorrect message file.  
+
+               You could edit the incorrect line mail..list.  This not 
+               necessary, however.  As long as you delete the incorrect 
+               message, MAILX will reconstruct mail..list the next time the 
+               user's mail is read.  
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     CNVRTMAIL                        UUCP                        CNVRTMAIL
+
+
+               --IMPORTANT--: Be sure you set the owner ID of any changed 
+               files to the owner ID of the mailbox.  If you do not do 
+               this, the mail cannot be read by its owner!  You can use the 
+               CHOWN utility, which is included in the UUCPbb package, to 
+               do this.  
+
+          FILES   
+
+               /DD/<username>.oldmail
+               /DD/<mail_dir>/<user>/mYYYYMMDDHHMMSS
+               /DD/<mail_dir>/<user>/mail..list
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/fileserv.man	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,198 @@
+
+
+     FILESERV                         UUCP                         FILESERV
+
+
+     PROGRAM:   
+
+          fileserv
+
+     CALLING SEQUENCE: 
+
+          fileserv
+
+     SUMMARY:   
+
+          Process commands sent to OS-9 fileserver by email.
+
+     DESCRIPTION:   
+
+          FileServ is an simple OS-9 fileserver program for use with the 
+          UUCPbb package.  FileServ is never run directly by a user.  It is 
+          forked by RMAIL when mail is sent to a special local "user": 
+          fileserv (note the spelling).  
+
+          The fileserver is turned on by setting two parameters in the 
+          /DD/SYS/UUCP/Parameters file: 'server' and 'fileserver'. If 
+          'server' is set to 'off', 'no' or the parameter is missing, the 
+          server is inactive.  If the parameter 'fileserver' is missing or 
+          the directory it points to is not readable by user 0 (superuser), 
+          the fileserver is also inactive.  If the fileserver is inactive, 
+          mail sent to 'fileserv' will get a "File server not available" 
+          response.  
+
+          FileServ reads its standard input for the message contents.  The 
+          sender's return address is extracted from the header.  The 
+          Subject: line is ignored in this version.  FileServ then reads 
+          the message body looking for commands, one to a line, which it 
+          understands.  Unrecognized commands are ignored.  There are five 
+          commands which FileServ understands at present: 
+
+          reply <address> - Tells the fileserver to send its responses to 
+                            the address <address> instead the one appearing 
+                            in the message header.  This command MUST be 
+                            the first one given in the message body.  If it 
+                            is not, it is ignored and the address from the 
+                            sender's header will be used.  
+
+          help            - Sends a help file.  The name of this file is 
+                            /DD/SYS/UUCP/FileServ.help. It gives brief 
+                            description of how to use the fileserver.  You 
+                            may customize for your particular system.  The 
+                            commands and their description should not be 
+                            changed, however.  
+
+          dir [pathname]  - Gets the contents of the directory where the 
+                            publicly retrivable files are kept.  This 
+                            directory is specified in the 
+                            /DD/SYS/UUCP/Parameters by the parameter 
+                            'fileserver'. If an optional pathname is 
+
+
+
+
+                                                                           
+
+
+
+
+     FILESERV                         UUCP                         FILESERV
+
+
+                            included, FileServ assumes [pathname] is a 
+                            subdirectory within the directory specified by 
+                            the 'fileserver' parameter.  Attempts to get 
+                            illegal directories will be rejected, e.g.  
+                            /DD/SYS 
+
+          get <filename>  - Tells FileServ to look for <filename> in the 
+                            allowed files directory and send it to the 
+                            requester.  If the file has an extension 
+                            matching one in the file /DD/SYS/UUCP/bin.list, 
+                            the file will be uuencoded before sending.  
+                            <filename> can be a full pathname.  Full 
+                            pathnames are forced to be subdirectories of 
+                            the 'fileserver' directory.  For example, if 
+                            the allowed files directory is 
+                            /H1/USR/SPOOL/FILES and the command 'get 
+                            /dd/sys/password' is received, the pathname 
+                            /H1/USR/SPOOL/FILES/dd/sys/password will be 
+                            used.  
+
+          quit            - Tells FileServ not to process any further lines 
+                            in the message body.  Any commands after 'quit' 
+                            are ignored.  
+
+          submit <file>   - Tells FileServ that the lines following this 
+                            command are a file submission to the 
+                            fileserver.  These files are placed in the 
+                            directory defined by the 'incoming' parameter.  
+                            If the file is uuencoded, it will be uudecoded 
+                            afterwards.  The file remains in the incoming 
+                            directory until the system administrator 
+                            reviews it.  The system administrator is sent 
+                            mail informing him/her of the file arrival.  If 
+                            the 'incoming' parameter is missing, set to 
+                            'no' or 'off', the file submission tossed in 
+                            the bit bucket.  The sender is sent a message 
+                            informing them that file submissions are not 
+                            being accepted.  
+
+                            This feature is not yet fully implemented.  
+                            FileServ currently ignores file submissions, 
+                            though it does inform the system adminstrator 
+                            of the attempt.  It also informs the sender 
+                            submissions are not currently accepted.  
+
+
+
+          FileServ has security feature which will not allow pathnames with 
+          '../' or '@' characters.  This prevents someone from trying to 
+          "sneak" around by backing up one or more levels.  Not allowing 
+          '@' prevents someone from opening the disk as a raw device, i.e.  
+          /h0@. Any pathname starting with a '/' is assumed to be a 
+          subdirectory within the allowed files directory.  All other names 
+          are assume to be in the root of the allowed files directory 
+
+
+
+
+                                                                           
+
+
+
+
+     FILESERV                         UUCP                         FILESERV
+
+
+          If FileServ gets a questionable file transfer request or it 
+          simply can't find the file or directory, it sends the requester a 
+          "can't find <file/directory>" message.  It also sends a warning 
+          message to the 'errorsto' user defined in 
+          /DD/SYS/UUCP/Parameters.  
+
+          All current FileServ activities are kept in the /DD/LOG directory 
+          under the name 'fileserv'. UUCLEAN rotates the fileserver's log 
+          files every time it is run.  It is a good practice to have CRON, 
+          MCRON or some other task scheduler run UUCLEAN once a day so 
+          these log files don't grow excessively large.  
+
+     BUGS   
+
+          When uuencoding files, FileServ doesn't check for file size.  If 
+          the requested file is 300K, FileServ will cheerfully uuencode and 
+          send it.  Many UUCP sites will not accept mail larger than 100K. 
+          If a uuencoded file is greater than 100K, it will most likely 
+          bounce.  For now, FileServ should not be used with large files.  
+          This problem will be fixed in a future update.  
+
+
+     FILES   
+
+          /DD/SYS/UUCP/Parameters
+          /DD/SYS/UUCP/FileServ.help
+          /DD/SYS/UUCP/bin.list
+          /DD/USR/SPOOL/PUB     (suggested directory. set by 'fileserver')
+          /DD/LOG/fileserv
+          /DD/LOG/fileserv.1
+          /DD/LOG/fileserv.2
+          /DD/LOG/fileserv.3
+          /DD/LOG/fileserv.4
+          /DD/LOG/fileserv.5
+          /DD/LOG/fileserv.6
+          /DD/LOG/fileserv.7
+
+
+
+
+                                     THANKS
+
+     The original FileServ program was written by Rick Adams. Rick 
+     contributed it to be included in the UUCPbb package.  (Thanks Rick!!!) 
+     Improvements were made by Bob Billson <bob@kc2wz.bubble.org> for use 
+     with UUCPbb.  
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/fixtext.man	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,66 @@
+
+
+     FIXTEXT                          UUCP                          FIXTEXT
+
+
+     PROGRAM   
+
+          fixtext
+
+     CALLING SEQUENCE 
+
+          fixtext                   -read standard in, write to standard out
+          fixtext infile            -read infile, write to standard out
+          fixtext - outfile         -read standard in, write to outfile
+          fixtext infile outfile    -read infile, write to outfile
+          fixtext -?                -give help
+          
+
+     SUMMARY   
+
+          Fix a text file so it has OS-9 tabbing and end of line 
+          terminators.  
+
+     DESCRIPTION   
+
+          FIXTEXT is a filter which expands tab characters, removes ESCAPE 
+          sequences and changes linefeeds to carriage returns.  It is 
+          useful on files received from UNIX systems where the end of line 
+          character is a linefeed rather than OS-9 carriage return.  OS-9 
+          on the CoCo can't deal tab characters or escape sequences so 
+          these need to be filtered.  
+
+          Examples of using FIXTEXT: 
+
+               fixtext <foo >bar 
+
+          FIXTEXT reads the standard input which is redirected from the 
+          file 'foo'.  It writes the changed file to the standard output 
+          which is redirected to the file bar.  
+
+               fixtext foo !  mailx him@his.system.org -dps "your file" 
+
+          FIXTEXT gets its input from the file 'foo' and pipes the output 
+          to Mailx for mailing to someone.  
+
+               list bar !  fixtext - foo 
+
+          The '-' in command line tells FIXTEXT to read in the standard 
+          input.  It reads the output of LIST which is piped to FIXTEXT. 
+          The output of FIXTEXT is put in the the file 'foo'. If 'foo' 
+          already exists, it will be silently overwritten.  
+
+               fixtext foobar barfoo 
+
+          FIXTEXT gets it input from the file 'foobar' and writes it output 
+          to the file 'barfoo'. If 'barfoo' already exists, it will be 
+          silently overwritten.  
+
+
+
+
+
+
+                                                                           
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/login.man	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,132 @@
+
+
+     LOGIN                            UUCP                            LOGIN
+
+
+     PROGRAM   
+
+          login
+
+     CALLING SEQUENCE 
+
+          login
+
+     SUMMARY   
+
+          Allow a user to log on to the system.  
+
+     DESCRIPTION   
+
+          LOGIN is a program to allow users to log on to OS-9/6809 systems 
+          such as the CoCo. Normally, LOGIN is forked by a program such as 
+          TSMON. This version of LOGIN is not required in order to run UUCP 
+          on the CoCo.  
+
+          When LOGIN runs, it sends the user its login prompt, 'login: '.  
+          The user responds by entering their username and a carriage 
+          return.  LOGIN checks the password file to see if username is 
+          valid.  If it isn't LOGIN, repeats the 'login: ' prompt.  The 
+          user only gets 3 chances to get it right.  After the third 
+          mistake, LOGIN exits.  
+
+          If the username matches an entry in the password file, LOGIN 
+          checks to see if a password is required.  If one is, LOGIN sends 
+          its 'Password: ' prompt.  For security, the user's password is 
+          not echoed back to them.  If the user makes a mistake entering 
+          the password, LOGIN will make them start again at the 'login: ' 
+          prompt.  
+
+          The user has 10 seconds to finish typing their response and hit 
+          <ENTER> at either of the two prompts.  Each time the user sends a 
+          character, the timer is reset.  If LOGIN times out, it logs the 
+          error to the /DD/LOG/login.errors file and exits.  
+
+          If the username and password match, LOGIN checks the 
+          /DD/LOG/login.aliases file to see if there this is an alias for 
+          another username.  If the file does not exist, LOGIN continues 
+          on.  If the file exists, LOGIN expects it to contain one or more 
+          entries, one to a line, with the format: 
+
+               alias newlogname 
+
+          If the username matches the 'alias' name, LOGIN logs the user in 
+          under the corresponding 'newlogname' during this session.  If no 
+          match is found, LOGIN uses the original username.  Any lines 
+          beginning with a '#', <SPACE>, <TAB> or carriage return character 
+          are considered comment lines and ignored.  
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     LOGIN                            UUCP                            LOGIN
+
+
+          Next, LOGIN checks for the existence of the file 
+          /DD/LOG/login.times. If it does not exist, LOGIN continues on.  
+          If the file exists, LOGIN expects it to contain one or more 
+          entries, one to a line, with the format: 
+
+               login_name start_time end_time 
+
+          start_time and end_time are in 24-hour time format.  For example, 
+          0930 is 9:30 a.m., 2015 is 8:20 p.m.  
+
+          LOGIN tries to match the username with a corresponding login_name 
+          entry.  If one is found, LOGIN checks to see if the user is 
+          within the range of allowed times.  If not, LOGIN tells the user, 
+          logs the error and exits.  If the time is acceptable, the user is 
+          allowed to continue.  
+
+          Alternatively, if the end_time field is missing and the 
+          start_time field contains the word "never", the attempt to log in 
+          is always rejected.  
+
+          If there is no entry for that particular username, LOGIN assumes 
+          the user is allowed in at any time.  
+
+          If LOGIN gets this far successfully, it chains to the command(s) 
+          given as the last field in the user's password file entry.  
+
+     NOTES   
+
+          This version of LOGIN is only for use with OS-9/6809 systems.  It 
+          is not currently supported for OS-9/68K.  
+
+     FILES   
+
+          /DD/SYS/password
+          /DD/LOG/login.errors
+          /DD/LOG/login.aliases
+          /DD/LOG/login.times
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/mailrc.doc	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,132 @@
+
+
+     mailrc                           UUCP                           mailrc
+
+
+     FILE   
+
+           ./<homedir>/<user>/UUCP/mailrc  (CoCo)
+           ./<homedir>/<user>/.mailrc      (OSK)
+
+     SUMMARY   
+
+          This file contains user settings for Mailx and news.  
+
+     DESCRIPTION   
+
+          Each entry in this file is on a separate line and follows the 
+          syntax.  --NOTE--: There must be at least one space on both sides 
+          of the '=': 
+
+               parameter = value 
+
+
+          The case (upper or lower) of the parameter is ignored.  Lines 
+          beginning with '#' <space>, <tab>, or a carriage return are 
+          comment lines and ignored.  The parameters which the user can set 
+          are: 
+
+          realname     - The user's real name, to be included in message 
+                         and news article headers.  If the name is more 
+                         than one word, it MUST be surrounded by double 
+                         quotes as shown in the example below.  
+
+          editor       - This specifies the editor invoked by the tilde 
+                         command ~e when composing message or news 
+                         article.  Specify only the name if command will be 
+                         in the current execution directory.  Otherwise, 
+                         specify a full path.  This value will override the 
+                         environment variable EDITOR. There is no default 
+                         value; 
+
+          auto_rot     - Specify on (or yes), or off (or no).  The default 
+                         value is off (no). If on (yes) is set, news 
+                         articles with the keyword rot13 will be 
+                         automatically unrot13'd when read.  
+
+          cc_prompt    - Specify on (or yes), or off (or no).  The default 
+                         is off (no). If on (yes) is set, the user will be 
+                         prompted "Cc: " to send a carbon copy of each 
+                         message to one or more addresses.  
+
+          organization - When sending news articles, this line specifies 
+                         the Organization: field in the article header.  If 
+                         the name of the organization is longer than one 
+                         word, it MUST be enclosed in double quotes.  An 
+                         organization specified in the system-wide 
+                         /DD/SYS/UUCP/Parameters file will override this 
+                         setting.  
+
+
+
+
+
+                                                                           
+
+
+
+
+     mailrc                           UUCP                           mailrc
+
+
+          quote        - This is the default quote character which will be 
+                         appended to the beginning of each line by Mailx or 
+                         POSTNEWS when the tilde command ~m is used.  Only 
+                         a single character not a string of characters is 
+                         acceptable.  
+
+          fullheader   - Mailx allows a user to default to displaying the 
+                         full message header when reading mail or an 
+                         abbreviated one.  If this parameter is missing or 
+                         is present and set to 'yes' or 'on', the full 
+                         header is displayed.  If it is present and set to 
+                         'off' or 'no', the shortned header is displayed.  
+
+
+
+          EXAMPLE:
+
+               realname = "The OTHER Rick Adams"
+               editor = ved
+               auto_rot = on
+               cc_prompt = on
+               organization = "Color Central"
+               quote = -
+               fullheader = no
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/mailx.man	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,858 @@
+
+
+     MAILX                            UUCP                            MAILX
+
+
+     PROGRAM   
+
+          mailx
+
+     CALLING SEQUENCE: 
+
+          mailx [-r]                                        ...read mail
+               opt:  r                - read mail in reverse order
+          
+          mailx [opts] [address <address...>] [opts]        ...send mail
+               opts: a <file>         - file replying to
+                     s "subject"      - Subject: "subject"
+                     x N              - N = debug level
+                     d                - don't add signature
+                     n                - use alt_signature
+                     p                - don't prompt for carbon copy (cc:)
+                     ?                - this message
+                     v                - toggle file viewer...default is OFF
+                     c [<user>...]    - check for waiting mail and that 'user'
+          
+          On the CoCo only using Shell+, non-superusers need to use '*'
+          instead of '@' in command line addresses.
+
+     SUMMARY:  
+
+          Send and receive electronic mail
+
+     DESCRIPTION:   
+
+                                  SENDING MAIL
+
+          Mail may be sent one of two ways, either entering it directly on 
+          the keyboard, or the input can be redirected from a file.  The 
+          recipient may be on this this system, on one or more remote UUCP 
+          nodes, or both.  The commands will be discussed in general first 
+          and in more detail later.  
+
+          To send mail with input coming from keyboard, the general command 
+          is: 
+               mailx [opts] <uucp_address> 
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     MAILX                            UUCP                            MAILX
+
+
+          To send a file, the command is: 
+
+               mailx [opts] <uucp_address> < filename 
+
+          or 
+
+               echo test message !  mailx [opts] <uucp_address> 
+
+          where 'filename' is the pathname of the desired file, 'opts' are 
+          one or more optional command line arguments, and 'uucp_address' 
+          is a user name or address which can take any of the forms 
+          described next.  The last example shows piping text to mailx.  
+
+          The address on a command line can take different three different 
+          forms, for example: 
+
+               mailx rick 
+
+          Sends mail to 'rick'. 'rick' may be either an alias (see 
+          ALIASES.DOC) or the name of a user on the local system.  
+
+               mailx "apple!fico!central!rickadams" 
+
+          Sends mail to the user "rickadams" using the "bang" (!) path 
+          given.  --NOTE--: On the CoCo, the double quotes are necessary to 
+          prevent Shell from trying to interpret the bang as a pipe 
+          character.  Under OSK, a different means of quoting the '!' may 
+          be needed.  Some shells use a backslash () to quote a character, 
+          e.g.  mailx apple!fico!ccentral!rickadams.  Check in the docs for 
+          the shell you are using under OSK.  
+
+               mailx user@node     -- or --     mailx user*node
+
+          The first address is given is a domain address.  The second form 
+          is NOT a valid domain address.  However, for CoCos using Shell+ 
+          v2.1, the second form is necessary for any user who is NOT the 
+          superuser.  A security feature in Shell+ strips the "@" from any 
+          command line arguments of non-superusers before they are 
+          processed.  To get around the problem, Mailx will treat a '*' 
+          internally the same as as the "@". There is a patch included in 
+          the original Shell+ archive which lets you turn off the "@" 
+          check.  If you have turned it off all users can use the properly 
+          first form.  The second address form should not be needed under 
+          OSK. This depends on how the OSK shell treats the '@' character.  
+
+               mailx @filename      -- or --     mailx *filename
+
+          This form tells mailx to look in the directory UUCP in the user's 
+          home directory for a file called 'filename'. The contents of the 
+          file will be interpreted as a mailing list.  Mailx assumes the 
+          file is a list of user names, aliaes or UUCP addresses, one per 
+          line.  The message will be sent to each address.  As mentioned 
+          above, the "*" form is for non-superusers using Shell+ on the 
+          CoCo.  
+
+
+
+
+                                                                           
+
+
+
+
+     MAILX                            UUCP                            MAILX
+
+
+          Mailx is also smart enough to understand the Internet '%'. For 
+          example: 
+
+               mailx joe%sandstorm.uucp@gigsys 
+
+          This will send mail to user 'joe' at sandstorm.  The message will 
+          be routed via gigsys.  In order for this to work properly, users 
+          of Shell+ v2.1 must turn off the shell variable expansion.  This 
+          is done by: 
+
+               OS9> -v 
+
+          Or it can be done in the user's password entry file as in this 
+          example: 
+
+               bob,000000,0,128,/dd/cmds,/dd/usr/bob,ex shell -v 
+
+          If the shell variable expansion is not turned off, Shell+ will 
+          try to interpret the '%' as a shell variable and remove it from 
+          uucp_address.  
+
+          There is a special case local user name 'daemon'. The UUSETUP 
+          program creates an entry for this user ID in the password file.  
+          Any mail sent from this user ID will have a special header with a 
+          'Reply-To: postmaster@<this_system>' address.  There is also a 
+          special user name 'nobody' recognized by RMAIL. Mail sent to user 
+          'nobody' will be sent to RMAIL's bit bucket.  
+
+          Next, Mailx tries to open the file 'aliases' ('.aliases' under 
+          OSK). If the file exists, Mailx attempts match each uucp_address 
+          with an alias address.  If a match is found, uucp_address is 
+          replaced with the appropriate address.  (See ALIASES.DOC for more 
+          details on the aliases file.) Thus you can send mail to: 
+
+               mailx fred barney mary 
+
+          where 'fred', 'barney' and 'mary' are aliases for longer uucp 
+          paths.  If no matching alias is found or the aliases file cannot 
+          be read, the addresses remain unchanged.  In the example above, 
+          Mailx would assume these are names of users on the system.  
+
+          Mail aliases, uucp addresses and mailing lists may be mixed 
+          freely on the command line.  This lets you send a single message 
+          to mutilple recipients.  For example: 
+
+               mailx fred "wingding!evil!purple!barney" @mail.list 
+
+          When mail is sent from the keyboard, you will be prompted for a 
+          "Subject:" line.  If no "Subject:" line is desired, hit ENTER to 
+          skip this line.  
+
+          Mailx reads the files /DD/SYS/UUCP/parameters and mailrc (.mailrc 
+          under OSK) file in your home directory to get the default 
+          parameters.  (See PARAMETERS.DOC, PARAMETERS.EXAMPLE and 
+
+
+
+
+                                                                           
+
+
+
+
+     MAILX                            UUCP                            MAILX
+
+
+          MAILRC.DOC for information on the format of these files.)  If 
+          'mailrc' is set to prompt for carbon copy (Cc:), Mailx will show 
+          the line 'Cc:'. One or more names, uucp_addresses, or aliases 
+          separated by a space can be entered.  A copy of the message will 
+          be sent to each address as well as those given on the command 
+          line.  If you don't desire to send a copy of the message, just 
+          hit ENTER.  
+
+          Mailx will now allow you to compose your message.  
+
+          First, a bit of advice.  UUCP is text based system.  Because are 
+          there are many different types of terminals which are used to 
+          read UUCP mail on, it is poor practice to include graphics or 
+          control characters or binary files in the message text and 
+          certainly NEVER in the message headers.  Graphics and control 
+          characters may do nice, fancy things on your terminal; however, 
+          the things they do to the receiver's terminal may not be so nice 
+          or fancy.  At the very least, you may make your mail unreadable 
+          at the receiving end.  Binary files can be included in mail after 
+          running them through a binary to text encoding program such as 
+          UUENCODE or CUTS. UUENCODE is a standard UUCP encoding utility.  
+          CUTS was written for the CoCo and unlikely to be found on other 
+          UUCP systems.  
+
+          Secondly, it is good practice to limit line lengths to less than 
+          80 characters.  Each line should end of a carriage return.  You 
+          can not assume that the receiver's terminal will properly handle 
+          excessively long lines.  Your nicely formatted text may end be 
+          hard or impossible to decipher on the receiver's terminal.  
+
+
+
+                                   COMPOSING MAIL
+
+          Initially, you are in OS-9's single line editor.  You can enter 
+          and change text as long as you do not hit the ENTER key.  While 
+          you are typing an outgoing message, there are various commands to 
+          assist you in composing the message.  Each of these commands 
+          starts with a tilde (~) character at the beginning of the line.  
+          After each command is finished, with the exception of ~a and ~x, 
+          you will be returned to OS-9's single line editor.  
+
+
+          ~v                  Edit message using "vi". "vi" refers to the 
+                              Tandy TSEDIT editor after the "vi" patches 
+                              have been applied to enable this editor to 
+                              work in OS9 device windows.  
+
+          ~e                  Edit message using the editor defined in 
+                              either by the environment variable EDITOR or 
+                              the file mailrc (.mailrc under OSK) in your 
+                              home directory.  The editor named in 'mailrc' 
+                              overrides the one defined by EDITOR.  
+
+
+
+
+
+                                                                           
+
+
+
+
+     MAILX                            UUCP                            MAILX
+
+
+          ~m[<char>]          Include text of letter being replied to.  An 
+                              optional character <char> will be put at the 
+                              beginning of each line.  The default 
+                              character is ">". This can be changed in 
+                              either 'parameters' or 'mailrc' files.  If a 
+                              space is used as the character, no quote will 
+                              mark the included text.  Examples: 
+
+                                   ~m<SPACE>    This is included message
+                                   ~m<ENTER>    >This is included message
+                                   ~m-          -This is included message
+
+          ~h                  Display help message.  
+
+          ~x                  Exit Mailx immediately, abandoning letter.  
+
+          ~r[<char>] <file>   Include text from file <file>. If an optional 
+                              character <char> follows '~r', each line of 
+                              the included text will be started with it.  
+                              Mailx assumes <filename> is in your current 
+                              data directory unless a full pathname is 
+                              given.  Examples: 
+
+                                    ~r <file>   This is included file.
+                                    ~r$ <file>  $This is included file.
+
+                              There is no default quote character for this 
+                              command.  
+
+                              Before appending the file, the file name is 
+                              checked for an ending extention, e.g.  .ar, 
+                              .lzh, etc.  If such an extention is found, 
+                              Mailx attempts to compared against the names 
+                              in the file /DD/SYS/UUCP/bin.list, if it 
+                              exists.  This file consists of a list of 
+                              names, one to a line, representing names of 
+                              binary files.  Common names would be: ar, 
+                              gif, pak, lzh, bin, z, vef, and gif.  
+                              --NOTE--: The dot (.) is NOT part of the name 
+                              in bin.list.)  If a match is found, Mailx 
+                              assumes the file is a binary one and 
+                              uuencodes it before appending it.  If the 
+                              file is uuencoded, the quote char is not 
+                              used.  If there is no match or bin.list 
+                              doesn't exist, Mailx proceeds as described 
+                              above.  
+
+          ~R[<char>] <file>   Works the same as ~r above except no attempt 
+                              is made to uuencode the file.  
+
+
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     MAILX                            UUCP                            MAILX
+
+
+          ~a                  Abort editing the current letter.  You will 
+                              be asked if you want to abort.  Only a 'y' or 
+                              'Y' will abort the letter.  If you were 
+                              replying to a message, you will be returned 
+                              to that message.  Otherwise Mailx will exit.  
+
+          ~!                  Forks a shell.  CNTRL-<BREAK) will kill the 
+                              shell and you can resume composing the 
+                              letter.  
+
+          ~u <file>           Uuencode <file> and append it to the letter.  
+
+
+
+          When editing a message, DO NOT attempt to do any of the 
+          following; the results are unpredictable: 
+
+              o   Change the message header To: or CC: lines.  The changes 
+                  will not be used when the mail is sent.  You can change 
+                  the Subject: line, however.  
+
+              o   Remove the blank line following the message header.  
+                  Mailers on remote systems expect this blank line to be 
+                  there and start with an End-Of-Line character 
+
+          When you are finished composing the letter, you send it by 
+          entering a period (.) followed by <ENTER>. The period must be the 
+          first and only character on the line.  
+
+          Mailx will then try to open and read either the file signature or 
+          alt_signature, if the command line optin '-n' was used, in your 
+          home directory.  The latter is discussed below.  If it exists, 
+          the contents will be appended to the letter.  (See SIGNATURE.DOC) 
+
+          If the mail cannot be sent to user, an error message will be 
+          shown.  The message will be saved in the file dead.letter in the 
+          user's home directory.  If dead.letter already exists, the 
+          message will be appended to the file.  This feature will prevent 
+          needing to retype a long message because of some addressing 
+          error.  
+
+
+
+                                COMMAND LINE OPTIONS
+
+          Various command line options can be used for sending mail.  They 
+          can be mixed in any order with addresses.  Each option must be 
+          preceded by a '-'. Options may be run together, for example: 
+
+               mailx -dps test bob@kc2wz.bubble.org 
+               mailx oracle@cs.indiana.edu -s "Oracle tell me ..." -p -d 
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     MAILX                            UUCP                            MAILX
+
+
+          Available options are: 
+
+
+          a <file>       file replying to.  This is used by POSTNEWS when 
+                         posting a followup to a news article.  
+
+          s <subject>    Subject: line.  If included on the command, you 
+                         will not be prompted for it later.  If the subject 
+                         consists of more than one word, they must be 
+                         enclosed in double quotes.  Example: 
+
+                              mailx -s test harvey 
+
+                         Sends a mesage to 'harvey' with: 
+                              Subject: test 
+
+                              mailx -s "This is a test" harvey 
+
+                         Sends a message to 'harvey' with: 
+                              Subject: This is a test 
+
+
+          xN             N equals the debug level from 0 (OFF) to 9 
+                         (highest). The default is OFF (0).  
+
+          d              Tells Mailx not to add your signature file to your 
+                         letter.  This is useful for sending mail to an 
+                         automatic mail servers where unexpected text can 
+                         cause unexpected results.  The default for this 
+                         option is OFF. This means Mailx will read the 
+                         contents of the signature (.signature under OSK), 
+                         if it exists in your home directory, and append 
+                         its contents to your message.  
+
+          n              Look for the file alt_signature (.alt_signature 
+                         under OSK) in your home directory.  If it can be 
+                         read, its contents will be appended to your 
+                         message instead of the default 'signature' 
+                         ('.signature' under OSK).  
+
+          p              Do not to prompt for carbon copy (Cc:).  This will 
+                         override the setting in the 'mailrc' file.  It is 
+                         useful for sending mail as in this example: 
+
+                              echo "Time to backup" !  mailx -p paul 
+
+                         The -p is necessary here.  Otherwise, if this 
+                         command was run by a system daemon such as CRON 
+                         and the 'mailrc' or the /DD/SYS/UUCP/Parameters 
+                         file was set to prompt for 'Cc:', Mailx would wait 
+                         for a response to the "Cc:" prompt which it would 
+                         never see.  The result look like the Mailx had 
+                         crashed.  
+
+
+
+
+
+                                                                           
+
+
+
+
+     MAILX                            UUCP                            MAILX
+
+
+                                 RECEIVING MAIL
+
+          This section deals with reading mail received from other users or 
+          remote UUCP systems.  Mail is read in the order it arrives.  
+          Messages can read either starting with the oldest to the most 
+          recent (first in, first out) order, starting with the most 
+          recently to the oldest (last in, first out) order.  Mailx 
+          defaults to first in, first out order.  
+
+          The two commands to read mail are: 
+
+               mailx 
+               mailx -r 
+
+          When mail begins you will be told the total number of messages 
+          waiting, how many are new (received since the last session), and 
+          how many are unread (new from a previous session but never 
+          read).  
+
+          If the message displayed is longer than the screen, the message 
+          will stop scrolling and a "MORE" prompt will be displayed until 
+          you hit one of the following keys: 
+
+          x              Mailx will exit immediately with no changes.  
+
+          q              This will display Mailx's command prompt: 
+
+                              mailx> 
+
+                         At this prompt you can use any of the commands 
+                         described in detail in the next section.  
+
+          a              This will redisplay the current message starting 
+                         from the beginning.  
+
+          n              This will stop showing the current message and go 
+                         to the next waiting message.  If the current 
+                         messsage is the last one, Mailx will ask if you 
+                         want to quit.  The current message remains 
+                         unchanged in either case.  
+
+          p, -           This will stop showing the current message and go 
+                         to the previous message.  If there is no previous 
+                         message, the current message is redisplayed from 
+                         the beginning.  
+
+
+          BREAK          Mailx will exit immediately with no changes to any 
+                         messages.  
+
+
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     MAILX                            UUCP                            MAILX
+
+
+          SPACE 
+          ENTER          Continue scrolling the current message.  
+
+
+          At the end of the message, Mailx's command prompt, "mailx>", will 
+          appear.  At this point, you may dispose of the mail in a number 
+          of ways: 
+
+          s [<filename>]      Saves the message to a file.  <filename> is 
+                              optional.  If none is give, the message is 
+                              saved in a file called 'mbox' in the user's 
+                              home directory.  If 'mbox' already exists, 
+                              the message is appended to the file.  If 
+                              <filename) is given, message will be saved 
+                              that in file.  Mailx puts <filename> in the 
+                              user's home directory unless a full pathname 
+                              to somewhere else is used.  An error message 
+                              is shown if Mailx is unable to save the 
+                              file.  
+
+                              You will then be given the option to delete 
+                              the message.  Any answer but yes keeps the 
+                              message.  
+
+          w [<filename>]      Saves the message to a file as does 's' 
+                              above.  However, the header is stripped 
+                              first.  Mailx begins with line following the 
+                              first blank line in the message.  A blank 
+                              line is a line beginning with a carriage 
+                              return or linefeed.  
+
+          n                   Go to the next message.  The current 
+          <SPACE>             message is unchanged.  If the current 
+          <ENTER>             message is the last one, Mailx exits.  
+
+          p, -                Go to the previous message.  If the current 
+                              message is the first one, it is redisplayed 
+                              from the beginning.  
+
+          a                   Shows the current message again starting from 
+                              the beginning.  
+
+          r                   Reply to the message being read.  You will 
+                              able to compose using the commands described 
+                              in COMPOSING MAIL above.  After the reply is 
+                              sent, you will be return to the command 
+                              prompt.  The current message will be 
+                              unchanged.  
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     MAILX                            UUCP                            MAILX
+
+
+          f                   Forward a copy of the current message to one 
+                              or more addresses.  You will be prompted for 
+                              "forward To:". Enter one or more names, uucp 
+                              addresses, or aliases with a space separating 
+                              each one.  If you decide not to forward the 
+                              message, hit ENTER in response to "forward 
+                              To:". If you have already typed addresses but 
+                              not yet hit ENTER, simply backspace as far as 
+                              possible and hit ENTER. In both cases, you 
+                              will be returned to the command prompt.  
+
+                              Next, you will be prompted for "Subject:". 
+                              You can enter it or hit ENTER in which case 
+                              the default "Subject:" will be "Forwarded 
+                              Mail".  
+
+                              A copy of the current message will be 
+                              attached and you will end up in Mailx's 
+                              single line editor.  You may either edit the 
+                              message (See COMPOSING MAIL) or send it 
+                              immediately.  The signature file is NOT 
+                              appended to a forwarded message.  
+
+
+          m <address>         Send mail to one or more UUCP addresses.  
+                              Separate each address with a space.  End 
+                              addresses with ENTER. If you decide not to 
+                              mail, hit ENTER instead of entering 
+                              addresses.  You will be returned to the 
+                              command prompt.  
+
+                              This command is essentially the same as using 
+                              'mailx <address>' on the command line with 
+                              two differences: 
+
+                                   1. The current message being read is 
+                                      available to include in the letter.  
+
+                                   2. Non-superusers can use '@' instead of 
+                                      '*' since the shell is not being used 
+                                      inside Mailx. (Only Shell+ users on 
+                                      the CoCo need to be concerned with 
+                                      this.) 
+
+                              You can also use the command line options, 
+                              -s, -d and -p. These are only in effect to 
+                              the duration of the 'm' command.  
+
+                              After the mail is sent, you will be returned 
+                              to the command prompt.  The current message 
+                              will be unchanged.  
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     MAILX                            UUCP                            MAILX
+
+
+          d                   Delete the current message.  You will be 
+                              asked for confirmation.  Any answer but 'Y' 
+                              or 'y' will leave the message unchanged.  
+
+                              If you answer 'Y', the current message will 
+                              be deleted and the next one displayed.  If 
+                              this was the last message, Mailx will ask if 
+                              you which to exit.  
+
+          u                   Undelete mail deleted during this session.  
+
+
+          h, ?                Displays a help screen of commands 
+                              available.  
+
+          q                   Exit Mailx after killing deleted mail.  
+
+          x                   Exits immediately leaving everything 
+                              unchanged.  
+
+          !                   Forks a shell.  CNTRL-BREAK will kill the 
+                              shell and return to the command prompt of the 
+                              current message.  
+
+
+          Example of reading mail in first in, last out order (default): 
+
+               OS9> mailx
+               From moon!johnharkin May 27 21:36:17 1991
+               Received: by ccentral (OS9 UUCP); 27 May 91 21:36:17
+               Date: Mon, 27 May 91 21:34:46
+               From: John Harkin <johnharkin@moon.UUCP>
+               Subject: Upcoming publication schedule
+               Reply-To: "John Harkin" <johnharkin@moon.UUCP>
+               To: ccentral!rickadams
+               Message-Id: <9105272134.AA00112@moon.UUCP>
+               
+               I'll have the necessary article text to you by the 29th; I hope
+               you can get the promotional brochure done quickly.
+               -- 
+               John Harkin     North Bay Network       moon!johnharkin
+               
+               mailx> q
+               
+               OS9>
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     MAILX                            UUCP                            MAILX
+
+
+                                    CHECKING MAIL
+
+          Mailx let's you check your mailbox to see if there is waiting 
+          mail.  The command syntax is: 
+
+               mailx -c [<user>...] 
+
+          Only the superuser is allowed to check for waiting mail of other 
+          users.  If a non-superuser attempts this, only their mailbox is 
+          checked.  You will be told if there is waiting mail and how many 
+          messages.  When the superuser checks another user's mail, the 
+          superuser's mailbox is also checked.  Some examples: 
+
+          User 'bob', who is not the superuser, is checking his mail:
+
+          OS9> mailx -c
+          You have mail <3 messages> ...type 'mailx' to read it
+          
+          OS9>
+
+          Superuser 'sue' is checking her mail and that of 'postmaster' and 
+          'fred': 
+
+          OS9> mailx -c postmaster fred
+          You have mail <1 message> ...type 'mailx' to read it
+          
+          postmaster: You have mail <2 messges> ...type 'mailx' to read it
+          fred: no mail
+          
+          OS9>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     MAILX                            UUCP                            MAILX
+
+
+     FILES   
+
+          Use of $HOME and $MAIL below indicate directories defined by 
+          environment variables.  For CoCo and OSK, the global environment 
+          variables MAIL and HOME must be defined, e.g.: 
+
+                 MAIL=/h1/usr/spool/mail
+                 HOME=/dd/home
+
+
+          In user's home directory:
+
+               (CoCo specific files)
+              $HOME/<user>/UUCP/aliases
+              $HOME/<user>/UUCP/mailrc
+              $HOME/<user>/UUCP/signature
+              $HOME/<user>/UUCP/alt_signature
+              $HOME/<user>/UUCP/<mailing_list>
+              $HOME/<user>/profile
+             
+               (OSK specific files)
+              $HOME/<user>/.aliases
+              $HOME/<user>/.mailrc
+              $HOME/<user>/.signature
+              $HOME/<user>/.alt_signature
+              $HOME/<user>/<mailing_list>
+
+          Other files: 
+              $HOME/<user>/dead.letter
+              $HOME/<user>/mbox
+              $MAIL/<user>/mail..list
+              $MAIL/<user>/mYYYYMMDDHHMMSS        (message file)
+              /DD/SYS/UUCP/Parameters
+              /DD/SYS/UUCP/sequence.mail
+              /DD/SYS/UUCP/sequence.spool
+              /DD/SYS/profile                (CoCo--global system environment)
+              ./<scratchdir>/UUCPtemp1.?            (temporary file)
+
+     SEE ALSO 
+
+          parameters.doc, aliases.doc, mailrc.doc, signature.doc,
+          rmail.man, parameters.example
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/parameters.doc	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,528 @@
+
+
+     Parmeters                        UUCP                       Parameters
+
+
+     FILE   
+
+          /DD/SYS/UUCP/Parameters
+
+     SUMMARY:   
+
+          This file contains the global system settings for all UUCP 
+          executables.  
+
+     DESCRIPTION:   
+
+          Each entry in this file is on a separate line and follows the 
+          syntax.  --NOTE--: There must be at least one space on each side 
+          of the '=': 
+
+          parameter = value
+
+          The case (upper or lower) of the parameter is ignored.  Empty 
+          lines and lines beginning with '*' or '#' are ignored as comment 
+          lines.  There is no particular order the parameters must be in, 
+          i.e.  'auto_rot' can be before or after 'quote' 
+
+          --NOTE-- If the same parameter is given more than once in the 
+          Parameters file, only the value of the last entry will be used.  
+
+          If a parameter is missing, it assumes a default value unless 
+          otherwise noted.  The parameters are: 
+
+          auto_rot     - Specify on (or yes), or off (or no).  The default 
+                         value is OFF (no). If on (yes) is set, news 
+                         articles with the keyword rot13 will be 
+                         automatically rot13'd when read.  Default is OFF.  
+
+          cc_prompt    - Specify on (or yes), or off (or no).  The default 
+                         is off (no). If on (yes) is set, the user will be 
+                         prompted "Cc: " to send a carbon copy of each mail 
+                         message they send.  Default is OFF 
+
+          quote        - This is the default quote character which will 
+                         start each line when the tilde command "~m" is 
+                         used in MAIL and POSTNEWS. It will be overriden by 
+                         users' settings in their mailrc files.  Default is 
+                         '>' 
+
+          organization - When sending news articles, this line specifies 
+                         the Organization: field in the article header.  If 
+                         the name of the organization is longer than one 
+                         word, it must be enclosed in double quotes.  An 
+                         organization specified in this file overrides 
+                         users' settings in their mailrc files.  There is 
+                         no default.  
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     Parmeters                        UUCP                       Parameters
+
+
+          tz           - This parameter takes one or two values.  The first 
+                         value is the name of your time zone; the second is 
+                         the name of your timezone during daylight savings 
+                         time.  Use only one value if you never change to 
+                         daylight savings time.  While you can use can use 
+                         time zone names such as EST EDT (Eastern Standard 
+                         Time and Eastern Daylight Time, respectively), the 
+                         suggested names specify your time's offset (in 
+                         military time format) from Universal Time (or 
+                         Greenwich Mean Time).  For example, EST is -0500 
+                         and EDT is -0400. This means that Eastern Standard 
+                         Time is five hours and zero minutes earlier than 
+                         GMT. The American standard for daylight standard 
+                         time is assumed -- from 2 a.m.  of the first 
+                         Sunday in April to 2 a.m.  of the last Sunday in 
+                         October.  There is no default.  
+
+          bigscratch   - This parameter specifies a full path to the 
+                         directory where temporary files will be created 
+                         when receiving compressed batched news.  The 
+                         device containing this directory should have 
+                         enough free space to comfortably hold large files, 
+                         e.g.  two files nearly 64K long.  These files may 
+                         be larger depending on how many newsgroups you 
+                         receive.  RNEWS will first try to use the RAM disk 
+                         for individual articles if it is big enough rather 
+                         than 'bigscratch'. This greatly speeds up 
+                         processing.  The size of the RAM is set by the 
+                         #define RAMDSIZE in uucp.h.  The current value is 
+                         80000 (80K). You can force the RAM disk to never 
+                         be used by setting the size to O. Be sure the 
+                         ending 'L' is on any changed value.  RNEWS assumes 
+                         this space is free when news is processed.  If it 
+                         isn't, you will probably lose articles!  If the 
+                         RAM disk is not big enough or not accessible 
+                         bigscratch will be used.  See 'scratchdir' below 
+                         for additional information.  The default value is 
+                         /DD. This directory can but does not have to be 
+                         either the same device or directory as 'scratch'. 
+                         Default is /DD.  
+
+          scratch      - This parameter specifies a full path to the 
+                         directory where temporary files will be created 
+                         when receiving or sending mail messages.  The 
+                         device containing this directory should have 
+                         enough free space to comfortably hold large 
+                         files.  If you have a RAM drive which is large 
+                         enough and that drive will always be iniz'd (and 
+                         formatted if necessary) when running UUCP 
+                         executables, then that is the recommended choice 
+                         on the CoCo. The default value is /DD; you may 
+                         wish to change this to /DD/TEMP or some other 
+                         device.  Many programs will run noticably faster 
+                         if the device containing the scratch directory is 
+
+
+
+
+                                                                           
+
+
+
+
+     Parmeters                        UUCP                       Parameters
+
+
+                         different from /DD. Default is /DD.  
+
+          errorsto     - This is the name of the user on the system where 
+                         undeliverable mail should be sent.  The default is 
+                         'postmaster'.  
+
+          pager        - This parameter specifies an optional file viewer 
+                         such as MORE or VU which will be used by Mailx or 
+                         READNEWS when reading mail or news.  If this 
+                         parameter is not specified, mail and news will be 
+                         displayed in scrolling form.  There is no 
+                         default.  
+
+          nodename     - This is the *unique* UUCP name of this system.  
+                         The name may consist of one to eight (but not more 
+                         than eight) alphanumeric characters.  Punctuation 
+                         is not allowed as part of the name.  There is no 
+                         default.  Examples: 
+
+                              ccentral
+                              mytoy
+                              kc2wz
+
+          sitename     - This is the domain name of this site.  If your 
+                         system has a fully qualified domain name, it goes 
+                         here.  If it does not, the entry should be your 
+                         nodename with '.UUCP' added to it.  There is no 
+                         default.  Examples: 
+
+                              kc2wz.bubble.org
+                              ccentral.UUCP
+
+          uucphost     - This is a bang-path to the nearest UUCP smart mail 
+                         host.  This will usually (but not always) be your 
+                         UUCP neighbor.  Any mail sent via a UUCP bang-path 
+                         which isn't explicitly sent to one of your UUCP 
+                         neighbors will be sent via this path to the 
+                         destination.  This parameter and the two following 
+                         are further explained below.  There is no 
+                         default.  
+
+          inhost       - This is a bang-path to the nearest Internet smart 
+                         mail host.  Mail which is sent to an 
+                         internet-style address such as user@site.domain 
+                         will be forwarded to this host.  Most UUCP smart 
+                         mailers also understand the Internet address 
+                         format.  There is no default.  
+
+          bithost      - This is a bang-path to the nearest BITNet host.  
+                         If this is left blank, mail will be routed to the 
+                         Internet smart mail host after ".bitnet" has been 
+                         appended to the address.  Mail is assumed to be 
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     Parmeters                        UUCP                       Parameters
+
+
+                         destined for the BITNet when it is of the form: 
+                         user@site where site does not contain any periods 
+                         (.). There is no default.  
+
+          newshost     - This is name of your default USENET newsfeed 
+                         host.  This is merely the name of the system NOT 
+                         the path to it.  If this parameter is not 
+                         specified, your default news host will be the 
+                         first system found in the /DD/SYS/UUCP/Systems 
+                         file.  There is no default.  
+
+          window       - This parameter specifies the UUCP g protocol 
+                         window size for UUCICO. Possible values are from 1 
+                         to 7. 1 (the default) is suggested unless you are 
+                         using SACIA or DACIA (in which case you can use a 
+                         higher value, 2-7, depending on how large you have 
+                         set the ACIA driver's buffer), or have patched 
+                         Aciapak to have a larger receive buffer (in which 
+                         case you can use 2 or 3). The throughput, 
+                         generally, will not increase with a window size 
+                         greater than 3 on the CoCo. Default is 1.  
+
+          hangup       - This parameter tells how to hang up your modem.  
+                         There are two choices "DTR" (drop the DTR line) or 
+                         "ATH", (send +++ATH). Default is ATH.  
+
+          spooldir     - This is the full path to directory where UUCICO 
+                         looks for queued mail/files to transfer to each 
+                         remote.  Each remote you call has its own 
+                         directory within spooldir.  The suggested 
+                         directory is /DD/USR/SPOOL/UUCP.  There is no 
+                         default.  
+
+          maildir      - This is the full path to directory containing the 
+                         users' mailbox directories.  This parameter is 
+                         only used if the environment variable MAIL is not 
+                         set.  
+
+          newsdir      - This is the full path to directory where Usenet 
+                         news articles are put.  READNEWS and POSTNEWS look 
+                         here for news.  The suggested directory is 
+                         /DD/USR/SPOOL/NEWS. There is no default 
+
+          pubdir       - This is the full path to the directory where 
+                         incoming public files (not mail or news) are put.  
+                         The are files which are transferred by the UUCP 
+                         program itself.  The suggested directory is 
+                         /DD/USR/SPOOL/UUCPPUBLIC. There is no default.  
+
+          server       - This parameter specifies whether the OS-9 
+                         fileserver is active.  Specify on or off, yes or 
+                         no.  If the fileserver is active, any mail sent to 
+                         the user 'fileserv' on this system gets passed 
+                         along to the program FILESERV. If the fileserver 
+
+
+
+
+                                                                           
+
+
+
+
+     Parmeters                        UUCP                       Parameters
+
+
+                         is not active, any mail sent to the local user 
+                         'fileserv' gets a "not available" response.  
+                         Default is OFF.  
+
+          fileserver   - This parameter specifies the full path to the 
+                         directory where files available through the 
+                         fileserver are kept.  The suggested directory is 
+                         /DD/USR/SPOOL/FILES. If this parameter is 
+                         unspecified, the directory doesn't exist or is 
+                         unreadable, the fileserver is not active; any mail 
+                         to user 'fileserv' gets a "not available" 
+                         response.  There is no default.  
+
+          incoming     - This parameter gives the directory where files 
+                         sent to the fileserver are placed for the system 
+                         administrator to review.  If this parameter is set 
+                         to 'no', 'off', missing or the fileserver itself 
+                         is not active, the fileserver will reject attempts 
+                         to submit files.  This feature is not implement 
+                         yet.  All attempts to submit a file are currently 
+                         rejected.  
+
+
+          The parameters 'auto_rot', 'cc_prompt', and 'organization' are 
+          also settable in each user's mailrc (.mailrc under OSK) file.  
+          This file is kept in the user's home directory.  The mailrc 
+          values will override the system-wide settings, except for 
+          'organization'. The /DD/SYS/UUCP/Parameters file 'organization', 
+          if defined, overrides the user's mailrc definition.  Attempts by 
+          users to redefine any other parameters is ignored.  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     Parmeters                        UUCP                       Parameters
+
+
+          In order explain uucphost, inhost, bithost, newshost further, 
+          consider this example network: 
+
+          coco3----------sandstorm-------------gigsys----------papabear
+             \               /  \                  \               /
+              \             /    \                  \             /
+               \           /      \                  \           /
+                \         /        \                  \         /
+                 \       /          \                  \       /
+                 homebase       garage3                 tatooine
+
+          Assume that you are on coco3, gigsys is on the Internet as 
+          gigsys.com, and sandstorm runs a smart UUCP mailer and you get 
+          your news from sandstorm.  In this example, you would use define: 
+
+               uucphost = sandstorm
+               
+               inhost = sandstorm!gigsys
+               
+               bithost = 
+               
+               newshost = sandstorm
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     Parmeters                        UUCP                       Parameters
+
+
+          If, instead, sandstorm and hostbase both ran non-smart-mailers 
+          (mailers which don't use pathalias and are not Internet mailers), 
+          but garage3 ran a smart UUCP mailer, you would change the above 
+          uucphost line to: 
+
+               uucphost = sandstorm!garage3 
+
+          Or if homebase provided your Usenet news feed only, you would 
+          change the above newshost line to: 
+
+               newshost = homebase 
+
+          Remember, you should get permission to route mail through each 
+          machine you explicitly route all of your mail through!  This 
+          includes each machine you specify in any of the three uucphost, 
+          inhost, or bithost.  Generally, your mail UUCP connection will 
+          work as both uucp and Internet host, and you will leave bithost 
+          blank.  
+
+               EXAMPLE:
+               
+               # name of this UUCP site
+               nodename = ccentral
+               
+               # domain name of this site
+               sitename = ccentral.UUCP
+               
+               # timezone, Daylight Savings Timezone
+               tz = -0400 -0300
+               
+               # file viewer
+               pager = vu
+               
+               # hangup by drop DTR
+               hangup = DTR
+               
+               # temporary directory for mail
+               scratch = /r0
+               
+               # temporary directory for news
+               scratchbig = /dd/tmp
+               
+               # undeliverable system mail goes to
+               errorsto = postmaster
+               
+               # bang-path to UUCP smart-host
+               uucphost = sandstorm
+               
+               # bang-path to Internet smart-host
+               inhost = sandstorm!gigsys
+               
+               # bang-path to Bitnet smart-host
+               #(blank means we use an Internet host)
+               bithost = 
+
+
+
+
+                                                                           
+
+
+
+
+     Parmeters                        UUCP                       Parameters
+
+
+               
+               # default news host
+               # blank means first system in Systems file is host
+               newshost = sandstorm
+               
+               # size of g-protocal sending window (1-7)
+               window = 3
+               
+               # organization
+               organization = "Color Central"
+               
+               # mailbox directory
+               maildir = /dd/usr/mail
+               
+               # news directory
+               newsdir = /dd/usr/spool/news
+               
+               # uucico's spool directory
+               spooldir = /dd/usr/spool/uucp
+               
+               # uucp's public directory
+               pubdir = /dd/usr/spool/uucppublic
+               
+               # Is the OS-9 fileserver active?  Response is yes, no, on or off
+               server = on
+               
+               # Directory where files available through the fileserver are kept
+               fileserver = /h1/usr/spool/files
+               
+               # Directory where submit files are put (not implemented yet)
+               incoming = /h0/usr/spool/files/incoming
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/postnews.man	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,330 @@
+
+
+     POSTNEWS                         UUCP                         POSTNEWS
+
+
+     PROGRAM   
+
+          postnews
+
+     CALLING SEQUENCE 
+
+          postnews [options]
+          
+             options: -f <file>
+                      -n <newsgroup>
+                      -S <system>
+                      -s <subject>
+                      -i <reference-ID>
+                      -a <reference-article>
+                      -t (force /t2 "dumb" windowing codes)
+
+     SUMMARY   
+
+          Post a Usenet news article 
+
+     DESCRIPTION   
+
+          This program assists you in composing a Usenet news article, 
+          posts it locally, and also queues it for transmission to your 
+          UUCP neighbor the next time uucico is run.  
+
+          The program prompts you for five fields that go in the header of 
+          the message, and then allows entry of your article.  Type a "." 
+          at the beginning of a line to end your article.  
+
+          If the file ./<homedir>/<user>/UUCP/signature 
+          (./<homedir>/<user>/.signature under OSK) exists, its contents of 
+          that file will be appended to the article before it is posted.  
+
+          If the file ./<homedir>/<user>/UUCP/organization 
+          (./<homedir>/<user>/.organization under OSK) exists, its contents 
+          will be used in the "Organization:" line in the header of the 
+          article.  If no such file exists, the system-wide organization 
+          file in /DD/SYS/UUCP/organization will be used.  If no 
+          organization file exists anywhere, the "Organization:" line will 
+          be omitted.  
+
+          The five fields you will be prompted for are: 
+
+          Newsgroups: 
+              The Usenet newsgroup to which this article should be posted.  
+              To be valid, this newsgroup must be listed in the file 
+              /DD/SYS/UUCP/ACTIVE.  
+
+          Subject: 
+              One-line subject description 
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     POSTNEWS                         UUCP                         POSTNEWS
+
+
+          Keywords: 
+              Optional list of keywords for the article; used by some news 
+              readers to index articles by keywords.  
+
+          Distribution: 
+              Distribution for the article, whether worldwide ("world"), 
+              the United States ("usa"), or some more regional 
+              distribution.  To be valid, the distribution must be listed 
+              in the file /dd/sys/uucp/distributions.  
+
+          Summary: 
+              One-line summary of the article's contents.  
+
+          You may choose to save time by putting the name of the newsgroup 
+          on the command line, i.e., "postnews ba.test".  Postnews also 
+          recognizes "-f <filename>" as an option to include the text of 
+          the message from an existing file.  
+
+
+          EXAMPLE 
+          OS9> postnews
+          Newsgroups: ba.test
+          Subject: This is a test
+          Keywords:
+          Distribution: ba
+          Summary: I am testing my new UUCP software
+          Organization: Color Central Software
+
+          This is a test.  This has ONLY been a test.  Had this been an 
+          actual posting, you would have been instructed to consult another 
+          newsgroup where things more interesting than this rather boring 
+          test are even now in progress.  
+          .
+          --
+          Rick Adams / Color Central Software / ...!fico2!ccentral!rickadams
+
+          OS9>
+
+
+
+          COMPOSING NEWS:
+
+          When you are entering news to be sent, there are a number of 
+          special commands that can be used to help out, just like when 
+          you're sending mail.  
+
+          Initially, you are in OS-9's single line editor.  You can enter 
+          and change text as long as you do not hit the ENTER key.  While 
+          you are typing an article, there are various commands to assist 
+          you in composing the article.  Each of these commands starts with 
+          a tilde (~) character at the beginning of the line.  After each 
+          command is finished, with the exception of ~a and ~x, you will be 
+          returned to OS-9's single line editor.  
+
+
+
+
+
+                                                                           
+
+
+
+
+     POSTNEWS                         UUCP                         POSTNEWS
+
+
+          ~v                  Edit article using "vi". "vi" refers to the 
+                              Tandy TSEDIT editor after the "vi" patches 
+                              have been applied to enable this editor to 
+                              work in OS9 device windows.  
+
+          ~e                  Edit article using the editor defined in 
+                              either by the environment variable EDITOR or 
+                              the file mailrc (.mailrc under OSK) in your 
+                              home directory.  The editor named in 'mailrc' 
+                              overrides the one defined by EDITOR.  
+
+          ~m[<char>]          Include text of the article being replied 
+                              to.  An optional character <char> will be put 
+                              at the beginning of each line.  The default 
+                              character is ">". This can be changed in 
+                              either 'parameters' or 'mailrc' files.  If a 
+                              space is used as the character, no quote will 
+                              mark the included text.  Examples: 
+
+                                   ~m<SPACE>    This is included article
+                                   ~m<ENTER>    >This is included article
+                                   ~m-          -This is included article
+
+          ~h                  Display help message.  
+
+          ~x                  Exit POSTNEWS immediately, abandoning 
+                              article.  
+
+          ~r[<char>] <file>   Include text from file <file>. If an optional 
+                              character <char> follows '~r', each line of 
+                              the included text will be started with it.  
+                              POSTNEWS assumes <filename> is in your 
+                              current data directory unless a full pathname 
+                              is given.  Examples: 
+
+                                    ~r <file>   This is included file.
+                                    ~r$ <file>  $This is included file.
+
+                              There is no default quote character for this 
+                              command.  
+
+                              Before appending the file, the file name is 
+                              checked for an ending extention, e.g.  .ar, 
+                              .lzh, etc.  If such an extention is found, 
+                              POSTNEWS attempts to compared against the 
+                              names in the file /DD/SYS/UUCP/bin.list, if 
+                              it exists.  This file consists of a list of 
+                              names, one to a line, representing names of 
+                              binary files.  Common names would be: ar, 
+                              gif, pak, lzh, bin, z, vef, and gif.  
+                              --NOTE--: The dot (.) is NOT part of the name 
+                              in bin.list.)  If a match is found, POSTNEWS 
+                              assumes the file is a binary one and 
+                              uuencodes it before appending it.  If the 
+
+
+
+
+                                                                           
+
+
+
+
+     POSTNEWS                         UUCP                         POSTNEWS
+
+
+                              file is uuencoded, the quote char is not 
+                              used.  If there is no match or bin.list 
+                              doesn't exist, POSTNEWS proceeds as described 
+                              above.  
+
+          ~R[<char>] <file>   Works the same as ~r above except no attempt 
+                              is made to uuencode the file.  
+
+          ~a                  Abort editing the current article.  You will 
+                              be asked if you want to abort.  Only a 'y' or 
+                              'Y' will abort the article.  If you were 
+                              replying to a article, you will be returned 
+                              to that article.  Otherwise POSTNEWS will 
+                              exit.  
+
+          ~!                  Forks a shell.  CNTRL-<BREAK) will kill the 
+                              shell and you can resume composing the 
+                              article.  
+
+          ~u <file>           Uuencode <file> and append it to the 
+                              article.  
+
+
+
+          When editing an article, DO NOT attempt to do any of the 
+          following; the results are unpredictable: 
+
+              o   Change the article header To: or CC: lines.  The changes 
+                  will not be used when the mail is sent.  You can change 
+                  the Subject: line, however.  
+
+              o   Remove the blank line following the article header.  
+                  Mailers on remote systems expect this blank line to be 
+                  there and start with an End-Of-Line character 
+
+          When you are finished composing the article, you send it by 
+          entering a period (.) followed by <ENTER>. The period must be the 
+          first and only character on the line.  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     POSTNEWS                         UUCP                         POSTNEWS
+
+
+     FILES   
+
+          Use of $HOME and $MAIL below indicate directories defined by 
+          environment variables.  For CoCo and OSK, the global environment 
+          variables MAIL and HOME must be defined, e.g.: 
+
+                 MAIL=/h1/usr/spool/mail
+                 HOME=/dd/home
+
+
+          In user's home directory:
+
+               (CoCo specific files)
+              $HOME/<user>/UUCP/mailrc
+              $HOME/<user>/UUCP/signature
+              $HOME/<user>/UUCP/organization
+              $HOME/<user>/profile 
+             
+               (OSK specific files)
+              $HOME/<user>/.mailrc
+              $HOME/<user>/.signature
+              $HOME/<user>/.organization
+
+          Other files: 
+              /DD/SYS/UUCP/Parameters
+              /DD/SYS/UUCP/sequence.news
+              /DD/SYS/UUCP/sequence.spool
+              /DD/SYS/UUCP/active
+              /DD/SYS/UUCP/organization
+              /DD/SYS/UUCP/distributions
+              /DD/SYS/profile                (CoCo--global system environment)
+              ./<scratchdir>/UUCPtemp1.?            (temporary file)
+
+     SEE ALSO 
+
+          parameters.doc, mailrc.doc, signature.doc,
+          rmail.man, parameters.example
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/profile.doc	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,66 @@
+
+
+     profile                                                        profile
+
+
+     FILE   
+
+           /DD/SYS/profile
+           ./<homedir>/<user>/profile
+
+     SUMMARY:   
+
+          Pseudo-environment variables file for the CoCo.  
+
+     DESCRIPTION:   
+
+
+          Since OS-9 Level 2 on the CoCo does not yet have true environment 
+          variables, UUCPbb attempts to emulates them.  The file 'profile' 
+          contains the system and user's environment variables.  
+
+          The file /DD/SYS/profile contains the system default values.  
+          Each user can also set some of the environment variables by 
+          creating a file 'profile' in their root home (login) directory.  
+
+          If the user's profile exists, it will override the system 
+          profile.  If it doesn't the system defaults are used.  
+
+          The file consists of one declaration per line with the format: 
+
+               variable=value 
+
+          There can be no space between on either '='. At present, the UUCP 
+          package only supports the variables: TERM, HOME, MAIL, SHELL, and 
+          EDITOR. For example: 
+
+               TERM=coco3
+               HOME=/dd/usr
+               MAIL=/h1/spool/mail
+               EDITOR=ved
+               SHELL=shell+
+
+          In the case of SHELL, the value 'shell+' is suggested when 
+          referring to Shell+ v2.1 or later; while 'shell' refers to the 
+          original Microware Shell. Programs will have to internally figure 
+          how to make use of the shell environment if the system uses both 
+          Shell+ and the MW Shell or another shell.  
+
+          The user is allowed only to change the variables TERM, EDITOR and 
+          SHELL in their profile.  The variables HOME and MAIL are reserved 
+          only for /DD/SYS/profile. If they appear in the user's profile, 
+          they are ignored.  If HOME is not defined in the system profile, 
+          getenv() will use the password to try and determine the HOME 
+          environment of the user.  
+
+
+
+
+
+
+
+
+
+                                                                           
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/readnews.man	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,198 @@
+
+
+     READNEWS                         UUCP                         READNEWS
+
+
+     PROGRAM   
+
+           readnews
+
+     CALLING SEQUENCE 
+
+          readnews
+
+     SUMMARY   
+
+          Usenet news reader 
+
+     DESCRIPTION   
+
+          The READNEWS command is used to read the news articles.  It 
+          maintains a file ./<homedir>/<user>/UUCP/newsrc 
+          (./<homedir>/<user>/.newsrc under OSK) to keep track of which 
+          articles you have already seen.  It will tell you how many 
+          articles remain to be read in each newsgroup, if any, and give 
+          you an opportunity to read them.  The characters "y", "n" and "q" 
+          are recognized as meaning "yes, read this newsgroup or article 
+          now", "no, skip this newsgroup or article and go to the next 
+          one", and "quit".  
+
+          The "f" command can also be used to post a followup article to 
+          the article you just read.  The article subject, etc, are read 
+          from the article, and postnews is executed to post your followup 
+          article to the newsgroup being read.  
+
+          At any prompt in readnews, you may type "h" to get a list of all 
+          available commands for that prompt.  
+
+
+
+          COMMANDS 
+
+          There are different commands possible depending on what you are 
+          doing in readnews.  
+
+          When you are at the beginning of a newsgroup, you will see a 
+          prompt that looks like this: 
+
+              61 article unread in newsgroup ba.test--read now? [yncq]
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     READNEWS                         UUCP                         READNEWS
+
+
+          These commands are available:
+          
+               SPACE       Read unread articles in this newsgroup
+               c           Catch-up, marking all articles as read
+               d           Directory of groups
+               g <group>   Goto newsgroup
+               h/?         Help (display available commands)
+               n           No, skip this group
+               q           Quit
+               s <group>   Subscribe to newsgroup <group>
+               u [<group>] Unsubscribe from the newsgroup <group>
+                             default is current newsgroup
+               y           Yes, read unread articles
+
+
+          While you are displaying an article, a "--MORE--" prompt may 
+          display if the article is too big to fit on one screen.  You may 
+          use any of these commands at that point: 
+
+               SPACE     Show next screen
+               n         Skip to next article
+               c         Catch-up (mark all articles as read)
+               p         Skip to previous article
+               s <file>  Save article to <file>
+               w <file>  Save article to <file>
+                           without header
+               v/.       Redisplay current article
+               u         Redisplay current article rot13'd (unrot)
+               q         Quit displaying article 
+               h         Help (display available commands)
+
+
+          After the article is displayed, you will see a prompt that looks 
+          like this: 
+
+              End of article 516 (of 513-580)--What now?  [nq] 
+
+          You may then use any of these commands: 
+
+               a         Add new article in current group
+               s <file>  Save article in <file>
+               w <file>  Save article in <file> without header
+               p         Skip to previous article
+               c         Catchup (mark all articles read) 
+               f         Followup (post followup article)
+               r         Reply to article author via email
+               q         Quit
+               v/.       Redisplay current article
+               n         Skip to next article
+               #         Display article #
+               u         Redisplay current article rot13'd (unrot)
+               h         Help (displays available commands)
+               !         Fork a shell
+
+
+
+
+
+                                                                           
+
+
+
+
+     READNEWS                         UUCP                         READNEWS
+
+
+          At the end of all the newsgroups, you will see this prompt: 
+
+              End of newsgroups [ynq]?  
+
+          These commands will be available at that point: 
+
+               SPACE/n/y  Start over, read new news
+               d          Directory of groups
+               g <group>  Goto newsgroup
+               h          Help (display available commands)
+               q          Quit
+               s <group>  Subscribe to the given group
+               u <group>  Unsubscribe from given group
+
+     FILES   
+
+          Use of $HOME and $MAIL below indicate directories defined by 
+          environment variables.  For CoCo and OSK, the global environment 
+          variables MAIL and HOME must be defined, e.g.: 
+
+                 HOME=/dd/home
+
+
+          In user's home directory:
+
+               (CoCo specific files)
+              $HOME/<user>/UUCP/newsrc
+              $HOME/<user>/UUCP/oldnewsrc
+              $HOME/<user>/profile 
+             
+               (OSK specific files)
+              $HOME/<user>/.newsrc
+              $HOME/<user>/.oldnewrc
+
+          Other files: 
+              /DD/SYS/UUCP/Parameters
+              /DD/SYS/UUCP/active
+              /DD/SYS/profile                (CoCo--global system environment)
+
+     SEE ALSO 
+
+          parameters.doc, newsrc.doc, parameters.example
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/rmail.man	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,132 @@
+
+
+     RMAIL                                                            RMAIL
+
+
+     PROGRAM:   
+
+          rmail
+
+     CALLING SEQUENCE: 
+
+          rmail [<filename>] <uucp_address>
+
+     SUMMARY:   
+
+          Distribute mail message to local or remote users.
+
+     DESCRIPTION:   
+
+          RMAIL takes an email message and distributes it to the proper 
+          user based on the given uucp_address.  If the uucp_address is for 
+          a user on another system, RMAIL queues the mail to be sent 
+          remotely the next time UUCICO is run.  This program is usually 
+          run via MAIL, UUXQT or UUCICO. It is not normally executed 
+          directly by the user.  
+
+          If filename is specified, the email message is taken from that 
+          file.  If no filename is given, the message is read from standard 
+          input.  
+
+          RMAIL recognizes three special local pseudo-users.  One is user 
+          'nobody'.  This is name of RMAIL's bit bucket.  Any mail 
+          addressed to 'nobody' goes in the bit bucket.  
+
+          A second special user is 'fileserv'. Mail sent to this "user" 
+          tells RMAIL to fork the fileserver program FILESERV. The message 
+          is sent to FILESERV for processing.  (see FILESERV.MAN).  
+
+          A third special user is 'mail-server'. Mail sent to this "user" 
+          tells RMAIL to fork the program MAILSERVER. The message is piped 
+          to MAILSERVER for processing.  MAILSERVER has not been written.  
+          The intention is to allow users to write applications program to 
+          interface with UUCPbb. The application only has to read its 
+          standard input to get the passed message.  How the message is 
+          interpreted is up to the application.  The next update of RMAIL 
+          will allow many different type of psuedo-users which will be able 
+          to fork more than simply FILESERV or MAILSERVER.  
+
+          If the mail is to a valid local user, RMAIL puts the message in 
+          the user's mailbox.  The message is given the file name 
+          'mYYYYMMDDHHMMSS', where YYYYMMDDHHMMSS is the year, month, date, 
+          hour, minute and second timestamp when RMAIL processed the mail.  
+          RMAIL also updates the 'mail..list' file in the user's mailbox 
+          directory.  The top mailbox directory where all the user's mail 
+          is kept is specified by the parameter 'maildir' in 
+          /DD/SYS/UUCP/Parameters.  
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     RMAIL                                                            RMAIL
+
+
+          If the message is to a non-existent local user, the message is 
+          sent to the user specified in the Parameters file as 'errorsto'.  
+
+          On a UUCP system, the standard user, who should get bounced mail, 
+          other errors is 'postmaster'. 'postmaster' is also the user mail 
+          is sent to when a remote system doesn't know any other users on 
+          your system and wish to make inquiries.  It is STRONGLY suggested 
+          a separate 'postmaster' account be created for this purpose.  
+          Attempting to get around this by using an alias to point to 
+          another account will likely lead to strange and unpredicatable 
+          results.  
+
+
+     BUGS   
+
+          RMAIL isn't very sociable about returning undeliverable mail.  
+          Currently, it sends all such mail to the 'errorsto' user.  For 
+          now, this user will have to manually return the mail.  RMAIL 
+          really should return the mail to the original sender itself.  
+          Obviously, RMAIL needs better manners.  
+
+          On the CoCo, there is a limit to the number of messages that can 
+          be waiting.  If termcap support is not compiled in, there can be 
+          about 185 messages waiting.  With termcap support, this number 
+          will drop, probably to around 125-140. (This has not been test 
+          thoroughly.) 
+
+     FILES   
+
+           /DD/SYS/UUCP/Parameters
+           /DD/SYS/UUCP/sequence.mail
+           /DD/SYS/UUCP/sequence.rmail
+           ./<maildir>/<user>
+           ./<maildir>/<user>/mail..list
+           ./<homedir>/<user>/UUCP/aliases      (CoCo)
+           ./<homedir>/<user>/.aliases          (OSK)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/rnews.man	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,66 @@
+
+
+     RNEWS                            UUCP                            RNEWS
+
+
+     PROGRAM   
+
+          cnvrtmail
+
+     CALLING SEQUENCE: 
+
+          rnews [opts] <filename>
+          
+          opts: -xN        - N is debug level 0 (off) to 9 (highest)
+                -n<group>  - article to newsgroup <group>
+
+     SUMMARY:   
+
+          Process received Usenet newsgroups.  
+
+     DESCRIPTION:   
+
+          RNEWS is rarely run by a user.  It is normally forked by UUXQT 
+          which usually runs after UUCICO completes a call.  
+
+          The newsgroups can be batch compressed, batched or unbatched.  If 
+          they are batch compressed, the utility COMPRESS (for .Z files) 
+          must be available in either in memory or in the execution 
+          directory.  
+
+          RNEWS will uncompress the news file, if necessary.  It will then 
+          attempt to move each article to the appropriate newsgroup's 
+          directory in the news spool directory.  If there is no directory 
+          for the particular newsgroup, the article is put in the news 
+          directory 'junk'.  
+
+          When processing news, RNEWS attempts to use the RAM disk if it 
+          normally has enough free space to fit the article.  If the 
+          article is too large for the RAM disk, the directory specified by 
+          the parameter 'scratchbig' in /DD/SYS/Parameters is used.  RNEWS 
+          does not check for a disk-full error on either the RAM disk or 
+          the 'scratchbig' directory.  The user must ensure the free space 
+          exists when RNEWS is running.  If the disk fills up, the article 
+          may be partially or completely lost.  
+
+     BUGS   
+
+          Debug messages may be a little too plentiful.  
+
+     FILES   
+
+          /DD/SYS/UUCP/Parameters
+          /DD/SYS/UUCP/active
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/signature.doc	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,66 @@
+
+
+     signature                                                    signature
+
+
+     FILE   
+
+           ./<homedir>/<user>/UUCP/signature        (CoCo)
+           ./<homedir>/<user>/UUCP/alt_signature    (CoCo)
+           ./<homedir>/<user>/.signature            (OSK)
+           ./<homedir>/<user>/.alt_signature        (OSK)
+
+     SUMMARY:   
+
+          These files contain a few lines which can be added to the end of 
+          outgoing mail or news articles.  
+
+     DESCRIPTION:   
+
+
+          Each user can create a signature files in their home directory.  
+          MAILX and POSTNEWS will attempt to read the contents and append 
+          it to the outgoing message.  alt_signature (.alt_signature under 
+          OSK) is an alternative signature file file which is available 
+          with the -n option in MAILX.  
+
+          The contents of signature is high individual.  There are a few 
+          guidelines to consider: 
+
+          Signatures should be short.  Generally, four lines or so is 
+          sufficient.  The signature generally contains your name and email 
+          address(es) in case the message arrives with the From: field 
+          mangled.  Some folks put short quotes in their signature files as 
+          well.  Excessively long signatures are annoying.  It can be 
+          annoying to read a two or three line message followed by a ten 
+          line signature.  After reading a number of similar messages, it 
+          can get really annoying.  
+          
+          Each in the signature file should be less than 80 characters.  
+          Each line should end with carriage.  You cannot assume the other 
+          person's terminal will correctly wrap-around lines which are too 
+          long.  
+          
+          Do not use graphics or control characters in the signature for 
+          (or mail text for that matter).  The graphics and control 
+          characters may do nice fancy things on YOUR terminal; however, 
+          the things they do on or to a remote reader's terminal may not be 
+          so nice.  You could easily make your message unreadable for the 
+          receiver.  
+
+
+
+          EXAMPLE: 
+
+                Bob Billson, KC2WZ     | internet: bob@kc2wz.bubble.org
+                $nail:  21 Bates Way   | uucp:     ...!uunet!kc2wz!bob
+                Westfield, NJ 07090
+               
+                    "Friends don't let friends run DOS" -- Microware
+
+
+
+
+                                                                           
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/subscribe.man	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,66 @@
+
+
+     SUBSCRIBE/UNSUBSCRIBE            UUCP            SUBSCRIBE/UNSUBSCRIBE
+
+
+     PROGRAM   
+
+          subscribe
+          unsubscribe
+
+     CALLING SEQUENCE: 
+
+          subscribe <newsgroup> [<newsgroup>...]
+          unsubscribe <newsgroups> [<newsgroup>...]
+
+     SUMMARY:   
+
+          Subscribe or unsubscribe to Usenet newsgroups.  
+
+     DESCRIPTION:   
+
+
+          These commands allow individuals to select the newsgroups they 
+          are able to read with READNEWS. The complete list of newsgroups 
+          the system receives is in the file /DD/SYS/UUCP/active.  
+
+          SUBSCRIBE allows the user to subscribe to one or more of the 
+          newsgroups the system receives.  If the newsgroup name is 'all', 
+          the user is subscribed to all the newsgroups listed in the active 
+          file.  The file 'newsrc' (.newsrc under OSK) in the user's home 
+          directory is updated to reflect the changes.  
+
+          UNSUBSCRIBE allows the user to unsubscribe from one or more of 
+          the newsgroups the system receives.  If the newsgroup name is 
+          'all', the user is unsubscribed from all the newsgroups listed in 
+          the active file.  The file 'newsrc' (.newsrc under OSK) in the 
+          user's home directory is updated to reflect the changes.  
+
+          Neither SUBSCRIBE nor UNSUBSCRIBE affect the newsfeed the system 
+          gets.  For example, if the newsfeed does not normally include the 
+          rec.foods.sourdough newgroups using SUBSCRIBE is meaningless.  
+          Similarly, UNSUBSCRIBE does not remove that newsgroup from the 
+          systems newsfeed.  To make such changes, the system administrator 
+          must contact his/her feed's system admininstrator.  
+
+     FILES   
+
+           /DD/SYS/UUCP/Parameters
+           /DD/SYS/UUCP/active
+           ./<homedir>/<user>/UUCP/newsrc     (CoCo)
+           ./<homedir>/<user>/.newsrc         (OSK)
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/3rdparty/packages/uucpbb/doc/uucico.man	Fri Apr 01 17:38:11 2005 +0000
@@ -0,0 +1,462 @@
+
+
+     UUCICO                           UUCP                           UUCICO
+
+
+     PROGRAM   
+
+          uucico
+
+     CALLING SEQUENCE: 
+
+       uucico [opts] -r | <sys> [<sys>...]  [opts]
+       
+             <sys>    - call remote system as MASTER
+       
+       opts: -r       - run as SLAVE
+             -u       - do not run UUXQT at all
+             -a       - run UUXQT after each call, default is after all calls
+                          are completed
+             -l       - use RAM disk for temporary "uulog"
+             -o       - orphan UUXQT
+             -pN      - fork UUXQT with a priority of N
+             -q       - run quietly
+             -wN      - use window size of N
+             -xN      - set debug level to N (0-9), default is 0 (off), if
+                          N > 5 additional info sent to 'uulog'
+             -z       - send log info to screen if debug level is 1 to 5,
+                          overrides -l
+             -iN      - wait N minutes between call retries, default is 2
+             -tN      - try to call remote up to N times, default is 1
+
+     SUMMARY:   
+
+          This program calls a remote UUCP node and exchanges UUCP 
+          traffic.  
+
+     DESCRIPTION:   
+
+          UUCICO operates in two modes: slave or master.  The default is to 
+          run as the master.  
+
+          As the master, UUCICO takes the active role.  It dials the remote 
+          system, logs onto the remote system, and initiates a UUCP 
+          transfer.  
+
+          This version of UUCICO allows multiple sites to be given on the 
+          command line.  Each site will be tried in turn.  Any reasonable 
+          number of remote names can given on the command line.  
+          Microware's C compiler will allow up to 30 command line 
+          arguments.  You probably won't be calling 30 different remotes.  
+          If you do, you should be running more than a CoCo. :-) 
+
+          A site will be tried a specific number of time, waiting a 
+          specific number of minutes between attempts.  UUCICO repeats the 
+          calling procedure for each remote given.  NOTE: The default 
+          values can be altered by changing the values of NAPTIME in 
+          uucico.h and MAXTRIES in uucico.c.  
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     UUCICO                           UUCP                           UUCICO
+
+
+          Normally, UUCICO is run as a background task by a task scheduler 
+          such as CRON or Boisy Pitre's MCRON. UUCICO normally sends output 
+          of the call's progress to the standard output.  If UUCICO is run 
+          manually from the keyboard this output is sent to the screen.  
+          There maybe times when such progress message are undesirable such 
+          as if a BBS program starts up UUCICO. Messages on the standard 
+          output may create problems.  In this case, the -q (quiet) option 
+          should be used.  This will suppress all screen output.  Log 
+          information will still be sent to the uulog file.  
+
+          UUCICO will detect if the device (port) it is trying to call out 
+          on is already in use.  If the device is busy, UUCICO will exit 
+          with an error message.  In order to take advantage of this 
+          feature, you must use Boisy Pitre's patch to make SCF devices 
+          non-shareable.  The patch is included in the UUCPbb package.  
+
+          The slave mode is enabled with -r. In slave mode, UUCICO 
+          identifies itself to the remote system calling in and waits for 
+          that system to respond.  If the system is allowed, a file 
+          transfer is set up.  
+
+          In order to be able to take or make calls, UUCICO needs 
+          information in the files Systems, Parameters, Dialers and 
+          Devices. All these files are located in the directory 
+          /DD/SYS/UUCP. The Systems file contains the name of the system, 
+          device to use and a chat script to tell it how to log on when 
+          calling the remote.  If there is more than one phone number to 
+          reach the same remote, the Systems file must have a separate line 
+          for each number.  UUCICO will try dialing each line until it gets 
+          through or times out.  The Devices files tells UUCICO which modem 
+          goes with a particular port.  The Dialers file contains 
+          information UUCICO needs in order to use that particular modem or 
+          direct (physical) connection.  
+
+          UUCICO logs all information about calls and file transfers to the 
+          file /DD/LOG/uulog. With debug output turned off (0) (the 
+          default) UUCICO normally logs date and time of the call, each 
+          file sent/received, if the call ended normally and the call 
+          duration in seconds.  
+
+          More detailed information can be obtained by increasing the debug 
+          level.  A number from 1 to 9 causes an increasing level of 
+          information.  
+
+          Because higher debug levels create more information, the CoCo may 
+          not be able to write it all to the hard drive fast enough.  This 
+          can cause packet errors and possibly terminate the connection.  
+          To get around this problem, at high debug levels UUCICO will 
+          attempt to use the RAM disk /R0 for temporary storage of the log 
+          information.  After the call is completed, UUCICO will move the 
+          file to the permanent /DD/LOG/uulog file.  
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     UUCICO                           UUCP                           UUCICO
+
+
+     OPTIONS   
+
+          UUCICO will accept options with or without space between it and 
+          its argument.  For example, either '-i3' or '-i 3' are 
+          acceptable.  If the option requires an argument and none is 
+          given, UUCICO will exit with an error.  
+
+          "-r" tells UUCICO to run in slave mode.  In order to allow a 
+          remote system to call in, an entry is needed in the 
+          /DD/SYS/password file.  A sample entry in might look like this: 
+
+
+          nuucp,000000,2,190,/h0/cmds,/h0/usr/spool/uucppublic,ex uucico -r
+
+
+          This single entry would cover multiple systems calling in.  If 
+          using the LOGIN utility included in the UUCPbb package, you need 
+          to create an empty file named /DD/LOG/nuucp.login. Another choice 
+          is to create a separate entry in the password file for each 
+          system that calls in.  
+
+          UUCICO compares the name each remote sends with those in the 
+          Systems file.  If a match is found, UUCICO accepts the 
+          connection.  If there is no match, the connection is shut down 
+          immediately.  
+
+          The option "-z" tells UUCICO to send the debug level output to 
+          the screen instead of the file 'uulog'. This option is only valid 
+          if the debug level is set from 1 to 5. At higher debug levels 
+          this option is ignored.  If the -l option is also on the command 
+          line, it is ignore if the debug level is from 1 to 5.  
+
+          The option "-u" tells UUCICO not to run UUXQT after the phone 
+          call(s) is (are) completed.  Normally, if UUCICO receives any 
+          files from the remote it will run UUXQT after all the calls are 
+          completed to process the newly arrived mail.  There may be times 
+          when you do not wish this to happen such as when memory may be 
+          tight because of other processes running.  Or if the modem kill 
+          switch is set on your system, UUXQT may not get run.  After modem 
+          hangs up, OS-9 may kill the process and any children.  In this 
+          case, you can set your task scheduler to run UUXQT at a later 
+          time.  
+
+          The option "-a" tells UUCICO to fork UUXQT after each call is 
+          made.  This only valid if you are polling more than one remote.  
+          The default is to chain to UUXQT after all calls are made.  Since 
+          "-a" forks UUXQT, memory could get tight on some systems since 
+          UUCICO, UUXQT, RMAIL and RNEWS will all be loaded.  If this 
+          happens, UUXQT will not be able to process the mail and/or news 
+
+
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     UUCICO                           UUCP                           UUCICO
+
+
+          The option "-p" tells UUCICO to fork UUXQT with a different 
+          priority.  Normally UUXQT is forked with the same priority as 
+          UUCICO. You may wish to change this so UUXQT does not hog the 
+          system or you may want UUXQT to run a higher priority when their 
+          is lot of news to process.  
+
+          The option "-w" allows you to override the default window size 
+          set in the /DD/SYS/UUCP/Parameters file by the parameter 'window 
+          ='.  
+
+          The option "-x" sets the debug level, 0 (off) to 9 (highest). 
+          Each level gives progressively more information.  Because 5 and 
+          up will often slow down transfers, possibly causing aborts on the 
+          CoCo, UUCICO will attempt to use the RAM disk /R0 for a temporary 
+          log file.  After the call, the log will be moved to the permanent 
+          log file /DD/LOG/uulog. Because the debug level creates a lot of 
+          information, it is really not a good idea to leave it on all the 
+          time.  Doing so will make the uulog file grow quite large, quite 
+          fast!  Also there is a limit to how fast the CoCo can go.  
+          Writing lots of information to the log files is normally 
+          unnecessary.  The default information written to uulog is 
+          sufficient for normal use.  When using the RAM disk, you must be 
+          sure it has sufficient room.  This depends on how many files are 
+          to be transferred; 20K is probably enough for most situations.  
+          If the RAM disk fills up, UUCICO will NOT warn you of the disk 
+          full error.  
+
+          The option "-l" (lower case L) tells UUCICO to use /R0 regardless 
+          of the debug level.  After the call is completed, UUCICO will 
+          move the temporary log to the permanent /DD/LOG/uulog file.  This 
+          option is overridden by -z if the debug level is from 1 to 5.  
+
+          The option "-o" tells UUCICO to orphan UUXQT when it runs it.  
+          This option is only valid if "-a" is not used at the same time.  
+          UUCICO forks a UUXQT without a parent.  This may prove useful on 
+          systems where the modem kill switch is set.  Since UUXQT has no 
+          parent, it will continue running.  This option has not been 
+          thoroughly tested with the modem kill switch, so comments on it's 
+          usefulness are welcome.  
+
+          Any command line argument which is not part of an option is 
+          assumed to be the name of a remote system to call.  
+
+          UUCICO keeps track of whether not any incoming work was 
+          received.  If no work arrived, UUXQT will not be run.  
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     UUCICO                           UUCP                           UUCICO
+
+
+          Examples: 
+
+               uucico sandstorm
+               uucico -t3 sandstorm ccentral
+               uucico sandstorm -t3 ccentral -i 5
+               uucico sandstorm ccentral -aq
+               uucico -t3 -p255 sandstorm ccentral
+               uucico -u sandstorm ccentral
+
+
+          In the first example, UUCICO will attempt to connect to the 
+          remote system 'sandstorm'. It will make the one attempt (the 
+          default).  
+
+          In the second example, UUCICO will try to first to call 
+          'sandstorm' up to three times waiting one minute (the default) 
+          between each try.  Then it will move on to 'ccentral'.  
+
+          The third example is the same as the second except UUCICO will 
+          wait five minutes between attempts.  No messages will be sent to 
+          the screen.  
+
+          The default times can be changed by changing the values in the 
+          uucico.h and uucico.c source file and recompiling.  MAXTRIES is 
+          the default number of retries.  NAPTIME is the default waiting 
+          period.  
+
+          The fourth example, says to call 'sandstorm' and 'ccentral' the 
+          default number of attempts, waiting the default interval between 
+          each attempt.  However, before trying to call 'ccentral', UUXQT 
+          will be run to process the mail, if there was any.  After the 
+          call to 'ccentral', UUXQT will be run again.  
+
+          The fifth example is similar to the second.  In this case, UUXQT 
+          will be run after all calls are completed at a priority of 255.  
+
+          The last example tells UUCICO to make the calls but don't run 
+          UUXQT at all.  UUXQT will either have to be run manually or the 
+          mail will be processed the next time UUCICO runs, receives and 
+          does not have the "-u" option used.  
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+
+
+
+     UUCICO                           UUCP                           UUCICO
+
+
+     BUGS   
+
+          UUCICO has not been thoroughly tested with incoming calls.  
+          Connections between a CoCo and an MM/1 (both running UUCPbb) and 
+          two System IV & V OS-9/68K machines have been verified to work.  
+          Tests between two CoCo's have not been fully carried out.  
+          Reports of problems or lack of them :-) are most welcome.  
+
+          UUCICO has no problems making outgoing calls.  The 'g' protocol 
+          in the UUCPbb package has been tested with Sun uucico, Taylor 
+          (GNU) uucico, whatever UUNET Technologies uses, Ultrix (v4.2) 
+          uucico, HoneyDanBer (HDB) uucico, UUPC (MS-DOS UUCP program) and 
+          itself.  Tests with the MS-DOS UUCP program, FSUUCP not been 
+          done.  Reports of success or failures with MS-DOS boxes are 
+          encouraged.  
+
+          HOWEVER, it has been discovered that not all uucicos are coded to 
+          "spec". In order to "fix" [read that as support] those uucicos, 
+          we need a bit of information.  In order to send a bug report, you 
+          need to: 
+
+               1) Compile gproto.c with DEBUG defined, e.g.: 
+
+                  For the 6809: 
+                      cc -s -dOS9 -dm6809 -dDEBUG -T=/r0 -r=RELS gproto.c
+                       important parts--> ^^^^^^^        ^^^^^^^^^^^^^^^^
+
+                  For the 6309: 
+                      cc -s -dOS9 -dm6309 -dDEBUG -T=/r0 -r=RELS gproto.c
+                       important parts--> ^^^^^^^        ^^^^^^^^^^^^^^^^
+
+               2) Run MAKE to recompile uucico.  
+
+               3) Try to get the following logs: 
+
+                     a) Your site has work, the remote site doesn't.
+                     b) Your site has no work, the remote site has work.
+                     c) Your site has no work, the remote site has no work.
+                     d) Both your site and the remote site have work.
+
+               4) The type and version of uucico the remote site is using, 
+                  i.e.  Taylor, HDB, etc.  If you do not know this 
+                  information, please supply an email address for the 
+                  system administrator so s/he can be contacted.  
+
+       We DO NOT need to see the login name or password for the remote 
+       account.  Email the log as one clearly marked file to: 
+
+            bob@kc2wz.bubble.org.  
+
+       Make sure your valid email return address is also provided.  Don't 
+       depend on systems along the way not to mung the From: line in your 
+       mail header.  Phone numbers and snail mail addresses are nice, but 
+       not required.  
+
+
+
+
+                                                                           
+
+
+
+
+     UUCICO                           UUCP                           UUCICO
+
+
+       The logs will be looked at and we will try to find a solution to 
+       your particular problem.  We will also accept fixes to gproto.c.  
+
+     FILES   
+
+          /DD/LOG/uulog
+          /DD/SYS/UUCP/Parameters
+          /DD/SYS/UUCP/Systems,
+          /DD/SYS/UUCP/dialers
+          /DD/SYS/UUCP/devices
+
+     SEE ALSO 
+
+          parameters.example, systems.example, devices.example,
+          dialers.example
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                                           
+
+