From: Franklin Robert Araujo França 973930@dcc.unicamp.br
Subject: [9fans] CPU command
Date: Tue, 29 Sep 1998 11:35:26 -0300 [thread overview]
Message-ID: <19980929143526.CC356ptYnmvlMW_m-NlJYnpT5PunQJaKyI87B_tcWJo@z> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 699 bytes --]
I´m trying to use the CPU command through a CPU server (named pinduca)
and a terminal (named mercurio). In the terminal prompt I type:
term% cpu -h il!pinduca!17005
And in the CPU server prompt I type nothing:
pinduca%
After I type <enter> in the terminal prompt, I receive the following
prompt:
pinduca%
And I´m logged at pinduca and I can see it´s name space and not
mercurio´s name space. This is like Rlogin, but the Plan 9 manual says: the
mechanism is quite different from either remote login or network file
system access.
What is wrong? Why the CPU command isn´t working correctly?
Thanks.
Franklin.
next reply other threads:[~1998-09-29 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-29 14:35 Franklin [this message]
1998-09-29 16:14 forsyth
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=19980929143526.CC356ptYnmvlMW_m-NlJYnpT5PunQJaKyI87B_tcWJo@z \
--to=9fans@9fans.net \
/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).