From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] something more simple than import(1) -B
Date: Thu, 5 Apr 2007 18:35:40 -0400 [thread overview]
Message-ID: <ee9e417a0704051535k32aa65b6w8521c1c10b15d596@mail.gmail.com> (raw)
In-Reply-To: <a4e6962a0704051445g11695c42s13f7a5f47f03395f@mail.gmail.com>
On 4/5/07, Eric Van Hensbergen <ericvh@gmail.com> wrote:
> Probably a stupid question -- there seems like there should be a
> simple way to take stdin/stdout and generate a srv file -- such that I
> could aux/listen1 tcp!*!someport srvit -b somesrvname
aux/listen1 tcp!*!someport rc -c 'echo -n 0 > /srv/somesrvname'
Russ
next prev parent reply other threads:[~2007-04-05 22:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 21:45 Eric Van Hensbergen
2007-04-05 22:35 ` Russ Cox [this message]
2007-04-05 22:38 ` Eric Van Hensbergen
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=ee9e417a0704051535k32aa65b6w8521c1c10b15d596@mail.gmail.com \
--to=rsc@swtch.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).