From: Chris Wedgwood <cw@f00f.org>
To: Blaisorblade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [uml-devel] [PATCH] uml: fail xterm_open when we have no $DISPLAY
Date: Mon, 15 Nov 2004 22:41:51 -0800 [thread overview]
Message-ID: <20041116064151.GB22588@taniwha.stupidest.org> (raw)
In-Reply-To: <200411151824.29365.blaisorblade_spam@yahoo.it>
On Mon, Nov 15, 2004 at 06:24:29PM +0100, Blaisorblade wrote:
> Thanks for drawing attention on this! I hadn't had the time to dig
> this out... for now reasonably correct
it's a partial solution, in general more is required
> but no time to review it properly now. The review would probably try
> to find a more direct fix to this...
catch the xterm process dying, up(&data->sem), and -EIO all requests
from that point onwards I guess. That applies for some of the other
channels too, some of the code would probably be abstracted a little
and generalized I guess.
--cw
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-11-16 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 3:25 [uml-devel] [PATCH] uml: fail xterm_open when we have no $DISPLAY Chris Wedgwood
2004-11-15 17:24 ` Blaisorblade
2004-11-16 6:41 ` Chris Wedgwood [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=20041116064151.GB22588@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.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