From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Serving 9p in python - anyone started that?
Date: Thu, 14 Nov 2002 18:42:41 +0900 [thread overview]
Message-ID: <c132ef7a8b226ab05ecfbfde31c4f02c@granite.cias.osakafu-u.ac.jp> (raw)
> Just curiosity. Why did you take that way instead of trying to get
> a toolset for doing rc 9p servers? I mean, IMHO, rc is the
> preferred way of scripting. I've some times wanted to
> be able to plug rc scripts into a generic 9p server skeleton,
> and alto to write an rc script that uses other tools to speak 9p.
Yeah!
Plan 9 uses files as object, and all the applications could be constructed
as a user level file server. Yes, I agree this is the right way to us.
So, we can write many of user interfaces as scripts to write command
or data to an appropreate control or data files. Yes, I agree. However,
rc is the one on which we do all those work? I don't want to live with
shell scripts even such rc. Could we have more complete script
language for this purpose?
Kenji -- yes, I'm not an expert of this field
next reply other threads:[~2002-11-14 9:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 9:42 okamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-14 20:56 markp
2002-11-14 21:02 ` matt
2002-11-14 18:54 Russ Cox
2002-11-15 11:52 ` Boyd Roberts
[not found] <rsc@plan9.bell-labs.com>
2002-11-14 17:33 ` Russ Cox
2002-11-14 18:28 ` Scott Schwartz
2002-11-14 18:46 ` matt
2002-11-14 19:19 ` Dan Cross
2002-11-14 19:00 ` William Josephson
2002-11-14 9:49 Fco.J.Ballesteros
2002-11-14 10:28 ` matt
2002-11-14 8:53 Russ Cox
2002-11-14 17:05 ` Ronald G. Minnich
2002-11-14 18:24 ` Scott Schwartz
2002-11-14 8:34 Fco.J.Ballesteros
2002-11-14 17:37 ` John E. Barham
2002-11-13 19:18 Russ Cox
2002-11-13 17:22 matt
2002-11-13 19:33 ` John E. Barham
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=c132ef7a8b226ab05ecfbfde31c4f02c@granite.cias.osakafu-u.ac.jp \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--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).