Re: how to ftp doc

Bob Peterson <peterson@choctaw.csc.ti.com> Mon, 07 June 1993 21:56 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05994; 7 Jun 93 17:56 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa05990; 7 Jun 93 17:56 EDT
Received: from mocha.bunyip.com by CNRI.Reston.VA.US id aa17809; 7 Jun 93 17:56 EDT
Received: by mocha.bunyip.com (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA26137 on Mon, 7 Jun 93 16:43:17 -0400
Received: from ti.com by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA26133 (mail destined for /usr/lib/sendmail -odq -oi -fiafa-request iafa-out) on Mon, 7 Jun 93 16:43:03 -0400
Received: from tilde.csc.ti.com ([128.247.160.56]) by ti.com with SMTP (5.65c/LAI-3.2) id AA24437; Mon, 7 Jun 1993 15:47:20 -0500
Received: from choctaw.csc.ti.com (choctaw) by tilde.csc.ti.com id AA03067; Mon, 7 Jun 1993 15:42:07 -0500
Received: by choctaw.csc.ti.com (4.1/SMI-4.1) id AA01793; Mon, 7 Jun 93 15:42:07 CDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Bob Peterson <peterson@choctaw.csc.ti.com>
Message-Id: <9306072042.AA01793@choctaw.csc.ti.com>
Subject: Re: how to ftp doc
To: April Marine <amarine@atlas.arc.nasa.gov>
Date: Mon, 7 Jun 93 15:42:06 CDT
Cc: iafa@bunyip.com
In-Reply-To: <9306062150.AA25054@mocha.bunyip.com>; from "April Marine" at Jun 6, 93 2:50 pm
Reply-To: peterson@csc.ti.com
Mime-Version: 1.0
X-Mailer: ELM [version 2.3 PL11]

April Marine said:

> Hi all.  Hope this mailing list still works as I am now vague on
> which group is responsible for the how to ftp doc we were working on.
> I apologize for the delay in getting it out.  I had a lag while I
> looked for work.
>	...
> thanks,
> April
>	...
> On many systems, various file naming conventions are used to help the
> remote user to determine the format of the stored information without
> first having to retrieve the files.  Below we list the more common
> compression, bundling, and transformation conventions used on the
> Internet.  This list is not intended to be exhaustive.  In all cases
> public domain or freely-available implementations of the programs
> associated with these mechanisms are available on the
> network.
> 
>   6) zip/unzip
> 
>   Often used in IBM PC environments, these complementary programs
>   provide both bundling and compression mechanisms.  The resulting
>   files are always in binary format.  Files resulting from the "zip"
>   program are by convention terminated with the ".zip" filename
>   extension.

  6a) gzip/gunzip

  The GNU project adopted a variant of the zip compression mechanism as a
  substitute for the compress/uncompress commands.  Unlike zip/unzip,
  these complementary programs provide only compression.  The resulting
  files are always in binary format.  Files resulting from the "gzip"
  program are by convention terminated with the ".z" or ".gz" filename
  extensions. The gunzip program also recognizes ".tgz" and ".taz" as
  shorthands for ".tar.z" or ".tar.Z".  Also, gunzip can recognize and
  decompress files created by the gzip, zip, compress, or pack commands.

  The GNU project recently began distributing and using the gzip/gunzip
utilities.  Even more recently they changed the default suffix from .z
to .gz, in an attempt to (1) reduce confusion with .Z, and (2) eliminate
a problem with case-insensitive file systems such as MS-DOS.

  Other than the above, rather late, addition, the document looks quite good.

-- 
Bob Peterson             Work: peterson@csc.ti.com              Expressway Site
Texas Instruments        Home: peterson@zgnews.lonestar.org     North Building
P.O. Box 655474, MS238   TIMSG: RWP  Landline: +1 214 995 6080  Aisle A4
Dallas, Tx USA 75265                 FAX line: +1 214 995 0304  2-88V97