From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] logging file changes
Date: Tue, 19 Sep 2000 00:16:23 -0400 [thread overview]
Message-ID: <20000919041626.F2E4C199DF@mail> (raw)
Ignoring the data storage problem for the time being,
the ``right'' solution for getting to the Windows boxes
is to eliminate Linux and write something to serve SMB
by translating for a 9P server. A simple single-threaded
``get an SMB request, do some 9P requests, answer the
SMB request; repeat'' server would be a great start.
I've got some ideas about turning something like
that into a multithreaded (many pending requests)
service fairly transparently. This may be more work
than you were bargaining for.
U9fs goes the wrong way: it is for Plan 9 boxes to
mount the namespace on a Unix box, not the other
way 'round.
Russ
next reply other threads:[~2000-09-19 4:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-19 4:16 Russ Cox [this message]
2000-09-19 4:39 ` Lucio De Re
2000-09-19 20:46 ` Matt
-- strict thread matches above, loose matches on Subject: below --
2000-09-18 20:02 Matt
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=20000919041626.F2E4C199DF@mail \
--to=rsc@plan9.bell-labs.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).