From: "John Floren" <slawmaster@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] Plan 9 in robotics
Date: Mon, 9 Oct 2006 15:33:45 -0400 [thread overview]
Message-ID: <7d3530220610091233w1ecb8af7v9e4f6be61df221b2@mail.gmail.com> (raw)
Hi everyone
Is anyone currently using Plan 9 to control robots? It seems to me
that the O.S. is well-suited for interfacing with some of the devices
my robotics club uses (serial GPS, etc), and the networked aspect
would make it useful for communicating among distributed, one-function
modules (we are considering ARM processors for this).
Thanks
John Floren
--
Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn
next reply other threads:[~2006-10-09 19:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 19:33 John Floren [this message]
2006-10-09 19:46 ` Skip Tavakkolian
[not found] <20061010075244.D9128E7C7@mail.cse.psu.edu>
2006-10-10 14:55 ` Bhanu Nagendra Pisupati
2006-10-10 16:23 ` Dan Cross
2006-10-11 2:04 ` Eric Smith
2006-10-11 4:38 ` Brantley Coile
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=7d3530220610091233w1ecb8af7v9e4f6be61df221b2@mail.gmail.com \
--to=slawmaster@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).