From: Brian Gerst <bgerst@didntduck.org>
To: Nick LeRoy <nleroy@cs.wisc.edu>
Cc: "Jeffrey W. Baker" <jwbaker@acm.org>, linux-kernel@vger.kernel.org
Subject: Re: on exit xterm totally wrecks linux 2.4.11 to 2.4.14-pre6 (unkillable processes)
Date: Thu, 01 Nov 2001 15:42:45 -0500 [thread overview]
Message-ID: <3BE1B3C5.E3D630D9@didntduck.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0111011212220.27747-100000@windmill.gghcwest.com> <200111012035.fA1KZMG11816@schroeder.cs.wisc.edu>
Nick LeRoy wrote:
>
> On Thursday 01 November 2001 14:13, you wrote:
> > On Thu, 1 Nov 2001, Nick LeRoy wrote:
> > > Marked experiment, for now. What about when it's no longer
> > > "experimental"? Configuring a kernel to enable such a feature should
> > > *not* break applications, especially something as prolific as xterm.
> >
> > Are you sure you know what you are talking about? Devfs causes this
> > problem because of a defect, not by design. It is marked experimental
> > because it's loaded with such defects. Don't use it until the
> > experimental tag is removed, if you are not prepared for some malfunction.
>
> Yeah, I think that I know what I'm talking about. The question was: Should
> devfs be fixed, or should xterm be fixed. I don't know how serious it is, or
> exactly what the nature of the problem is (haven't followed the thread that
> closely), but, from the "mile high" point of view, this defect, be it design
> or just a one-line bug, needs to be fixed before it can be tagged
> "non-experimental". I don't understand why people would think otherwise, to
> be honest.
Fix devfs. If the kernel lets a user program crash it, it's a kernel
bug.
--
Brian Gerst
next prev parent reply other threads:[~2001-11-01 20:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-01 16:25 on exit xterm totally wrecks linux 2.4.11 to 2.4.14-pre6 (unkillable processes) Ricardo Martins
2001-11-01 19:05 ` Pierre Rousselet
2001-11-01 19:19 ` Ricardo Martins
2001-11-01 19:31 ` Pierre Rousselet
2001-11-01 19:44 ` Nick LeRoy
2001-11-01 20:00 ` Pierre Rousselet
2001-11-01 20:06 ` Nick LeRoy
2001-11-01 20:13 ` Jeffrey W. Baker
2001-11-01 20:35 ` Nick LeRoy
2001-11-01 20:40 ` Rik van Riel
2001-11-01 21:34 ` Richard Gooch
2001-11-02 3:41 ` David Ford
2001-11-01 20:42 ` Brian Gerst [this message]
2001-11-09 1:17 ` Dr. Kelsey Hudson
2001-11-01 19:47 ` Ricardo Martins
2001-11-01 19:58 ` Per Lidén
-- strict thread matches above, loose matches on Subject: below --
2001-11-02 6:16 Chris Rankin
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=3BE1B3C5.E3D630D9@didntduck.org \
--to=bgerst@didntduck.org \
--cc=jwbaker@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nleroy@cs.wisc.edu \
/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