All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Walberg <twalberg@mindspring.com>
To: Ville Herva <vherva@niksula.hut.fi>
Cc: John Adams <johna@onevista.com>, linux-kernel@vger.kernel.org
Subject: Re: Need blocking /dev/null
Date: Fri, 2 Nov 2001 14:46:04 -0600	[thread overview]
Message-ID: <20011102144604.E8312@mindspring.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0111012322310.14742-100000@Consulate.UFP.CX> <01110215041301.01066@flash> <20011102223209.D26218@niksula.cs.hut.fi>
In-Reply-To: <20011102223209.D26218@niksula.cs.hut.fi> from Ville Herva on 11/02/2001 14:32

[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]

I think that

find / -name foo 2>&-

should do the trick (under ksh, anyway, and
probably zsh or bash as well). Csh variants
IIRC don't have the concept of closing a
file descriptor...

		tw

>>	
>>	The initial question was how to do
>>	
>>	find / -name foo 2> /dev/null 
>>	
>>	or similar if /dev/null is not present. (Eat is a place holder for a
>>	imaginary progrom acting as /dev/null replacement).
>>	
>>	I guess 
>>	
>>	find / -name foo 2>/dev/stdout 1>/dev/stderr | eat
>>	
>>	would (kinda) work, but it fails if you want to do
>>	
>>	find / -name foo 2> /dev/null | less
>>	
>>	Can be done with named pipes, though.
>>	
>>	
>>	-- v --
>>	
>>	v@iki.fi
>>	-
>>	To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>	the body of a message to majordomo@vger.kernel.org
>>	More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>	Please read the FAQ at  http://www.tux.org/lkml/
End of included message



-- 
+--------------------------+------------------------------+
| Tim Walberg              | twalberg@mindspring.com      |
| 830 Carriage Dr.         | www.concentric.net/~twalberg |
| Algonquin, IL 60102      |                              |
+--------------------------+------------------------------+

[-- Attachment #2: Type: application/pgp-signature, Size: 175 bytes --]

  reply	other threads:[~2001-11-02 20:46 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 [this message]
2001-11-05 22:08                     ` Andreas Schwab
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=20011102144604.E8312@mindspring.com \
    --to=twalberg@mindspring.com \
    --cc=johna@onevista.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.