From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] iso?
Date: Sun, 16 Feb 2003 13:16:12 -0500 [thread overview]
Message-ID: <23e62cd91cc5d0cdfd8d09cfd98219bd@plan9.bell-labs.com> (raw)
In-Reply-To: <200302161746.h1GHkYM13009@augusta.math.psu.edu>
The main reason they're bzipped is that they used
to be available only via the web page, and compression
is a no-brainer then.
Given the latency of most connections to sources,
my guess is that you get an enormous saving in time
by downloading it compressed and then dealing with
a local file system. But maybe not.
In any case, there should be a script to do an install
for you.
Russ
prev parent reply other threads:[~2003-02-16 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-16 17:03 Sam
2003-02-16 17:22 ` Dan Cross
2003-02-16 17:38 ` Sam
2003-02-16 17:46 ` Dan Cross
2003-02-16 18:16 ` Russ Cox [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23e62cd91cc5d0cdfd8d09cfd98219bd@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).