public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: gene.heskett@verizon.net
Cc: linux-kernel@vger.kernel.org,
	Clemens Schwaighofer <cs@tequila.co.jp>,
	"Markus T." <markus@trippelsdorf.net>
Subject: Re: Linux 2.6.9-rc3
Date: Thu, 30 Sep 2004 17:55:13 -0400	[thread overview]
Message-ID: <415C80C1.8070406@pobox.com> (raw)
In-Reply-To: <200409301627.20548.gene.heskett@verizon.net>

Gene Heskett wrote:
> bz2 has resulted in corrupted unpacks here on more than one occasion, 
> and it has done it without any outwardly visible error when the 
> md5sum was good.  I've had it skip a whole subdir tree in a kernel 
> unpack on at least 4 occasions, and a missing file someplace on 
> several more occasions.  I don't have any such troubles when dl'ing 
> and using the .gz version of things.
> 
> There has been at least one occasion where the .bz2 dl had a bad 
> md5sum, again without any visible error as it was downloading, nuke 
> it and go back and get the same file again and it was good.  Again 
> I've had no such troubles when using the .gz versions, so after a a 
> while, I got into the habit of just gettng the .gz version and I've 
> never had an instance of a bad md5sum that wasn't accompanied by site 
> access problems.


There's definitely something else going on.  I don't see how you can 
blame bz2 for downloading problems.  If this were true we would see a 
_lot_ more problem reports than just one in >5 years.

	Jeff



  reply	other threads:[~2004-09-30 21:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30  3:37 Linux 2.6.9-rc3 Linus Torvalds
2004-09-30  4:53 ` Markus T.
2004-09-30  4:59   ` Tom Duffy
2004-09-30  5:02   ` Gene Heskett
2004-09-30  6:29     ` Clemens Schwaighofer
2004-09-30  7:30       ` James Bruce
2004-09-30  7:33         ` Clemens Schwaighofer
2004-09-30 15:53         ` Ingo Saitz
2004-09-30 20:27       ` Gene Heskett
2004-09-30 21:55         ` Jeff Garzik [this message]
2004-10-01  0:42           ` Clemens Schwaighofer
2004-10-01  3:30             ` Gene Heskett
2004-10-01  3:34               ` Clemens Schwaighofer
2004-10-01  4:01                 ` Gene Heskett
2004-10-01  4:05                   ` Clemens Schwaighofer
2004-10-01  4:06                 ` Gene Heskett
2004-10-01  3:17           ` Gene Heskett
2004-10-01  5:44             ` Christian Hesse
2004-09-30 18:58     ` Bill Davidsen
2004-09-30 20:32       ` Gene Heskett
2004-09-30  5:03 ` Tom Duffy
2004-09-30  5:14   ` Marcel Holtmann
2004-09-30  5:33     ` Tom Duffy
2004-09-30  5:20   ` Gene Heskett
2004-09-30  5:24     ` Marcel Holtmann
2004-09-30 20:41       ` Gene Heskett
2004-09-30 14:13 ` Linux 2.6.9-rc3 (compile stats) John Cherry
2004-09-30 19:03 ` Linux 2.6.9-rc3 Bill Davidsen
2004-10-01 13:49 ` [PATCH] tty fall-out (was: Re: Linux 2.6.9-rc3) Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2004-09-30 15:38 Linux 2.6.9-rc3 Tim Krieglstein
     [not found] <2K07b-1Ez-3@gated-at.bofh.it>
     [not found] ` <2Kh8e-5H2-23@gated-at.bofh.it>
     [not found]   ` <2KjMz-6E6-17@gated-at.bofh.it>
     [not found]     ` <2Kmr3-9n-1@gated-at.bofh.it>
2004-10-01 12:36       ` Pascal Schmidt

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=415C80C1.8070406@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=cs@tequila.co.jp \
    --cc=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.net \
    /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