From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: factotum
Date: Sat, 17 May 2003 13:24:06 -0400 [thread overview]
Message-ID: <Pine.LNX.4.30.0305171321540.25295-100000@athena> (raw)
In-Reply-To: <Pine.LNX.4.30.0305171216240.25295-100000@athena>
Sam,
RTFEFTM. (examples from the manpage)
ok, i figured someone should say it.
Any docs to explain pcauth vs. pccpu?
Sam
next prev parent reply other threads:[~2003-05-17 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.30.0305161044360.21257-100000@athena>
2003-05-16 16:06 ` Russ Cox
2003-05-17 16:34 ` Sam
2003-05-17 17:24 ` Sam [this message]
2003-05-17 19:37 ` northern snowfall
2003-05-18 23:28 ` [9fans] Hangar 18 Weekly Social - May 22, 2003 Jim Choate
2003-05-19 1:00 ` northern snowfall
2003-05-19 0:08 ` boyd, rounin
2003-05-19 0:36 ` [9fans] What is TFT? (was: Hangar 18 Weekly Social - May 22, 2003) Jim Choate
2003-05-19 0:45 ` [9fans] anybody put nvram onto Sony VAIO memort stick? boyd, rounin
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=Pine.LNX.4.30.0305171321540.25295-100000@athena \
--to=sah@softcardsystems.com \
--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).