ProfitPress Mega CDROM2 Shareware Freeware (MSDOS)(1992)(Eng)

home *** CD-ROM | disk | FTP | other *** search

/ ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng) / ProfitPress-MegaCDROM2.B6I / MISC / NETWORK / FSUU12R4.ZIP / FSUU12R4.DOC < prev next >

Wrap

Text File | 1991-10-20 | 49.2 KB | 1,343 lines

/-------------------------------------------------------------------------\ | Fubar Systems UUCP (FSUUCP) version 1.2 Release 4 - October 1991 | | Designed and programmed by Christopher J. Ambler, Fubar Systems. | | (C) Copyright by UUPlus(tm), 1991. | | - - - - - - - - - - - - All Rights Reserved. - - - - - - - - - - - - - | \-------------------------------------------------------------------------/ TABLE OF CONTENTS ----------------- 1. FOREWORD 2. GETTING STARTED - INSTALLATION/CONFIGURATION 3. FILES 4. DIRECTORY STRUCTURE 5. ERROR MESSAGE SUMMARY 6. % ESCAPE CODES (Usenet News) 7. REGISTRATION INFORMATION /-------------------------------------------------------------------------\ | Fubar Systems UUCP (FSUUCP) version 1.2 Release 4 - October 1991 | | Designed and programmed by Christopher J. Ambler, Fubar Systems. | | (C) Copyright by UUPlus(tm), 1991. | | - - - - - - - - - - - - All Rights Reserved. - - - - - - - - - - - - - | \-------------------------------------------------------------------------/ FOREWORD -------- I. BUGS ---- This release attemps to correct the major problems that have been sent in to Fubar Systems for correction. This version is also a completely rewritten system (Turbo C++), which increases performance. As always, there are more bugs to be found in any software package this complex. Please feel free to send bug reports to: Fubar Systems Support Staff 1742 Lima Drive San Luis Obispo, CA 93405-6817 If you would like to join the FSUUCP mailing list, send your request to subscribe to: "fsuucp-request@zeus.calpoly.edu". This list will be used as a means of answering questions regarding FSUUCP, as well as a place where future announcements regarding new releases will appear. ALL bug reports will receive attention, and will be implemented in future releases. We are also always happy to help with environment or setup problems. II. SHAREWARE --------- This software is SHAREWARE. It has taken us over two years to get this far. If you find the software of use, a $35 contribution is requested. This software may be copied and distributed as long as no files are altered in any way whatsoever (with the exception of configuration files, of course), this documentation is included intact, no charge is made for ANY reason, and those that receive it may also redistribute it under the above conditions. We reserve the right to modify distribution conditions at any time without prior notice. Firms that sell shareware for a profit may NOT include this software without the written permission of Fubar Systems. Many of these firms fail to adequately inform the customer that they are buying shareware, and what that entails. There are exceptions; if your company is one of them, please feel free to contact Fubar Systems at the address above. If you offer this software on your BBS, or use it on your BBS, the registration fee is only $20. Please indicate your BBS number and account on the registration form. Please see the file LICENSE.TXT for more licensing information. III. CONVENTIONS/ASSUMPTIONS ----------------------- This documentation is written with the assumption that those trying to install it have some basic knowledge of Usenet news and electronic mail facilities. UUCP feeds can be tricky in setup and maintenance, therefore, if this is your first time with something of this nature, we recommend you purchase a good book on UUCP management (the NutShell book "Managing UUCP and Usenet" is highly recommended) or that you seek the advice and assistance of an experienced UUCP user. All suggestions on making this package easier to use will receive prompt attention. The contact address for the Nutshell Books is: O'Reilly & Associates, Inc. 103 Morris St. Sebastapol, CA 95472 (I am told that this address is new as of 1 December, 1991. Before that date, I would guess that you should call them at the number below for the address). (707) 829-0515 (707) 829-0104, Fax or, to order: (800) 338-6887 (US and Canada) They can also be reached via email at: uunet[.uu.net]!ora!nuts This software system is as close to UNIX(tm) standard as it could be made without sacraficing functionality. It can be considered a subset of the UNIX(tm) utilities of the same name, but with certain enhancements and/or compromises in the name of functionality. This version has no password protection, as it is intended for standalone use. The integrated version of this software (FSBBS 2.0) does support multiple clients and password protection. Details of this package can be obtained by contacting Fubar Systems. FSBBS 2.0 is scheduled for a First Quarter 1992 release. /-------------------------------------------------------------------------\ | Fubar Systems UUCP (FSUUCP) version 1.2 Release 4 - October 1991 | | Designed and programmed by Christopher J. Ambler, Fubar Systems. | | (C) Copyright by UUPlus(tm), 1991. | | - - - - - - - - - - - - All Rights Reserved. - - - - - - - - - - - - - | \-------------------------------------------------------------------------/ GETTING STARTED - INSTALLATION/CONFIGURATION -------------------------------------------- STEP 1: Run the installer ------------------------- This release incorporates an installer program that we hope will make installing and configuring this package easier. We welcome suggestions and comments on this program. To begin installation of FSUUCP 1.2: 1) Unpack the distribution ZIP file into a scratch directory or onto a disk. 2) Type "install" and follow the prompted instructions. The installer will create the proper directories and move the files into them, as well as create certain configuration files, some of which will need to be hand edited. Be sure to supply the two variables that are ESSENTIAL for FSUUCP operation, "logname" and "sysname." "logname" is the single UUCP name of your machine (eg. camelot) and "sysname" is the domain-ized name of your machine (eg. camelot.arthur.com). If you do not have a domain, enter your machine name followed by the psuedo-domain ".UUCP" (eg. camelot.UUCP), and look into getting a domain! 3) Edit the configuration files STEP 2: Set up the following DOS environment variables ------------------------------------------------------ This variable is MANDATORY for proper operation of FSUUCP: "FSUUCP" - Gives the directory path to the "FSUUCP.CFG" configuration file. If this variable is not present, then FSUUCP.CFG MUST be somewhere on the DOS path for proper operation. Ok, so it's not mandatory, but be sure to either set it, or put FSUUCP.CFG on the path. The following variables are optional: "TZ" - Timezone. Used to append your timezone to time and date information. For example, "PDT" for Pacific Daylight Time. Without it, FSUUCP assumes Eastern time. (Yes, Fubar Systems is located in drought-stricken California, but Turbo C++ defaults to eastern time, so argue with Borland). "USER" - Name of the user currently using this FSUUCP session. This variable determines which mailbox to use and also which return paths are returned by mail and news. This variable overrides any such setting in the FSUUCP.CFG file. "HANDLE" - Stores the value of field which prints out handle information on mail and news messages. If you do not have a handle, simply set this variable to your real name. This variable overrides any such setting in the FSUUCP.CFG file. STEP 3: Edit the following files -------------------------------- The following files need to be edited to reflect your own system. Some are optional, and will work as supplied, while others NEED to be edited, and are marked with an asterisk. * [basedir]\fsuucp.cfg * [libdir]\uucp\systems * [libdir]\news\active * [libdir]\news\batcher.cfg [libdir]\news\dist * [libdir]\news\explist [libdir]\news\headers [libdir]\news\modrecdg [libdir]\news\recordin * [libdir]\news\sys [libdir]\aliases See the description of the files in section 3, part III, Include files and functions, for information on how to edit these files. Also, note that there is documentation in the files themselves. STEP 4: Create home directories ------------------------------- Create a directory for each user that will be using FSUUCP in the [home] directory that you specified in the installer. You may optionally create a mailrc (mailrc) file in this directory for each user, as well as a signature file (sig). A news reading control file (newsrc) will be created automatically the first time the user reads news. /-------------------------------------------------------------------------\ | Fubar Systems UUCP (FSUUCP) version 1.2 Release 4 - October 1991 | | Designed and programmed by Christopher J. Ambler, Fubar Systems. | | (C) Copyright by UUPlus(tm), 1991. | | - - - - - - - - - - - - All Rights Reserved. - - - - - - - - - - - - - | \-------------------------------------------------------------------------/ INCLUDED FILES / FUNCTIONS -------------------------- Please verify that you have the following files in your copy of FSUUCP 1.2. These files are very important to the proper operation of the software. If you do find that you are missing any of these files, please contact us via one of the methods given in the FOREWORD section. The following files should be in your distribution file (FSUU12R4.ZIP): I. DISTRIBUTION FILES ------------------ README.1ST (read this if you haven't already) LICENSE.TXT (licensing information, please read also) FSUU12R4.DOC (this document) HISTORY (detailed feature history) ALIASES (example aliases file) EXE.ZIP (zip file of the executable programs) LIBUUCP.ZIP (zip file of the UUCP libraries) LIBNEWS.ZIP (zip file of the NEWS libraries) INSTALL.EXE (installer) INSTHELP.HLP (installer help file) II. EXECUTABLE FILES ---------------- UUCICO.EXE ---------- This program implements a standard 'g' protocol transfer mechanism. Usage: uucico [-r 1|0] [-s system] [-x debug] [-p] [-v] [-h] [-ln] [-z] [-f filename] The site specified with "-s" must be in the systems file. The "-r" option specifies either slave (0) or master (1) mode when starting up the program. To call another system, use the -r1 option. To receive a call, use the -r0 option. At this time, uucico assumes that the other system has logged in and is waiting for the start of the UUCP session to begin. If you have need to allow systems to poll you at specified or unspecified times, you probably need FSBBS, which implements the front end to allow systems to log in, and provides password protection. --> The -s and -r arguments are MANDATORY. All others are optional. The "-x" option allows for specifying a debug level from 1 to 9. These debug levels provide different amounts of information necessary for debugging a connection. (i.e. 1 provides the least information, 9 the most. A rather gluttonous amount, really). Once a connection is stable, debug level 3 is usually sufficient. Debug information can be dumped to the printer in addition to being displayed on the screen by using the "-p" option. Note that with a high debug level, a large amount of information will be created, and may cause performance degradation if the printer being used has a small buffer. It may even hang UUCICO. Nobody here is brave enough to try debug levels greater than 5 with the -p option. "-v" will print the current version number of FSUUCP. The "-h" option tells uucico to ignore the host name sent by the remote machine. It has the same effect as the "ignorehost on" option in the FSUUCP.CFG file. If -h is used, the ignorehost command in the FSUUCP.CFG file will be ignored. The "-l" option allows the maximum length (number of characters) of the sitename to be specified when calling a remote system. This switch is intended to provide compatibility with systems that do not follow the UUCP standard of a maximum of 8 characters in a sitename. The value specified here will override any value set in the FSUUCP.CFG file. The "-f" option allows debug information to be diverted to a file. The "-z" option is a dirty hack to strip NULL characters that follow returns. You should never need it. If you do, see the administrator of the site that you are calling about getting the uucico connection working in RAW mode. BATCHER.EXE ----------- This program "batches" news into the proper files for transmission and places them in the appropriate directories to await transmission. The batching takes place according to the parameters supplied in the BATCHER.CFG file. Note that batcher will fail if the proper spooling directories have note been created. See SETUP for more information on setting up the proper directories. Usage: batcher [-s system] [-v] The "-s" flag allows you to specify which system to batch news articles for. Without it, it will batch for all systems with batch files. The "-v" option specifies "verbose" mode. If this flag is used, then batcher will show all the actions that it takes in preparing batches. Without the -v option, batcher will display the copyright, but not output any information. This "quiet" mode is the default as some systems run batcher often and don't want all the output. EXPIRE.EXE ---------- Expire removes news articles that are "n" days old. The value for "n" is specified in the explist file. Usage: expire [-g group] [-d days] [-t] [-v] The "-g" option lets you specify a specific group or group set to expire. Ex: expire -g rec expire -g comp.sys.all expire -g comp,rec,alt.sex.all The "-d" option allows you to override the expire value in days that is specified in the explist file. The "-t" option runs expire in test mode, i.e it shows its actions but doesn't perform any expirations. The "-v" option runs expire in verbose mode, so that all debugging output is displayed. UUXQT.EXE --------- Uuxqt places incoming data files from UUCP transfer in the proper directory structure (i.e. mail is delivered to the proper mailbox and news is placed in the proper directory). UUXQT should be invoked after a call with UUCICO. It is reccomended that you do this via a batch file, for example: uucico -r1 -x5 -s%1 uuxqt -s%1 where the system name will be substituted for the %1 variable, when given on the command line. Usage: uuxqt [-s system] "system" must be a system name specified in your systems file. MAIL.EXE -------- Mail is an RFC-822 compliant mailer subset. This program is tricky and is constantly being improved for later releases. Please inform us of any bugs you find or features you would like in this program. This program is as close to UNIX(tm) mail as possible. For help in receive mode, type "?"; for help in composition mode (sending mail), press the F1 key. Mail now has (as of version 1.2, Release 3) a full-screen editor. This is brand new, so be sure and drop us a line letting us know what you think of it. For sending mail: Usage: mail <valid address(s)> For receiving mail: Usage: mail mail [-f filename] The "-f" option starts mail using the filename that is specified instead of the default mail spool. There is no account security provided for access to mailboxes. If you require user account security, it is suggested that you use FSBBS and require all users to access the system via modem. FSBBS provides complete account security. POSTNEWS.EXE ------------ This program allows you to post news to the network. Articles posted with this program must be "batched" using "batcher.exe" before being transferred, but are added immediately to the local newsgroups. Usage: postnews (no command line arguments) READNEWS.EXE ------------ This program is a subset of the standard readnews system. It allows access to the newsgroups and articles received via UUCP transfer. Some features are not implemented due to the constraints of the PC, while others will be implemented in the future. As with mail, please feel free to send suggestions regarding this program. Usage: readnews [-c] [newsgroup] The "-c" option checks all currently subscribed-to newsgroups and reports back with the number of new messages in each. Upon startup, readnews performs a sanity check between the newsrc and active files. If a newsgroup is in the active file but not in the newsrc, the user is prompted to add this group as a new group. If the converse of this is true (i.e. a newsgroup is in the newsrc but not in the active file), then readnews will remove it from the newsrc and inform the user that a bogus group was found and removed. Readnews also uses the full screen editor. F1 will bring up help information for using the editor. UULOG.EXE --------- This program displays UUCP log entries for systems or users from the LOGFILE. Usage: uulog [-s system] [-u user] UUSNAP.EXE ---------- This program displays a "snapshot" list of all UUCP jobs queued and ready for transfer. Usage: uusnap (no command line arguments) UUQ.EXE ------- Uuq displays detailed information about the list of all UUCP jobs queued and ready for transfer. Usage: uuq [-l] [-s system] uuq [-d nnnn] The "-l" option displays the information in "long" format, providing more detailed information regarding queued jobs. The "-s" option provides output for only the specified system. The "-d" option, with the four digit job number, deletes that job from the queue. ACTMAKE.EXE ----------- Actmake uses the newsgroups in the active file to create the proper directories for news storage under the NEWS base directory. This program will also verify any news directories that are already in place. When adding new newsgroups, it's often easiest to add the to the active file, and just run actmake. Actmake will not remove newsgroup directories that are not mentioned in the active file; these need to be removed manually. Usage: actmake (no command line arguments) FIXACTIV.EXE ------------ Fixactiv reads the current active file, and scans the Usenet news directories for the lowest and highest articles, repairing the active file to these values. Warning - If there are no articles, active will be reset to 0 for that newsgroup. To override this feature, use the [-r] option to retain the highest article number. III. SUPPORT FILES ------------- Below is a description of the function of each file, the file format, and some example lines. Note that some fields in these files will be set up automatically by the installer. These cases are noted below. Also note that there is probably better documentation in the example files provided in the distribution. configuration file ([basedir]\fsuucp.cfg) ----------------------------------------- This file controls execution of FSUUCP. Lines consist of a control variable and a value, seperated by whitespace (space or tab). This file will be created and set up by the installer. After creating this file, the installer will place it in the base directory, along with the rest of the executables. - sysname ------- "sysname" is the full domainized name of your site. If you do not have a domain name, use the same value as in logname, with the ".UUCP" psuedo- domain appended. Ex: sysname vogonsys.space.big.com sysname vogonsys.UUCP - logname ------- "logname" is the standard UUCP site name. This is the name that other machines recognize your machine by. Ex: logname vogonsys - user ---- "user" is the name of the user currently using the FSUUCP session. This determines which mailbox to use, as well as which return paths are returned by mail and news. Note that the value of the environment variable USER will override this setting. Ex: user zaphod Needs to be hand edited. - handle ------ "handle" is the string that is printed in both mail and news headers to identify a user. If you do not wish to have a handle, simply enter your real name here. Note that the value of the environment variable "HANDLE" will override this setting. Ex: handle Zaphod Beebelbrox Needs to be hand edited. - spool ----- This is the base path for the spool directory. The spool directory holds the data and control files for mail and news that are waiting for transfer. See below for more information on the spool directory structure. Ex: spool c:\fsuucp\spool This field is completed by the installation program. - logfile ------- This is the name for the UUCP logging file. FSUUCP generates log files that are even uglier than UNIX(tm) log files, but there is useful information in them for debugging purposes and feed testing. Ex: logfile c:\fsuucp\spool\uucp\logfile This field is completed by the installation program. - organization ------------ This is the organization field which is printed in Usenet message headers Ex: organization Dr. Ho's Secret Laboratory and Daycare Centre Needs to be hand edited. - smarthost --------- This is a valid UUCP bang-path to your nearest or most trusted smarthost. At this time, FSUUCP does not support domainized mailing by itself. If a mail path is generated that FSUUCP does not understand, it will punt the message off to this site, hoping it can make sense of it. Ex: smarthost foo!bar!ucbvax In this example, mail to "spock@enterprise.ufp.com" would be mailed as "foo!bar!ucbvax!spock@enterprise.ufp.com", parsing from left to right. (That is, it would be sent to "foo"). Be sure that the first name in the smarthost field is a system that you connect directly to, and that it is mentioned in your SYSTEMS file. Needs to be hand edited. - libdir ------ This is the base path for the LIB directory. Within LIB are the control files for UUCP and NEWS. See below for more information on the lib directory structure. Ex: libdir c:\fsuucp\lib This field is completed by the installation program. - home ---- This is the directory under which each user will have a home directory for storing a mailrc, sig, and newsrc file. This field is completed by the installation program. (though you will have to create the individual user directories under it yourself) - pubdir ------ This is the path name for the directory which holds all files that are neither mail nor news. This path is being implemented and reserved for future use. This field is completed by the installation program. - news ---- This is the base path for the Usenet news directory. All newsgroup storage areas are based off of this path. See below for more information on the news directory structure. Ex: news c:\fsuucp\news This field is completed by the installation program. The installer will also create [news]\outgoing, for outgoing batch files. - iinit ----- - oinit ----- These fields allow initialization strings to be sent to the modem upon startup. Common uses include: turning the speaker on or off, turning on MNP data buffers, and setting up the dialing speed. Note that FSUUCP will send this information regardless of the dialer type in the systems. The "oinit" field is used to initialize the modem for outgoing calls, while the "iinit" field initializes it for incoming calls. Note also that FSUUCP automatically sends an ATZ before sending this information, if the dialer is not "direct". Note also that in direct mode, specifying "\^" in either of these init fields will surpress the return on the end of the string, and the "\^" will not be sent. Most errors in startup occur as a result of incorrect modem initialization strings. This is especially true of modems with MNP capability. It is strongly suggested that for these modems, you include the "&F" string (factory settings) along with any other initialization strings. Ex: oinit AT L3 M1 S11=42 X4 iinit AT M1 S0=1 Needs to be hand edited. - port ---- This is the COM port to use. 1 is equivilant to COM1, 2 is COM2, etc. Ex: port 1 Needs to be hand edited. - editor ------ This is the switch for determining which editor to use. FSUUCP has 2 internal editors, or allows you to specify your own. The internal editors are "line" and "visual" and specify the line-by-line and full-screen-visual editors. Ex: editor line Ex: editor visual Ex: editor c:\fsuucp\bin\vi.exe - ramdisk ------- If this optional field is placed in the fsuucp.cfg file, then all temporary storage will use the root directory of the drive specified. If no ramdisk is used, then temporary storage will use the path [spool]\uucp\tmp for all temporary files. Ex: ramdisk e Needs to be hand edited. (optional) - serveralias ----------- This optional field allows a remote machine to store files with server-dependent drive specifications in them. This is used by batcher.exe to correctly access news articles for batching. For example, if a network is running such that the remote machine references the server's c: drive as f:, this field allows batcher to run using the correct reference (c:). Ex: serveralias c In this example, any references in a batch file in [news]/outgoing for any drive letter will be changed to c. This unconditional mapping allows multiple workstations to map the server's news spool to any letter, and allow the server to correctly access the articles. Needs to be hand edited. (optional) - autosig ------- This field controls the status of the automatic appending of signature files to mail messages. The default setting is always off. If you set it on, your signature ([home]\[user]\sig) will be appended to your outgoing mail messages. Ex: autosig on Note that any value other than "on" will turn this option off. Signatures are automatically appended to news articles if a sig file exsts. Needs to be hand edited. (optional) - BIOS ---- Setting this value to "on" causes all output to be channeled through BIOS calls for aid in BBS door operation. Ex: bios on Needs to be hand edited. (optional) - timeout ------- This field controls the amount of time that UUCICO will wait at any prompt before exiting. Make sure that modem register S7 is set to the same value as this field. Setting of this register can be accomplished by sending it as one of the characters in the "onit" field mentioned above. The default timeout is 30 seconds. Ex: timeout 45 Needs to be hand edited. (optional) - attribution ----------- This field allows you to create the format for the "attribution" line in news messages using the percent escape codes. See section "% ESCAPE CODES" for more details. Ex: attribution In article %i, %f writes: Needs to be hand edited. (optional) ------------------------------------------------------------------------------ news reading file ([home]\[username]\newsrc) -------------------------------------------- This file controls how newsgroups are read. Simply put, it contains the newsgroup name, a control character, and the highest message read. The control character is a colon (":") for a newsgroup that you are subscribed to, and a bang ("!") for a group you are not subscribed to. This file will be created automatically the first time each user runs READNEWS. Example lines: alt.sex:69 alt.drugs:42 alt.gambling:21 rec.arts.rocknroll:17 alt.weemba.sheep!2 ------------------------------------------------------------------------------- news active file ([libdir]\news\active) --------------------------------------- This file contains information about all the newsgroups that your system knows about and cares to receive. Each newsgroup is on its own line with the following format: group lseq hseq post eg: alt.bbs 0000000000 0000000000 y where: "group" is the name of the newsgroup (eg. rec.arts.startrek.info) "lseq" is a word containing the lowest message available in the newsgroup. "hseq" is a word containing the highest message available in the newsgroup. "post" is a character describing the post permissions for that newsgroup. "y" allows posting, "x" does not, "m" denotes a moderated newsgroup, in which case the distribution is replaced with the email address of the moderator. These fields are maintained automatically by the RNEWS module, which is called by UUXQT and READ/POSTNEWS ------------------------------------------------------------------------------- batcher control file ([libdir]\news\batcher.cfg) ------------------------------------------------ This file controls the parameters for news batching. Documentation is found in the example batcher.cfg file provided. ------------------------------------------------------------------------------- header control file ([libdir]\news\headers) ------------------------------------------- This file controls the displaying of headers within news. The provided file is set up for a standard news configuration. You may edit it to insert any headers you wish, however DO NOT delete any of the preexisting headers or else news will crash. Further documentation is included in the file. ------------------------------------------------------------------------------- Posting recording ([libdir]\news\recordin) ------------------------------------------ This file is displayed before going to the editor when a user goes to post news. It usually contains a message indicating that posting will cost the net thousands of zorkmids, or to remind users not to post any trade secrets. ------------------------------------------------------------------------------- signature file ([home]\[username]\sig) -------------------------------------- This (optional) file can contain a signature for each user, which will be appended to the end of every Usenet news posting. It is common netiquette to keep the signature at or below 4 lines, if possible, to cut down on the size of news articles. If you wish to put a note in your sig that you're running FSUUCP, you would have the everlasting gratitude of the author! ------------------------------------------------------------------------------- mail reading file ([home]\[username]\mailrc) -------------------------------------------- This file is used to create mail aliases that the mail program can use in delivering mail. The format of the file is: "#" denotes a comment line, and alias lines have the alias to be used and the delivery path seperated by a whitespace. Ex: # Forward mail to Mr. Beebelbrox # alias zaphod goldhart!zaphod # # Marvin is really "marv" # alias marvin marv # # # alias 42list zaphod marv phred bill@future ted@future Please note that this is an optional file and that its absence will not hinder the performance of FSUUCP. ------------------------------------------------------------------------------- mail aliasing file ([libdir]\aliases ------------------------------------ The above aliasing is supported on a global basis by creating an aliases file. Network aliasing of machines is also supported. This allows you to alias local machines so that mail to a server can be delivered locally. The command is "iam". Ex: iam fubarsys.slo.ca.us iam fubarsys.com iam fubarsys iam bbs.fubarsys.com iam bbs iam amoure.fubarsys.com iam amoure iam erotica.fubarsys.com iam erotica Any mail received with these addresses will be treated and delivered as local mail. Please note that this is an optional file and that its absence will not hinder the performance of FSUUCP. ------------------------------------------------------------------------------- sys file ([libdir]\news\sys) ---------------------------- Examples and documentation for this file are included as a sample sys file. -------------------------------------------------------------------------------- systems file ([libdir]\uucp\systems) ------------------------------------ The systems file controls how FSUUCP logs into the remote system. Think of it as a basic login script processor. Here is a sample systems entry. Note that this is one complete line. For the sake of this documentation, it has been broken up, but in the systems file, it should be contiguous. joltsys Any Hayes 2400 ATDT5551212 "" <CR> TCP\s> set\sbinary\son TCP\s> c\scsl "" \r tion:\s joltsys ogin: me ssword: itsmeagain joltsys: the system we are calling. This should be the same as the entries in the batcher.cfg and sys files. If a system does not appear here, you cannot send mail directly to it. Any: The time you may call. Currently, timing is not implemented. Soon, FSUUCP will support calling systems at specific times. Hayes: The dialer type. Currently, FSUUCP supports "hayes" and "direct" dialers. The hayes type assumes a hayes compatible modem. 2400: the baud rate at which to set the communications port. ATDT5551212: the string to dial. For a direct connection, you may substitute this for anything you need to wake the connection up. If nothing else, put in a return ("\r"). THE REST OF THE systems LINE ---------------------------- The rest of the systems line is a send/expect pair script. In this instance, "" means expect nothing, and send a carraige return sequence. The <CR> is unique to FSUUCP, it directs UUCICO to send a return once per second for 10 seconds until something is received from the remote site. The rest of the lines are just strings to expect from the remote site, and what to send when that string is seen. ESCAPE CODES ------------ The systems send/expect script processor understands some basic escape codes: \b - send break \r - send return \n - send newline \t - send tab \d - flush line, delay 1 second \s - send space \c - do NOT send a return at the end of this line (default is to do so) \\ - send a backslash There is more documentation in the distributed systems file. NOTE ---- Editing an systems entry to work is a long and sometimes VERY difficult process! No two system are alike, and it takes some getting used to and a bit of skill to get your systems entry to log you in correctly every time. This is probably where you'll spend the most time configuring FSUUCP. GOOD LUCK! /-------------------------------------------------------------------------\ | Fubar Systems UUCP (FSUUCP) version 1.2 Release 4 - October 1991 | | Designed and programmed by Christopher J. Ambler, Fubar Systems. | | (C) Copyright by UUPlus(tm), 1991. | | - - - - - - - - - - - - All Rights Reserved. - - - - - - - - - - - - - | \-------------------------------------------------------------------------/ DIRECTORY STRUCTURE ------------------- I. INSTALLER --------- The new installation module should create the appropriate directory structure for you automatically. The following information is provided for informational and debugging purposes, should it be needed after initial installation. These paths are also referred to in later sections regarding editing of configuration files. II. DIRECTORIES ----------- BASEDIR: The main directory should have executables and FSUUCP.CFG. HOME: The directory in which all user directories go. LIB: This is the base path for control files used by UUCP and NEWS. LIB\NEWS: Usenet news control files. LIB\UUCP: UUCP control files. NEWS: This is where all Usenet news and related information is stored. NEWS\OUTGOING: outgoing batch information NEWS\[GROUPS]: newsgroups. Examples: \NEWS\REC\ARTS\STARTREK \NEWS\REC\HUMOR \NEWS\REC\HUMOR\FUNNY Whereas newsgroups are seperated by a "." in actual use, the articles are stored in directories in which the "." has been replaced by a "\". SPOOL: This is where all outgoing and incoming mail and news is stored. SPOOL\MAIL: All local mailboxes are stored here. SPOOL\NEWS: Temporary news storage space, news logs and arbitron results. SPOOL\UUCP: This is the base directory for all UUCP file storage. There is a directory for your system which contains all the outgoing command files. There are directories for each system that you talk to, which contains outgoing and incoming data and command files for that system. UUCICO transports files in and out of these directories, and UUXQT executes those command files which are bound for your system, or which your system needs to handle SPOOL\UUCP\TMP - Temporary UUCP file storage space. SPOOL\UUCP\[SYSTEM] - A directory for each system you poll (up to 8 chars). NOTE: Please be sure that you use up to the full 8 characters! FSUUCP now supports full system directory names. If a system name is less than 8 characters, that's fine. ANOTHER NOTE: FSUUCP will create spool directories that need to exist if they already don't. /-------------------------------------------------------------------------\ | Fubar Systems UUCP (FSUUCP) version 1.2 Release 4 - October 1991 | | Designed and programmed by Christopher J. Ambler, Fubar Systems. | | (C) Copyright by UUPlus(tm), 1991. | | - - - - - - - - - - - - All Rights Reserved. - - - - - - - - - - - - - | \-------------------------------------------------------------------------/ ERROR MESSAGE SUMMARY --------------------- The following is a list of the possible error messages with which UUCICO can terminate. Negotiation phase ----------------- STARTUP: rmsg timeout (M1) STARTUP: rmsg timeout (M2) STARTUP: rmsg timeout (M3) STARTUP: rmsg timeout (S1) STARTUP: rmsg timeout (S2) FSUUCP has timed out while waiting for data from the remote site. The code in parenthesis designates where in the process the timeout occured. M codes are for master and S codes are for slave mode. STARTUP: Shere error [data] FSUUCP did not receive an "=" as the 6th character in the Shere message expected at this point. The actual message received is displayed. To keep this from being a problem, define "ignorehost" as described above. STARTUP: host name error [data] The host name provided by the remote did not match the one supplied to uucico. The actual Shere message received is displayed. STARTUP: No U or No common protocol [data] STARTUP: No P or No common protocol [data] No protocol message was received, or no common protocols could be found. The data sent from the remote is displayed. STARTUP: M2 not OK, got [data] No "ROK" message was received. The data sent from the remote is displayed. SETPROTO: Could not find protocol The protocol agreed upon could not be found in the protocol table. Since FSUUCP only supports "g" at this time, this message should never appear. Control Phase ------------- SBREAK: error sending [H] message (sndpkt) SBREAK: error receiving [H] reply (getpkt) An "H" message was expected and was never seen. SEND: malformed command line [data] A badly formed command line was found. The actual command line is displayed. SEND: invalid request: [data] The remote has sent an invalid request. The actual request is displayed. SDF: error sending request SDF: error receiving reply An error occured sending or receiving a command to/from the remote. SDF: did not get 'Y' got [data] FSUUCP did not receive permission to complete the request. The actual reply is displayed. File control Phase ------------------ RECEIVE: [error] closing [filename] RECEIVE: Error writing data to [filename] SEND: [error] opening workfile [filename] SEND: error opening command file [filename] A DOS error occured while operating on the file "filename" Transfer Phase -------------- SDF: sendpkt failure SCHKDIR: sendpkt failure RECEIVE: sendpkt failure (SY) RECEIVE: sendpkt failure (CY) The packet sending mechanism failed. RECEIVE: getpkt failure RECEIVE: getpkt failure The packet receiving mechanism failed. The above errors are usually caused by phone noise or an error on the remote side. A simple solution is to wait a short time and then re-poll the site. /-------------------------------------------------------------------------\ | Fubar Systems UUCP (FSUUCP) version 1.2 Release 4 - October 1991 | | Designed and programmed by Christopher J. Ambler, Fubar Systems. | | (C) Copyright by UUPlus(tm), 1991. | | - - - - - - - - - - - - All Rights Reserved. - - - - - - - - - - - - - | \-------------------------------------------------------------------------/ % ESCAPE CODES -------------- All of the following escape codes can be used to format the "attribution" strings within news. They are primarilly used internally. %a - current article number %c - news directory %C - current newsgroup, dot format %d - full name of newsgroup directory (using "\" format) %D - "Distribution:" line from the current article %t - "From:" line from the current article, or the "Reply-To:" line if there is one. Comments (such as the full name) are not stripped out. %u - Host name (your machine's name) - equivalent to "logname" field in fsuucp.cfg %i - "Message-I.D.:" line from the current article, with <> guaranteed %A - login name (yours) - equivalent to "USER" environment variable or "user" field in fsuucp.cfg %n - "Newsgroups:" line from the current article %W - Full name (yours) - equivalent to "HANDLE" environment variable or "handle" field in fsuucp.cfg %o - organization (yours) - equivalent to "organization" field in fsuucp.cfg. %s - subject %S - subject, with one "Re:" stripped off %T - "To:" line derived from the "Path:" line of the current article to produce a uucp path %x - the news library directory %Z - domainized system name - equivalent to the "sysname" field in fsuucp.cfg %% - a literal percent sign /-------------------------------------------------------------------------\ | Fubar Systems UUCP (FSUUCP) version 1.2 Release 4 - October 1991 | | Designed and programmed by Christopher J. Ambler, Fubar Systems. | | (C) Copyright by UUPlus(tm), 1991. | | - - - - - - - - - - - - All Rights Reserved. - - - - - - - - - - - - - | \-------------------------------------------------------------------------/ ------------------------------ cut here -------------------------------------- REGISTRATION FORM FOR FSUUCP ---------------------------- FSUUCP 1.2 R4 102091E-REG - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Please provide the following information: Name: ____________________________________________________________________ Address: _________________________________________________________________ City, ST, zip: ___________________________________________________________ Voice Phone: _____________________________________________________________ UUCP Node Name: __________________________________________________________ Domain Address: __________________________________________________________ Your E-mail address: _____________________________________________________ Computer Type: ___________________________________________________________ Other UUCP/Communications software: ______________________________________ From where did you acquire FSUUCP: _______________________________________ Comments? Type of registration: [ ] $35 user [ ] $20 BBS (please detail below) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - FSUUCP BBS SYSTEM REGISTRATION FORM ----------------------------------- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - If you run a BBS: Name of BBS: _____________________________________________________________ Up since: ________________________________________________________________ Phone #: _________________________________________________________________ Max Baud: ____________ MNP/Protocols?: __________________________________ Communication Parametres: ________________________________________________ Sysop Name/Handle: _______________________________________________________ Account for Fubar Systems: _______________________________________________ (Preferably "Fubar" or "Fubar Systems") Password for this account: _______________________________________________ --------------------------------------------------------------------------------