From: Rob Landley <telomerase@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: BUG in 2.4.0: dd if=/dev/random of=out.txt bs=10000 count=100
Date: Fri, 12 Jan 2001 19:53:14 -0800 (PST) [thread overview]
Message-ID: <20010113035314.316.qmail@web5205.mail.yahoo.com> (raw)
If I do the dd line in the title under 2.4.0 I get an
out.txt file of 591 bytes.
If I do the same thing from /dev/zero, I get the
expected 1,000,000 byte file.
I've shoehorned 2.4.0 into a fresh red hat 7.0 install
which could quite easily be a bad thing, yes ripped
out their strange gcc and symlinked kgcc->gcc to do
the compile. But other than this it seems to be
working. (So far...)
dd says it completes happily even when copying from
random. 0+100 records in, 0+100 records out. It
takes about thirty seconds to finish on the dual
gigahertz processor intel box I'm using to test it,
which implies it's actually performing the truly
impressive waste of CPU cycles I'm requesting from it.
I'm just not getting the data in my file.
Am I doing something wrong?
My dd is from fileutils-4.0x-3. (Straight Red Hat
7.0, I think...) Didn't see anything about that in
Documentation/Changes...
I'll be happy to try one of the prepatches if anybody
thinks they've addressed this problem already.
Anybody? Need more debugging info? Want me to wave a
dead chicken at something specific? Stick printk's
into the kernel?...
Rob
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
-
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 3:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 3:53 Rob Landley [this message]
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
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=20010113035314.316.qmail@web5205.mail.yahoo.com \
--to=telomerase@yahoo.com \
--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
all inboxes | Powered by JetHome®