From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Dvorak <johnydog@go.cz>
Cc: Mateusz ?oskot <m.loskot@chello.pl>,
linux-kernel@vger.kernel.org, ftpadmin@kernel.org
Subject: Re: Strange problem with 2.4.x kernel
Date: Fri, 07 Dec 2001 14:10:53 -0800 [thread overview]
Message-ID: <3C113E6D.2030504@zytor.com> (raw)
In-Reply-To: <20011206190454.B848@cheetah.chello.pl> <20011206123342.42179ed3.reynolds@redhat.com> <20011206194151.D848@cheetah.chello.pl> <20011207222457.A939@go.cz>
Jan Dvorak wrote:
> (CCing to ftpadmin@kernel.org)
>
> On Thu, Dec 06, 2001 at 07:41:51PM +0100, Mateusz ?oskot wrote:
>
>>Dni 06.12 2001 r., o godzinie 12:33 Tommy Reynolds napisa?(a) co nast?puje:
>>
> ..
>
>>>Use ftp(1) or wget(1) to do the downloads. Do _not_ try to get the files using
>>>any web browser, such as Netscape, because they are known to mangle files that
>>>they don't understand.
>>>
>>I know, I used only ftp, ncftp or yafc - the same result ;-((((
>>
>>Thanks
>>
>
> What is your line speed ? ProFTPD 1.2.0rcX and 1.2.2rcX (and probably other
> versions) corrupts data on slow links (e.g modem) when compiled with
> --enable-sendfile option (default). Could you try downloading on fast link,
> or from mirrors ?
>
> To ftpadmin@kernel.org:
> Could you please check ? Thanks.
>
We're currently running ProFTPD 1.2.2 final (with sendfile enabled.)
We're planning a full server replacement before the end of the month, at
which time we'll probably replace it with vsftpd.
-hpa
next prev parent reply other threads:[~2001-12-07 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 18:04 Strange problem with 2.4.x kernel Mateusz Łoskot
2001-12-06 18:30 ` Hans-Georg Fischer
2001-12-06 18:52 ` Mateusz Łoskot
2001-12-06 18:33 ` Tommy Reynolds
2001-12-06 18:41 ` Mateusz Łoskot
2001-12-07 21:24 ` Jan Dvorak
2001-12-07 22:10 ` H. Peter Anvin [this message]
2001-12-07 23:11 ` Mateusz Łoskot
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=3C113E6D.2030504@zytor.com \
--to=hpa@zytor.com \
--cc=ftpadmin@kernel.org \
--cc=johnydog@go.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=m.loskot@chello.pl \
/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