From: Michael Pakovic <mpakovic@fdn.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 2.4.4 fork.c changes cause linuxconf to fail
Date: Sun, 29 Apr 2001 11:27:18 -0400 [thread overview]
Message-ID: <3AEC32D6.EC179FCB@fdn.com> (raw)
The changes to kernel/fork.c from 2.4.4-pre1 to 2.4.4-pre3 (and in
2.4.4) cause the RedHat 6.2 linuxconf utility to fail with the message
"broken pipe". The linuxconf utility will run the first time, but all
subsequent runs give the "broken pipe" error. The error message is
generated as a result of a fflush command in linuxconf. I can provide
more information upon request.
Mike Pakovic
next reply other threads:[~2001-04-29 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-29 15:27 Michael Pakovic [this message]
2001-04-29 15:40 ` 2.4.4 fork.c changes cause linuxconf to fail Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2001-04-30 8:00 Adam J. Richter
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=3AEC32D6.EC179FCB@fdn.com \
--to=mpakovic@fdn.com \
--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