From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9base ports to unix
Date: Fri, 19 Aug 2005 14:52:50 +0100 [thread overview]
Message-ID: <93198fd06809a16f4a19e427e72b0f4e@quintile.net> (raw)
In-Reply-To: <89d1e7b8050819053245099105@mail.gmail.com>
Hi,
> I did so, because for writing rc scripts, which is my favorite
> scripting language already, it sucked to be dependent on dynamically
> linked bloat binaries from GNU. I measured that a simple sleep call to
Not wishing to troll, but genuine interest - why do you prefer a port
of plan9's rc to a staticially linked version of Byrons rc rewrite?
For me there is nothing to chose unless you have a lot of scripts from
a plan9 system that tickle the changes Byron made. I find the differences
between Plan9 and Linux sed more of a pain.
-Steve
next prev parent reply other threads:[~2005-08-19 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 12:32 Anselm R. Garbe
2005-08-19 13:52 ` Steve Simon [this message]
2005-08-19 14:10 ` Anselm R. Garbe
2005-08-19 19:58 ` Scott Schwartz
2005-08-21 20:16 ` Russ Cox
2005-08-22 6:13 ` Anselm R. Garbe
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=93198fd06809a16f4a19e427e72b0f4e@quintile.net \
--to=steve@quintile.net \
--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).