From: LiteStar numnums <litestar@gmail.com>
To: Russ Cox <russcox@gmail.com>
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] standalone auth/cpu server and fossil?
Date: Thu, 14 Jul 2005 20:20:26 -0500 [thread overview]
Message-ID: <283f5df1050714182070a39512@mail.gmail.com> (raw)
In-Reply-To: <ee9e417a05071409286fbc7554@mail.gmail.com>
Meh, errors smerrors =P.
On 7/14/05, Russ Cox <russcox@gmail.com> wrote:
> > You don't really need to con /srv/fscons; echo's will do perfectly:
> > echo 'uname bootes bootes' >> /srv/fscons
>
> Unless you want to see errors.
>
> Russ
>
--
In possibility the eternal, rightly understood, continually lays out
only a small piece at a time
In possibility the eternal is continually near enough to be at hand
and yet far enough away to keep man advancing towards the
eternal, on the way, in forward movement. In this way the ternal lures
and draws a person, in the possible, from craddle to grave
if he just chooses to hope
<<Soren Kierkegaard>>
prev parent reply other threads:[~2005-07-15 1:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 14:55 rattan
2005-07-14 16:24 ` LiteStar numnums
2005-07-14 16:28 ` Russ Cox
2005-07-14 19:16 ` Dan Cross
2005-07-14 19:20 ` Steve Simon
2005-07-15 1:20 ` LiteStar numnums [this message]
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=283f5df1050714182070a39512@mail.gmail.com \
--to=litestar@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=russcox@gmail.com \
/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).