From: Matthew Wilcox <matthew@wil.cx>
To: parisc-linux@thepuffingroup.com
Cc: parisc-linux-cvs@puffin.external.hp.com
Subject: Re: linux bame
Date: Wed, 10 Jan 2001 23:31:49 +0000 [thread overview]
Message-ID: <20010110233149.A18122@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200101102108.OAA19847@puffin.external.hp.com>; from bame@puffin.external.hp.com on Wed, Jan 10, 2001 at 02:08:27PM -0700
On Wed, Jan 10, 2001 at 02:08:27PM -0700, Paul Bame wrote:
> Log message:
> First-pass attempt at /proc/config, mostly from grant. Seems to work
> fine with 'cat', but 'tail' and 'wc' aren't reliable with my userspace.
umm. this has often been discussed for addition to the standard linux
kernel, but linus has not yet taken patches to do so. i suggest searching
linux-kernel archives to see the arguments, i got bored and didn't read
them so i can't summarise. i don't think this is something we should
be adding.
tail and wc invariably don't work on /proc files. neither does less.
this is pretty inherent to the design of /proc and not a reflection on
your code.
> NOTE THIS IS ONLY VISIBLE on the proc_config branch.
it might be better to let this branch wither...
--
Revolutions do not require corporate support.
next parent reply other threads:[~2001-01-10 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200101102108.OAA19847@puffin.external.hp.com>
2001-01-10 23:31 ` Matthew Wilcox [this message]
[not found] <200011092253.PAA14963@puffin.external.hp.com>
2000-11-10 9:49 ` linux bame Matthew Wilcox
2000-11-10 15:57 ` bame
2000-11-14 19:17 ` Michael Ang
2000-11-14 20:00 ` Paul Bame
[not found] <200011012053.NAA15579@puffin.external.hp.com>
2000-11-02 0:13 ` Matthew Wilcox
2000-11-02 6:18 ` bame
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=20010110233149.A18122@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=parisc-linux-cvs@puffin.external.hp.com \
--cc=parisc-linux@thepuffingroup.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox