From: "Anthony Sorace" <anothy@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] cpu(1) design...
Date: Fri, 9 Nov 2007 09:55:04 -0500 [thread overview]
Message-ID: <509071940711090655r445ab903sd820f3ebbb584836@mail.gmail.com> (raw)
In-Reply-To: <df49a7370711090645u5e6c1ac6h82ab046d2068ba8c@mail.gmail.com>
ah, i see. yes, i've been caught by that as well.
the problem is i've also been caught doing 'cpu system', thinking of
it as a parallel to ssh or telnet. i probably assume -c more often
than -h, but that does seem less consistent with other "remote access"
commands.
next prev parent reply other threads:[~2007-11-09 14:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 12:50 Steve Simon
2007-11-09 14:40 ` Anthony Sorace
2007-11-09 14:45 ` roger peppe
2007-11-09 14:55 ` Anthony Sorace [this message]
2007-11-09 15:33 ` Steve Simon
2007-11-09 15:46 ` ron minnich
2007-11-09 15:57 ` erik quanstrom
2007-11-09 14:52 ` erik quanstrom
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=509071940711090655r445ab903sd820f3ebbb584836@mail.gmail.com \
--to=anothy@gmail.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).