mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick LeRoy <nleroy@cs.wisc.edu>
To: Pierre Rousselet <pierre.rousselet@wanadoo.fr>
Cc: Ricardo Martins <thecrown@softhome.net>, 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, 1 Nov 2001 14:06:54 -0600	[thread overview]
Message-ID: <200111012007.fA1K7AG10327@schroeder.cs.wisc.edu> (raw)
In-Reply-To: <3BE1777F.30705@softhome.net> <200111011945.fA1Jj0G09069@schroeder.cs.wisc.edu> <3BE1A9D5.3000508@wanadoo.fr>
In-Reply-To: <3BE1A9D5.3000508@wanadoo.fr>

On Thursday 01 November 2001 14:00, Pierre Rousselet wrote:
> Nick LeRoy wrote:
> > On Thursday 01 November 2001 13:31, Pierre Rousselet wrote:
> >>Ricardo Martins wrote:
> >>> >> Procedure
> >>> >> In X windows (version 4.1.0 compiled from the sources) when writing
> >>> >> "exit" in xterm to close the terminal emulator, the window freezes,
> >>> >> and from that moment on, every process becomes "unkillable",
> >>> >> including
> >>>
> >>>xterm
> >>>
> >>> >> and X (ps also freezes), and there's no way to shutdown GNU/Linux in
> >>> >> a sane way (must hit reset or poweroff).
> >>> >
> >>> >I can see the problem here with 2.4.13. I don't know if it's kernel
> >>> >related, I'm used using rxvt, never xterm.
> >>> >
> >>> >It looks like xterm takes the terminal where you started X from.
> >>> >
> >>> >Are you using devfs ?
> >>> >
> >>> >
> >>> >Pierre
> >>>
> >>>Pierre, yes, i'm using devfs that seems to be the problem, do you know
> >>>how to fix it ?
> >>
> >>Is it devfs or xterm which needs to be fixed ? I would
> >>
> >>suggest to switch to rxvt which works fine with/without devfs.
> >
> > With all due respect, I'd have to differ.....  Do you have any idea how
> > many people are running how many copies of xterm as we speak?  Even if we
> > pair that down to all those running devfs, it's certainly a substantial
> > number. The kernel should, above all else, run old applications without
> > breaking them.
> >
> > -Nick
>
> devfs is still marked EXPERIMENTAL in the kernel building. If you select it
> you
>
> must be prepared to tolerate some misbehaviour. rxvt is not newer than
> xterm, it is lighter.

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.

-Nick

  reply	other threads:[~2001-11-01 20:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-01 16:25 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 [this message]
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-02  3:41                 ` David Ford
2001-11-01 20:42               ` Brian Gerst
2001-11-01 21:34               ` Richard Gooch
2001-11-09  1:17           ` Dr. Kelsey Hudson
2001-11-01 19:47   ` Ricardo Martins
2001-11-01 19:58     ` Per Lidén
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=200111012007.fA1K7AG10327@schroeder.cs.wisc.edu \
    --to=nleroy@cs.wisc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre.rousselet@wanadoo.fr \
    --cc=thecrown@softhome.net \
    /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®