From: Chris Wedgwood <cw@f00f.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alexander Viro <viro@math.psu.edu>, linux-kernel@vger.kernel.org
Subject: Re: [CFT][PATCH] large /proc/mounts and friends
Date: Tue, 16 Oct 2001 22:58:31 +1300 [thread overview]
Message-ID: <20011016225831.A26737@weta.f00f.org> (raw)
In-Reply-To: <Pine.GSO.4.21.0110152308440.11608-100000@weyl.math.psu.edu> <Pine.LNX.4.33.0110152053080.8668-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0110152053080.8668-100000@penguin.transmeta.com>
On Mon, Oct 15, 2001 at 09:01:17PM -0700, Linus Torvalds wrote:
But you're probably right that it doesn't really matter, and as we
really have "pipe" semantics we might as well dis-allow any lseek
except to the beginning (I know that there have been apps out
there that avoid re-opening /proc files by lseek'ing to zero and
re-reading - they may not be common enough to matter, though).
I always wondered why for a number of /proc entries that aren't really
files why we don't simply expose them as pipes as opposed to
zero-length files? Surely that will confuse fewer user-land programs
as well and feeling more technically correct?
--cw
next prev parent reply other threads:[~2001-10-16 9:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 1:10 Alexander Viro
2001-10-16 3:01 ` Linus Torvalds
2001-10-16 3:45 ` Alexander Viro
2001-10-16 4:01 ` Linus Torvalds
2001-10-16 4:08 ` Alexander Viro
2001-10-16 9:58 ` Chris Wedgwood [this message]
2001-10-16 3:52 ` Linus Torvalds
2001-10-16 4:03 ` Alexander Viro
2001-10-16 4:29 ` Linus Torvalds
2001-10-16 4:41 ` Linus Torvalds
2001-10-16 5:16 ` Keith Owens
2001-10-17 2:09 ` Alexander Viro
2001-10-16 4:43 ` Alexander Viro
2001-10-16 4:05 ` Anton Blanchard
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=20011016225831.A26737@weta.f00f.org \
--to=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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®