WELCOME TO THE BFDS FILE DISTRIBUTION NETWORK!

Introduction to the BFDS:

  BFDS stands for the Batch File Distribution System.  It is a File
  Distribution Network for distributing the various utilities, files and
  information used in Batch File Scripts.  The file distribution has been
  established as an adjunct to the BATPOWER echo available on many   
  Fido-Net Systems.  It is linked to systems world wide and still 
  growing

Requirements for Joining the BFDS as a distribution Site:

 1)  You must run a Fido-Net compatible mailer, capable of accepting mail and
     forwarding echo mail and data files.

 2)  You must run a File distribution software package capable of processing
     data Files and *.TIC control files.

 3)  It is the general requirement that the BFDS file be made available for
     download and or Freq or DFreq as per the restrictions of your BBS system.

 4)  To be a "registered" BFDS site please fill out the BFDS_APP.TXT form and
     send via Netmail or File Attach to 1:141/1135 or 1:141/1136. You system
     will then be listed in the BFDS_BBS.TXT list as an official site for files
     Hatched into the BFDS.

Follow the simple steps below to get yourself up and running.

 1)  Create a file area called BFDS - this is where the files will reside. 
     Make it available to regular users on your BBS.

 2)  Create a message area called BFDS_MAIL - this is the echo used for
     communication between BFDS nodes.  Anything related to BFDS is welcomed in
     this echo.  The BFDS_MAIL echo is governed by the traditional FIDO-NET
     rules pertaining to ECHO-MAIL and is moderated by yours truly.  If you
     want to allow people not-related with BFDS to have a peek at it - feel
     free; (However, I can't imagine why anybody would want to read it) but you
     MUST limit the postings only to yourself.  This Echo is intended for 
     systems who wish to Hatch files into the BFDS_ADM return FDN.

    NOTE:  If you do not wish to hatch files you do not need this echo area!

 3)  Session and TICK passwords: It is up to your up/down link (and yourself)
     to decide if you need them.

 4)  Contact the SYSOP on the board that you'll be feeding from.  He/she should
     set you up in his/hers TICK and e-mail routing configuration files.  If
     for any reason you are not happy with the feed (your modems don't like
     each other, or some other such thing) contact me @ 1:141/1135 or
     1:141/1136 and I'll suggest an alternate feed.  But whatever you do,
     please keep me informed.  The sysop that you will be requesting a feed
     from is NOT required to hook you up.  If he/she chooses not to provide you
     with a feed it's probably for some good reasons.  This is a loose group of
     volunteers, and there is no law requiring anybody to cooperate.

 5)  It is assumed that you'll be calling your up/link node to pick up the
     feeds (BFDS and BFDS_MAIL).  The frequency with which you'll call is up to
     you and your up-link.  I suggest that you call at least once a week, but
     if you choose to do that daily it's fine too.  Just make sure that you let
     your up-link know.

 6)  IMPORTANT:  After you are all configured and confident that everything is
     A-OK, fire up a message in BFDS_MAIL to let us all know that you are up
     and running.  I will update the routing information and change your status
     from NEW to PERM.  However, if you are not confident, fire a "help-wanted"
     message - somebody should be able to lend a hand...

 7)  BFDS_MAIL Echo:  The message echo is required for all nodes who wish to
     Hatch files into the BFDS file echo.  If you are feeding a system who does
     not want the echo please do not allow that node to hatch into the BFDS.

 8)  HATCHING:  The BFDS allows open hatching for all registered nodes.  Any
     Node that is receiving the BFDS file echo *and* the BFDS_MAIL message echo
     may hatch files.

 9)  Archive types: The preferred archive type is ZIP, however .ARJ, ARC, & LZH
     archives may be hatched into the BFDS.  It is NOT required that you
     maintain the archive type on your BBS (with the exception of the
     BFDS_KIT.ZIP) as long as the file descriptions remain with the archive.

 10) EXTREMELY IMPORTANT:  If (for any reason) you wake up one morning with a
     strong feeling that the BFDS enterprise is not for you, and you decide to
     drop out you have only one duty: LET YOUR UP-LINK (and myself) know that
     you are leaving. If you don't feed any down-links you can terminate
     immediately after receiving "sorry to see  you go" message from your
     up-link.  If you ARE feeding even a single down-link, you would have to
     stay in the game for the time it will take to arrange an alternate hookup
     for your down-link(s).  Usually it will take about a week.

 11) You are joining a "system-in-progress" - this means that there already are
     numerous files in BFDS.  It is highly recommended that you Freq or DFreq
     the files from your up-link node so you are up-to-date with what is
     available.  Please contact your up-link node for file-names or watch for a
     periodic announcement in BFDS_MAIL. 

 12) Please make the BFDS_KIT available for file requests on your board.  When
     changes are made to the information contained in the archive it will be
     hatched into the BFDS using the Replace option.  It is recommended that
     the archive format for this file not be changed.

That about sums it up.  If you have any questions you may contact me via Netmail
at 1:141/1135 at 1:141/1136.

-><-Dennis Powers
    BFDS Coordinator