From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] some shell scripts
Date: Wed, 13 Oct 2004 23:50:54 -0700 [thread overview]
Message-ID: <2c09e36b136393b4df31b8b14a3c2f27@collyer.net> (raw)
In-Reply-To: <20041014105926.08edbf1f.martin_ml@parvat.com>
I think performance could be acceptable: I run lnfs over both file
systems (main and other) on my old ken file server and it doesn't seem
to slow things noticeably, and this should be similar: the file server
would just pass requests through, taking note of creations and
removals and updating its database. It sounds pretty straightforward
actually.
next prev parent reply other threads:[~2004-10-14 6:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 22:38 Russ Cox
2004-10-14 5:29 ` Martin C.Atkins
2004-10-14 6:50 ` geoff [this message]
2004-10-14 9:56 ` Martin C.Atkins
2004-10-14 15:29 ` Nigel Roles
2004-10-15 0:25 ` geoff
2004-10-15 0:28 ` Russ Cox
2004-10-15 0:38 ` geoff
2004-10-14 9:22 ` Fco. J. Ballesteros
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=2c09e36b136393b4df31b8b14a3c2f27@collyer.net \
--to=geoff@collyer.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).