From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: Multio deadlock (Re: multios doesn't work with 2>&1)
Date: Sun, 27 Oct 2013 21:16:27 +0000 [thread overview]
Message-ID: <20131027211627.79b05e20@pws-pc.ntlworld.com> (raw)
In-Reply-To: <20131027203347.15be6bc2@pws-pc.ntlworld.com>
On Sun, 27 Oct 2013 20:33:47 +0000
Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
> Hmm... why don't we initialise fdtable[0..2] to FDT_INTERNAL at boot?
Er, because it doesn't mean that, FDT_INTERNAL means "users can't monkey with
this". We need something to mean "open and users can monkey with it".
Maybe something with a similar function to FDT_EXTERNAL would
work... but we'd need to be careful about the points where things got
closed. We'd probably have to special case it in closem() when that
gets passed FDT_UNUSED.
Not sure how much this is worth it to avoid a bad close that's ignored anyway.
pws
next prev parent reply other threads:[~2013-10-27 21:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131027145917.GA5509@localhost.localdomain>
[not found] ` <131027100137.ZM4100@torch.brasslantern.com>
2013-10-27 17:46 ` multios doesn't work with 2>&1 Peter Stephenson
2013-10-27 18:27 ` Bart Schaefer
2013-10-27 19:39 ` Multio deadlock (Re: multios doesn't work with 2>&1) Bart Schaefer
2013-10-27 20:24 ` Bart Schaefer
2013-10-27 20:33 ` Peter Stephenson
2013-10-27 21:16 ` Peter Stephenson [this message]
2013-10-27 22:31 ` Bart Schaefer
2013-10-27 22:18 ` Bart Schaefer
2013-10-27 18:11 ` multios doesn't work with 2>&1 Bart Schaefer
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=20131027211627.79b05e20@pws-pc.ntlworld.com \
--to=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).