From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fun with cfs.
Date: Wed, 12 Jan 2005 23:30:39 +0000 [thread overview]
Message-ID: <c4a44349f3c9a025b0492829ddf0c86d@terzarima.net> (raw)
In-Reply-To: <ee9e417a0501121338377fdba1@mail.gmail.com>
>> iostats -df /fd/1 rc
>> # play with anything
as it happens, `i knew that', but i wonder if little idioms like that
might helpfully be added to the relevant manual pages in EXAMPLES.
perhaps the more obscure ones could all be collected together in emacs(1).
next prev parent reply other threads:[~2005-01-12 23:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 18:26 Ronald G. Minnich
2005-01-12 18:33 ` Fco. J. Ballesteros
2005-01-12 18:37 ` Ronald G. Minnich
2005-01-12 21:38 ` Russ Cox
2005-01-12 21:43 ` Ronald G. Minnich
2005-01-12 23:30 ` Charles Forsyth [this message]
2005-01-12 23:21 ` Ronald G. Minnich
2005-01-13 0:06 ` Russ Cox
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=c4a44349f3c9a025b0492829ddf0c86d@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cse.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;
as well as URLs for NNTP newsgroup(s).