From: "H. Peter Anvin" <hpa@transmeta.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Diego Calleja <DiegoCG@teleline.es>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.18rc4aa1
Date: Mon, 25 Feb 2002 06:41:35 -0800 [thread overview]
Message-ID: <3C7A4D1F.9080600@transmeta.com> (raw)
In-Reply-To: <20020224165531.A14179@dualathlon.random> <20020224222531.04f44502.DiegoCG@teleline.es> <20020225135052.F3137@inspiron.suse.de>
Andrea Arcangeli wrote:
> On Sun, Feb 24, 2002 at 10:25:31PM +0100, Diego Calleja wrote:
>
>>On Sun, 24 Feb 2002 16:55:31 +0100
>>Andrea Arcangeli <andrea@suse.de> wrote:
>>
>>
>>>URL:
>>>
>>> ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.18rc4aa1.gz
>>> ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.18rc4aa1/
>>>
>>
>>Andrea, I think there's an error on compressed files.
>>-2 times downloaded .gz file(1'3 MB?)= unexpected end of file
>>-1 time downloaded .bz2 file: Compressed file ends unexpectedly
>>
>
> I guess one mirror gone wild, CC'ed to Peter just in case he knows. (I
> upload to the staging area, and then an atomic move will make the inode
> visible in /pub, so it shouldn't a problem triggered during the upload
> stage and a wget on the above url worked for me infact)
>
> (ah, an of course remeber to use binary ftp download :)
>
Without the IP number of the offending mirror, there is little or no
hope to track down the problem, if there is one.
-hpa
next prev parent reply other threads:[~2002-02-25 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-24 15:55 2.4.18rc4aa1 Andrea Arcangeli
2002-02-24 21:25 ` 2.4.18rc4aa1 Diego Calleja
2002-02-24 20:34 ` 2.4.18rc4aa1 Eric Krout
2002-02-24 21:28 ` 2.4.18rc4aa1 Allan Sandfeld
2002-02-24 23:08 ` 2.4.18rc4aa1 Diego Calleja
2002-02-25 12:50 ` 2.4.18rc4aa1 Andrea Arcangeli
2002-02-25 14:41 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-24 21:29 2.4.18rc4aa1 rwhron
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=3C7A4D1F.9080600@transmeta.com \
--to=hpa@transmeta.com \
--cc=DiegoCG@teleline.es \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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