From: Jan Kasprzak <kas@informatics.muni.cz>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-pre11 /proc/partitions read
Date: Tue, 22 Oct 2002 18:14:26 +0200 [thread overview]
Message-ID: <20021022181426.P26402@fi.muni.cz> (raw)
In-Reply-To: <Pine.LNX.3.95.1021022110331.3644A-100000@chaos.analogic.com>; from root@chaos.analogic.com on Tue, Oct 22, 2002 at 11:10:29AM -0400
Richard B. Johnson wrote:
:
: > # dd if=/proc/partitions bs=512|wc -l
: > 1+1 records in
: > 1+1 records out
: > 12
: >
: > # dd if=/proc/partitions bs=128k|wc -l
: > 0+1 records in
: > 0+1 records out
: > 32
:
: Well yes, sorta. The proc file-system is a compromise. You can
: `cat` it and `more` it, but anything that uses `lseek` will
: fail in strange ways.
I hope dd(1) does not use lseek() :-) The question is
whether the application should supply a big enough buffer to read(2)
or whether it is possible to read(2) in more smaller chunks.
-Y.
--
| Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> |
| GPG: ID 1024/D3498839 Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
| http://www.fi.muni.cz/~kas/ Czech Linux Homepage: http://www.linux.cz/ |
|-- If you start doing things because you hate others and want to screw --|
|-- them over the end result is bad. --Linus Torvalds to the BBC News --|
next prev parent reply other threads:[~2002-10-22 16:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 14:19 2.4.20-pre11 /proc/partitions read Jan Kasprzak
2002-10-22 15:10 ` Richard B. Johnson
2002-10-22 16:14 ` Jan Kasprzak [this message]
2002-10-22 18:40 ` Andries Brouwer
2002-10-22 18:10 ` Marcelo Tosatti
2002-10-23 8:36 ` Jan Kasprzak
2002-10-22 18:45 ` Christoph Hellwig
2002-10-22 18:59 ` Andries Brouwer
2002-10-22 18:26 ` Marcelo Tosatti
2002-10-22 19:32 ` Andries Brouwer
2002-10-22 19:35 ` Christoph Hellwig
2002-10-22 19:58 ` Andries Brouwer
2002-10-22 20:32 ` Alan Cox
2002-10-23 8:39 ` Jan Kasprzak
2002-10-23 9:13 ` Jan Kasprzak
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=20021022181426.P26402@fi.muni.cz \
--to=kas@informatics.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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.