Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pasteur!ucbvax!tut.cis.ohio-state.edu!osu-cis!att!cbnews!djz
From: djz@cbnews.ATT.COM (Danny Zerkel)
Newsgroups: comp.sources.d
Subject: Re: "Archive-name:" proposed change
Summary: An opinion on archive naming
Keywords: multiple part postings
Message-ID: <5337@cbnews.ATT.COM>
Date: 3 Apr 89 14:28:49 GMT
References: <780@usl.usl.edu> <2464@ndsuvax.UUCP> <1187@ncr-sd.SanDiego.NCR.COM> <97030@sun.Eng.Sun.COM>
Reply-To: djz@cbnews.ATT.COM (Danny Zerkel)
Organization: AT&T Bell Laboratories
Lines: 82

In article <97030@sun.Eng.Sun.COM> page@sun.UUCP (Bob Page) writes:
>I'm not a fan of the 'part X of Y' stuff in the archive name because
>moderators tend to miscount.  Even so, I do it in the subject line.
...
>greg@ncr-sd.SanDiego.NCR.COM (Greg Noel) proposed something like:
>>Archive-name: fun/hangman/V01r01-src/Part01of03
>
>The problem with this is the sites that use things like tar and cpio
>to store the entire collection of a posting.  I've had a couple of
>requests to limit my archive names to seven unique characters,
>so folks could archive the postings as 'pgmname.CPIO.Z' and
>still fit in 14 characters (the current SystemV limit).  I'm not
>sure how the above proposed archive-name would work for those sites.
>
>..bob
>Bob Page    page@sun.com    sun!page    415/336-2745

I've been doing my best to archive the sources from comp.sources.unix,
comp.sources.games, comp.sources.x, comp.sources.misc, and alt.sources.
I tried comp.binaries.ibm.*, but being unfamiliar with there contents
I was unsure what would be an useful name scheme.

For the comp.sources.* stuff, I use the following method:

Use regular expressions to search the first 2048 bytes of the article--
looking for lines like:

  Archive-name: fred/Part02
  Archive-name: fred/Patch01
  Archive-name: fred-killer

Parts are then stored thusly:
fred.02

Usually in a directory reflecting its original group, such as:
unix/fred.02

Patches have the following appearance:
unix/fred.p01

And single part postings are given the number 00:
unix/fred-kille.00

Notice the limit on name length is 10, which leaves 4 characters for
part separation.  These parts and patches are then lumped together in
and zoo archive:
unix/fred.zoo
unix/fred-kille.zoo

I have only recently started using zoo, before I was using cpio and compress
and calling the arhive: fred.ZZ.  But these are difficult to deal with.
Zoo seems to work well and the automatic compression is nice, but it acts
a bit twitchy about implied .zoo extensions on archives.  So I've taken to
typing the .zoo at all times.

This system easily expands to handle fixes: .f?? (usually the number is
selected by me at random), repostings .r??, and other miscellaneous bits
which I have seen.  The only problem with the fixes stuff is that I can
never remember the original archive name for a fix article like:

>
>Wow dudes!  I kept getting core dumps in "Bogus Rouges from Space"
>until I figured out this fix:
>
>  o.main.c: 66327
>       printf("Narley!");
>  main.c: 66327
>	printf("Fer sure!");
>

So if some standardized method of naming and archiving is developed, I'm
very interested in extending it to fixes of an unoffical nature.  Of course,
anything would help in alt.sources (ie, "Subject: Bit Shuffler PART 1 of 83").

I currently pipe whole newsgroups into my archiving program, and end up
adding more expressions every time it burps and saves parts 1 through 83
as funky/bitshuff.00.

****************************************************************************
Danny J. Zerkel
AT&T Bell Labs
Maloderous-Cow-Town-USA, OH