9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] 2 newbe questions of a general nature
Date: Thu,  5 Apr 2007 11:13:00 -0400	[thread overview]
Message-ID: <ee9e417a0704050813x36ef7c83qcf35440cce83a5cb@mail.gmail.com> (raw)
In-Reply-To: <5d375e920704042029o3c001e41r1f37c745f734939c@mail.gmail.com>

> Would be nice if the BL overlords could avoid this, maybe by moving
> the previous day ISO before the new one takes its place, similar to
> how replica moves foo to _foo.

It already does that (maybe the overlords aren't as dumb as you think).
But if the HTTP download gets interrupted after a new file has been
dropped in its place, a client retrying the HTTP request will see
the new file.  If your download is not interrupted, then it will get
a consistent file.

Even if you are getting interrupted, the CD is at most 100MB
compressed, which is only 5 hours at 56kbps, so you've got plenty
of time to grab it in the 24-hour window.

Further, I doubt very much that this is the cause of people with
broken ISO images.  You can't get that far if you get half of one
download and half of another.  They're compressed, and the checksum
will fail during decompression even if the web browser doesn't notice
that the file changed in the second request.  So you'd end up with a
broken .bz2 file, not a broken image.  If you ever get to a .iso file,
it will be intact.

Russ


  reply	other threads:[~2007-04-05 15:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-04  9:14 vlholmesjr
2007-04-04 12:42 ` erik quanstrom
2007-04-05  3:29   ` Uriel
2007-04-05 15:13     ` Russ Cox [this message]
2007-04-05 16:08       ` erik quanstrom
2007-04-06 13:26         ` Laurent Malvert
2007-07-05 14:01           ` Harri Haataja
2007-04-05 16:19       ` Uriel

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=ee9e417a0704050813x36ef7c83qcf35440cce83a5cb@mail.gmail.com \
    --to=rsc@swtch.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).