From: Andreas Schwab <schwab@suse.de>
To: Tim Walberg <twalberg@mindspring.com>
Cc: Ville Herva <vherva@niksula.hut.fi>,
John Adams <johna@onevista.com>,
linux-kernel@vger.kernel.org
Subject: Re: Need blocking /dev/null
Date: 05 Nov 2001 23:08:57 +0100 [thread overview]
Message-ID: <jek7x4swee.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0111012322310.14742-100000@Consulate.UFP.CX> <01110215041301.01066@flash> <20011102223209.D26218@niksula.cs.hut.fi> <20011102144604.E8312@mindspring.com>
In-Reply-To: <20011102144604.E8312@mindspring.com> (Tim Walberg's message of "Fri, 2 Nov 2001 14:46:04 -0600")
Tim Walberg <twalberg@mindspring.com> writes:
|> I think that
|>
|> find / -name foo 2>&-
|>
|> should do the trick (under ksh, anyway, and
|> probably zsh or bash as well).
This is different since the process now gets an error when trying to write
to fd 2, and a good implementation with check for errors.
Andreas.
--
Andreas Schwab "And now for something
Andreas.Schwab@suse.de completely different."
SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
next prev parent reply other threads:[~2001-11-05 22:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 21:07 Need blocking /dev/null Marko Rauhamaa
2001-10-29 21:24 ` Alan Cox
2001-10-30 3:52 ` Marko Rauhamaa
2001-10-30 7:02 ` Tim Connors
2001-10-30 16:04 ` Marko Rauhamaa
2001-10-31 0:51 ` Riley Williams
2001-10-31 9:23 ` Ville Herva
2001-10-31 23:13 ` Riley Williams
2001-11-01 0:11 ` Doug McNaught
2001-11-01 7:27 ` Ville Herva
2001-11-01 7:52 ` Abramo Bagnara
2001-11-01 23:51 ` Riley Williams
2001-11-02 19:53 ` Ville Herva
2001-11-02 20:04 ` John Adams
2001-11-02 20:32 ` Ville Herva
2001-11-02 20:46 ` Tim Walberg
2001-11-05 22:08 ` Andreas Schwab [this message]
2001-11-01 7:24 ` Ville Herva
2001-10-29 21:45 ` Hugh Dickins
2001-10-29 23:03 ` elko
2001-10-29 23:12 ` Mike Fedyk
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=jek7x4swee.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=johna@onevista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=twalberg@mindspring.com \
--cc=vherva@niksula.hut.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.