From: "Anthony Sorace" <anothy@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] it's live
Date: Wed, 26 Jul 2006 16:30:44 -0400 [thread overview]
Message-ID: <509071940607261330s72c129cbr5508803da39a822e@mail.gmail.com> (raw)
In-Reply-To: <44C7C6C1.7010201@lanl.gov>
i know you said "more later", but i'm impatient.
i *think* this is really cool, but i'm not entirely sure. that is, i'm
sure there are cool bits, but i don't know which ones. how's the thing
work? i assume the embedded system's connected directly to the GPS, as
you talked about a while ago, but isn't the web server. how's that
transfer happen? and what system/web server is doing the overlay?
i'm not tremendously interested in GPS myself, but very much so in DoC
and the other connecting bits.
next prev parent reply other threads:[~2006-07-26 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 19:47 Ronald G Minnich
2006-07-26 19:52 ` Devon H. O'Dell
2006-07-26 20:30 ` Anthony Sorace [this message]
2006-07-26 21:30 ` Ronald G Minnich
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=509071940607261330s72c129cbr5508803da39a822e@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).