From: elko <elko@home.nl>
To: Hugh Dickins <hugh@veritas.com>, Marko Rauhamaa <marko@pacujo.nu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Need blocking /dev/null
Date: Tue, 30 Oct 2001 00:03:42 +0100 [thread overview]
Message-ID: <01103000034207.13457@ElkOS> (raw)
In-Reply-To: <Pine.LNX.4.21.0110292144120.1085-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.21.0110292144120.1085-100000@localhost.localdomain>
On Monday 29 October 2001 22:45, Hugh Dickins wrote:
> On Mon, 29 Oct 2001, Marko Rauhamaa wrote:
> > I noticed that I need a pseudodevice that opens normally but blocks
> > all reads (and writes). The only way out would be through a signal.
> > Neither /dev/zero nor /dev/null block, but is there some other
> > standard device that would do the job?
> >
> > If there isn't, writing such a pseudodevice would be trivial. What
> > should it be called? Any chance of including that in the kernel?
>
> /dev/never
sorry, the bait was too obvious: /dev/microsoft
--
ElkOS: 12:01am up 6 days, 9:32, 3 users, load average: 2.54, 2.40, 2.27
bofhX: appears to be a Slow/Narrow SCSI-0 Interface problem
\x04
next prev parent reply other threads:[~2001-10-29 23:01 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
2001-11-01 7:24 ` Ville Herva
2001-10-29 21:45 ` Hugh Dickins
2001-10-29 23:03 ` elko [this message]
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=01103000034207.13457@ElkOS \
--to=elko@home.nl \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marko@pacujo.nu \
/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.