From: Bernd Eckenfels <inka-user@lina.inka.de>
To: 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 20:24:35 +0100 [thread overview]
Message-ID: <E14HWHz-0004ru-00@sites.inka.de> (raw)
In article <20010113035314.316.qmail@web5205.mail.yahoo.com> you wrote:
> If I do the dd line in the title under 2.4.0 I get an
> out.txt file of 591 bytes.
/dev/random will only give you as much bytes as are available. and even then
you should not do it cause you drain the random pool. Use /dev/urandom
instead.
Greetings
Bernd
-
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 reply other threads:[~2001-01-13 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 19:24 Bernd Eckenfels [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-13 5:28 BUG in 2.4.0: dd if=/dev/random of=out.txt bs=10000 count=100 Rob Landley
2001-01-13 3:53 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
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=E14HWHz-0004ru-00@sites.inka.de \
--to=inka-user@lina.inka.de \
--cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox