From: Jeff Dike <jdike@karaya.com>
To: root@chaos.analogic.com
To: lists@corewars.org, Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Bad Network SIGIO on Linux-2.4.19
Date: Wed, 21 Aug 2002 11:06:27 -0400 [thread overview]
Message-ID: <200208211506.g7LF6RQ02046@karaya.com> (raw)
In-Reply-To: Your message of "Wed, 21 Aug 2002 10:36:13 EDT." <Pine.LNX.3.95.1020821103155.31858B-100000@chaos.analogic.com>
root@chaos.analogic.com said:
> Well if this is a 'fix' there is a lot of legacy software that just
> got broken. It was discovered when the new kernel was booted on some
> very reliable file-servers.
Then your "very reliable" file-servers are broken and need fixing so they
no longer depend on this bug.
Jeff
prev parent reply other threads:[~2002-08-21 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-16 19:27 Richard B. Johnson
2002-08-21 14:24 ` lists
2002-08-21 14:36 ` Richard B. Johnson
2002-08-21 15:06 ` Jeff Dike [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=200208211506.g7LF6RQ02046@karaya.com \
--to=jdike@karaya.com \
--cc=root@chaos.analogic.com \
/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
all inboxes | Powered by JetHome®