From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Mark Lord <lkml@rtr.ca>
Cc: David Miller <davem@davemloft.net>,
jheffner@psc.edu, torvalds@osdl.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.17: networking bug??
Date: Mon, 19 Jun 2006 09:07:02 +0200 [thread overview]
Message-ID: <44964D16.6060206@aitel.hist.no> (raw)
In-Reply-To: <448F32E1.8080002@rtr.ca>
Mark Lord wrote:
>
> Unilaterally following the standard is all well and good
> for those who know how to get around it when a site becomes
> inaccessible, but not for Joe User.
>
So lets enable it in the kernel, and let the distros turn it off.
The Joe User who isn't a kernel hacker won't be running 2.6.17
in a long time. He'll be running whatever his distro packages for him,
and they will know how to disable (or patch out) window scaling.
Someone who compiles his own kernel runs into all sorts of
issues, this is just one more of them.
> If it always fails, or always works, that's not such a big problem.
> I would never have complained if I had never been able to access
> the web sites in question. But since it IS working in 2.6.16,
> and got broken in 2.6.17, I'm bloody well going to complain.
Yes. And make sure you complain to those running the bad
box as well.
Helge Hafting
next prev parent reply other threads:[~2006-06-19 7:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <448EC6F3.3060002@rtr.ca>
[not found] ` <448ECB09.3010308@rtr.ca>
2006-06-13 15:00 ` 2.6.17: networking bug?? Mark Lord
2006-06-13 15:28 ` Mark Lord
2006-06-13 16:58 ` Mark Lord
2006-06-13 17:22 ` Mark Lord
2006-06-13 17:39 ` John Heffner
2006-06-13 17:50 ` Linus Torvalds
2006-06-13 18:26 ` Mark Lord
2006-06-13 19:08 ` Mark Lord
2006-06-13 21:26 ` David Miller
2006-06-13 21:49 ` Mark Lord
2006-06-13 22:12 ` Rick Jones
2006-06-13 22:23 ` David Miller
2006-06-13 22:40 ` Rick Jones
2006-06-13 23:01 ` David Miller
2006-06-14 1:25 ` John Heffner
2006-06-13 23:22 ` Matt Mackall
2006-06-19 7:07 ` Helge Hafting [this message]
2006-06-14 5:18 ` Andi Kleen
2006-06-14 8:09 ` Daniel Drake
2006-06-13 18:28 ` John Heffner
2006-06-13 20:45 ` Barry K. Nathan
2006-06-13 22:09 ` Chase Venters
2006-06-13 22:23 ` David Miller
2006-07-02 17:39 ` Jan Knutar
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=44964D16.6060206@aitel.hist.no \
--to=helge.hafting@aitel.hist.no \
--cc=davem@davemloft.net \
--cc=jheffner@psc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=netdev@vger.kernel.org \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).