From: "Mateusz Łoskot" <m.loskot@chello.pl>
To: linux-kernel@vger.kernel.org
Cc: Mateusz ?oskot <m.loskot@chello.pl>, ftpadmin@kernel.org
Subject: Re: Strange problem with 2.4.x kernel
Date: Sat, 8 Dec 2001 00:11:13 +0100 [thread overview]
Message-ID: <20011208001113.C4239@cheetah.chello.pl> (raw)
In-Reply-To: <20011206190454.B848@cheetah.chello.pl> <20011206123342.42179ed3.reynolds@redhat.com> <20011206194151.D848@cheetah.chello.pl> <20011207222457.A939@go.cz>
In-Reply-To: <20011207222457.A939@go.cz>; from johnydog@go.cz on Fri, Dec 07, 2001 at 10:24:58PM +0100
> What is your line speed ?
I have CABLE MODEM connection and I have aout 40 kbps speed from ftp.krenel.org
I think it is not so slow ;-))), I get linux kernel archive in 10 minutes ;)
> 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 ?
I tried download from different places. So, it doesn't work.
As I said before in my posts, I suspect my RAM SIMM's (thanks to kernel hackers which gave me a lot of help)
So, I have to test it and I will know whats going wrong.
> To ftpadmin@kernel.org:
> Could you please check ? Thanks.
I think that this is problem with BIG tar.gz files, because if I try to ungzip
kernel 2.2.19 everything goes fine, so it must be a hardware problem.
Thanks a lot for your help
--
Mateusz Łoskot
E-mail: m.loskot@chello.pl
GG#: 792434
prev parent reply other threads:[~2001-12-07 23: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
2001-12-07 23:11 ` Mateusz Łoskot [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=20011208001113.C4239@cheetah.chello.pl \
--to=m.loskot@chello.pl \
--cc=ftpadmin@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.