From: David Ford <david@linux.com>
To: David Santinoli <u235@libero.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG in 2.4.0: dd if=/dev/random of=out.txt bs=10000 count=100
Date: Sat, 13 Jan 2001 14:45:49 -0800 [thread overview]
Message-ID: <3A60DA9C.19A2B13A@linux.com> (raw)
In-Reply-To: <20010113035314.316.qmail@web5205.mail.yahoo.com> <20010113213728.B790@aidi.santinoli.com>
David Santinoli wrote:
> On Fri, Jan 12, 2001 at 07:53:14PM -0800, Rob Landley wrote:
> > If I do the dd line in the title under 2.4.0 I get an
> > out.txt file of 591 bytes.
> And it's the same under 2.2.x, too.
>
> > dd says it completes happily even when copying from
> > random. 0+100 records in, 0+100 records out. It
> It's not a fault of dd, or of the read() system call, either. It's just the way
> /dev/random works - you can't read more bytes than those available in the
> entropy pool. And if you try, you'll just fail with no error.
It won't fail, it will block, then continue reading when more bytes are
available. The application may time out however.
-d
-- ---NOTICE
-- fwd: fwd: fwd: type emails will be deleted automatically.
"There is a natural aristocracy among men. The grounds of this are
virtue and talents", Thomas Jefferson [1742-1826], 3rd US President
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-13 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 3:53 BUG in 2.4.0: dd if=/dev/random of=out.txt bs=10000 count=100 Rob Landley
2001-01-13 4:44 ` David Ford
2001-01-13 5:08 ` John Heffner
2001-01-13 20:37 ` David Santinoli
2001-01-13 22:45 ` David Ford [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-13 5:28 Rob Landley
2001-01-13 19:24 Bernd Eckenfels
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=3A60DA9C.19A2B13A@linux.com \
--to=david@linux.com \
--cc=david+validemail@kalifornia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=u235@libero.it \
/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