From: greg@squally.halcyon.com (Greg Naber)
Newsgroups: comp.os.linux,alt.os.linux
Subject: Fidonet Distribution
Date: 12 Apr 92 20:01:44 GMT
Reply-To: greg@squally.halcyon.com (Greg Naber)
Organization: S'Qually Holler's, Renton WA

Well I really put my foot in it this time;-)

I have been assigned/cajoled/volunteered to get this stuf distributed in
the Fidonet land. I do have the backing of SOME of the fidonet filemover
backbone structure to accomplish this.

What I am looking for is comments to the following text file before
setting up the distribution scheme. (Also more volunteers with dual
identities to help out;-)

This file is in fidonet jargon.
Please help me pick this apart, any comments appriciated.


Linux Distribution Network Policy Document For Fidonet - Rev 1 - 12 April 1992
Greg Naber
1:343/34@fidonet.org or greg@squally.halcyon.com


      Area Name        Area Description
      =========        ================

      LNXSYS           LNX - System Files Distribution.
                       contains: Linux system files, source,
                                 system updates, drivers,
                                 patches & modifications,
                                 release notes, installation
                                 instructions and boot/root images.

      LNXCOMP          LNX - Complier Files Distribution.
                       contains: complier related materials, i.e.
                                 GCC-* source code, binaries, libraries,
                                 and related installation instrutions.

      LNXDOC           LNX - Documentation Files Distribution.
                       contains: Manual (man pages) documentation,
                                 for all areas. Update documentation
                                 to all areas. Installation Instuctions.
                                 Misc. documentation.

      LNXUTIL          LNX - Utilities File Distribution.
                       contains: All Linux related binary format
                                 utilities and updates.

      LNXGAME          LNX - Games File Distribution.
                       contains: All Linux related binary format games.

      LNXSOURC         LNX - Source Code Distribution.
                       contains: All source code for utilities and games.

      LNXMISC          LNX - Miscellaneous Linux Related files.
                       contains: Any Linux related files not covered
                                 by other file areas.

       LNXUNIX         LNX - Unix Related Files Distribution.
                       contains: Any files related to unix and MAY NOT be
                                 related to Linux.

1. I would like to not see "CrippleWare" or "VaporWare" included.  Only Public
Domain and ShareWare should be submitted. Demonstration software submitted will
be allowed only if the software is able to be used in some fashion that will
enable the end user to "Try before you buy". One thing to keep in mind is that
Linux itself and GCC is 'freeware'.

2.      Due to the unix abilities to have numerous characters in the naming of
files and dos's limitation of 8 character with 3 character extension names, it
would be impracticable to allow any node to hatch files into the LNX areas.
Hatching will be restricted to LNX RC's. This will control the possible hatch-
ing of duplicate files under different names.

3a.     The common compression utility used will be unix format to make
transfers between Dos and Unix easier for beginning systems to transfer files
between the two. The common naming of files will reflect this in the extension
of the file name. I.E. An extension of .Z will mean unix's compress program has
been used to compress the file. An extension of .TZ will mean the file is
'tarred' and compressed under unix.

3b.     Occasionally files may be 'split' to reduced the overall size of a file
for transfer. In this case the file name will be <filename>.001, <filename>.002,
etc. It is to be assumed that these files will be compressed, they may also be
'tarred'. A corrisponding ascii text file should be included to discribe the
split file, <filename.lnx>.

3c.     The text file <filename>.txt may also be used to describe a file and
it's related/asscociated, documentation/source/binary files located in other
areas.

3d.     The corrisponding Dos utilities to manage these files will be made
available.

3e.     Other compression programs common to Dos will be allowed for Ascii
files for the purpose of compression of related materials for transmittal,
and viewing on Dos based systems. Although all formats are supported by Unix
keep in mind that the utilities ARE NOT distributed on the original Linux
disks, and as such should not be used often.

4.      There will be an Echo set up between all the the LNXNRC's called
LNXRCECHO.  This Echo is strictly for the use of the PDNRC's in each Zone, and
for nodes that are a gateway to another Zone.  Normal downstream nodes should
not have access to this echo.

5.      There will be another Echo set up between all the the LNX nodes called
LNXMANAGE.  This Echo is for the use of the LNX nodes in each Zone, and for
nodes that are a gateway to another Zone. Users should not be allowed access
to this area. This area is not mandatory, but suggested.

6.      There will be another Echo set up for all the nodes picking up files
from the LNXRC's called LNXECHO. This Echo is for the users of individual
BBS's so those users of files that are sent through the LNX can have a
medium that is appropriate to discuss the installation of Linux and it's
related files. This area is not mandatory, but suggested.

7.      ALL LNX nodes will have session-level passwords with each other. This
is simply to ensure the integrity of the LNX.

8.      ANY file that comes to your system via the LNX should have the CRC
checked by TICK as it is processed.  No archive advertisments should be placed
into the archive while the file is still being sent to another LNX node.  This
idea is not meant to advertise a BBS, but to move files.  This also corrupts
the CRC info, and it will cause TICK to bomb out on the CRC check.  Nodes
should not re-archive the file until that node is sure ALL the downstream
nodes have it.  Please pay attention to authors wishes when re-packing files.

9.      The LNX is free, and should always be just that.  However, sometimes
it costs money to move these files, so there is no problem with asking LOCAL
downstream nodes to help pay for the phone call when picking up the LNX.  The
LNX should be allowed to travel as far and to as many nodes as possible.

10.     Any changes/additions to this policy should be coordinated with the
International LNX Coordinator, Greg Naber at 1:260/230@fidonet.org alternate
address is greg@squally.halcyon.com for those with Internet/UUCP access.



Catch Ya Later!

Greg
---
        S'Qually Holler's BBS Renton, Wa. 1-206-235-0270 USR HST D/S
                         1:343/34@fidonet.org
                         squally.halcyon.com
Newsgroups: comp.os.linux