9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Vincent D Murphy <murphyv@student.cs.ucc.ie>
To: 9fans@cse.psu.edu
Subject: [9fans] heterogeneous cpu servers?
Date: Sun, 14 Jan 2001 16:56:06 +0000	[thread overview]
Message-ID: <20010114165606.A18906@student.cs.ucc.ie> (raw)

can a NT, linux, or solaris box 'be' a plan9 cpu server?  i fear not;
if this is the case, does anybody have an idea what would need to be
done to make it happen?

rationale: i have to develop java at work -- my duties dictate it.
however i have found that i am far more productive working in plan9/acme,
and now i want to use it for java, perl and oracle development work.
maybe i could even win over a few converts among my co-workers.  :)

to do this, i need to access tools on other hosts, running operating
systems which are better supported than plan9 by the developers of
those tools.  hopefully it is possible to do this as transparently as
possible, through creating a distributed development environment.

for example, it would be nice to run 'java/javac foo' or similar on my
plan9 terminal, and have javac run on a solaris box, with the obvious
multiplexing of /dev/cons and friends taken care of.  then i could
process the stderr output of the compiler such that it is acme-friendly.

needless to say, such a capability would be immensely useful for
distributed systems in general, rather that just 'hacking foo with acme'.

i have looked at cpu.c, but i remain in the dark as to how plan9 cpu
servers work from having read the source.  any pointers to further
(prosey) info, apart from cpu(1)?


             reply	other threads:[~2001-01-14 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-14 16:56 Vincent D Murphy [this message]
2001-01-16 17:58 ` please_no_spam_to_
2001-01-14 19:54 Russ Cox
2001-01-15 11:23 Richard Miller

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=20010114165606.A18906@student.cs.ucc.ie \
    --to=murphyv@student.cs.ucc.ie \
    --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).