From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] SMB -> 9P
Date: Tue, 19 Sep 2000 14:07:08 +0100 [thread overview]
Message-ID: <20000919130503.82605199D4@mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
it's not too bad if you work from the documents and only
glance at other implementations for the undocumented bits,
and do the name service -- if needed -- by adding an interface to the existing
one instead of including a privately hacked copy of BIND (well,
that's what it looked like to me at the time).
as these things go it's possibly easier and more worthwhile than NFS.
as a protocol it's a bit silly because it mixes everything together.
[-- Attachment #2: Type: message/rfc822, Size: 1368 bytes --]
To: cse.psu.edu!9fans
Subject: Re: [9fans] SMB -> 9P
Date: Tue, 19 Sep 2000 08:40:06 -0400
Message-ID: <20000919124008.52B9219A09@mail>
but coding it? what a ghastly prospect.
I really don't think it would be that bad.
Certainly better than say vga.
Russ
next reply other threads:[~2000-09-19 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-19 13:07 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-19 12:40 Russ Cox
2000-09-19 11:01 boyd.roberts
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=20000919130503.82605199D4@mail \
--to=forsyth@vitanuova.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).