From: Mark Carter <alt.mcarter@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] So, why Plan 9?
Date: Tue, 12 Oct 2010 14:09:28 +0000 [thread overview]
Message-ID: <a4470c09-4800-4ec5-9763-9fda0010b1b0@f25g2000yqc.googlegroups.com> (raw)
In-Reply-To: <AANLkTimdFc9yUy7Uz8wONG7NQ14BCT_38_6SEQNHCbA5@mail.gmail.com>
On Oct 12, 9:21Â am, porttik...@gmail.com (Anssi Porttikivi) wrote:
> we really do not need protocols above the network layer, but HTTP, SMTP,
> DNS, SOAP, IIOP, IMAP, IRC, SSH, SSL, TP, SNMP and hundred others can all be
> replaced by "remote file access".
This sounds pretty interesting.
You may not be aware of it, but there's a project called thimbl (I'm
not involved in it) that is using the finger daemon on Linux to
provide a Twitter-esque clone. I'm not aware of its exact workings,
but it's something along the lines that a user's ~/.plan file is used
as the Twitter post. I have plan9port set up on Slackware, and I was
wondering how one might implement this idea using Plan 9. You're
saying that my "post" will just be a file then, stored in a directory
which others can read. Are there any docs you can point me to (Noddy
learns Plan 9) which would give the basics as to how I might set such
a thing up?
Sorry that I haven't even made it to "day one" of Plan 9 yet.
next prev parent reply other threads:[~2010-10-12 14:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 9:05 Mark Carter
2010-10-11 10:23 ` Sergey Zhilkin
2010-10-11 11:07 ` Robert Raschke
2010-10-11 11:17 ` Robert Raschke
2010-10-11 11:53 ` Nick LaForge
2010-10-11 13:39 ` Bruce Ellis
2010-10-11 14:45 ` ron minnich
2010-10-11 15:01 ` Karljurgen Feuerherm
2010-10-12 8:33 ` Aleksandar Kuktin
2010-10-12 8:51 ` Max E
2010-10-12 14:47 ` David Leimbach
2010-10-12 11:25 ` Steve Simon
2010-10-12 12:24 ` Jacob Todd
2010-10-12 16:04 ` Aleksandar Kuktin
2010-10-11 18:43 ` Brian L. Stuart
2010-10-12 8:17 ` Anssi Porttikivi
2010-10-12 14:09 ` Mark Carter [this message]
2010-10-12 14:53 ` Steve Simon
2010-10-12 14:59 ` David Leimbach
2010-10-12 9:06 ` Max E
2010-10-12 9:29 ` yy
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=a4470c09-4800-4ec5-9763-9fda0010b1b0@f25g2000yqc.googlegroups.com \
--to=alt.mcarter@gmail.com \
--cc=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).