From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] g9fs
Date: Wed, 13 Oct 2004 11:00:54 +0100 [thread overview]
Message-ID: <168a6a4451bdc5af460d73f112c2d1ef@quintile.net> (raw)
In-Reply-To: <568e0886f8a7a8d6b6ad7331a8c85802@quintile.net>
> I am tempted to have a go, unless Rob or
> Dave has written it already that is...
>
> -Steve
On closer inspection the code that exists was written
by reverse engineering packet snifs, and though this can
be fun, in my experience it is often depressing -
unpublished protocols being liable to change.
-Steve
next prev parent reply other threads:[~2004-10-13 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 20:20 [9fans] ask "unix co-creator" Rob Pike Ronald G. Minnich
2004-10-13 2:04 ` [9fans] g9fs John DeGood
2004-10-13 9:08 ` Steve Simon
2004-10-13 10:00 ` Steve Simon [this message]
2004-10-13 10:15 ` Nigel Roles
2004-10-13 14:15 ` Steve Simon
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=168a6a4451bdc5af460d73f112c2d1ef@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).