From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] exportfs
Date: Sun, 8 Jul 2001 23:56:19 -0400 [thread overview]
Message-ID: <20010709035619.27191.qmail@g.bio.cse.psu.edu> (raw)
In-Reply-To: Message from arisawa@ar.aichi-u.ac.jp of "Mon, 09 Jul 2001 12:28:36 +0900." <20010709033215.9312F199FC@mail.cse.psu.edu>
I think something like that is a good idea.
The thing that I sometimes want is to do that in the local case, a way
to say "everything under /foo is read only", as a sanity check on e.g. a
http daemon.
Maybe the best approach is an ro-fs that you mount first, and then
exportfs? Is that more modular, or just more work?
next prev parent reply other threads:[~2001-07-09 3:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-09 3:28 arisawa
2001-07-09 3:56 ` Scott Schwartz [this message]
2001-07-09 16:08 ` Dan Cross
2001-07-09 23:41 arisawa
2001-07-10 0:59 rob pike
2001-07-10 2:46 ` Dan Cross
2001-07-10 2:50 rob pike
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=20010709035619.27191.qmail@g.bio.cse.psu.edu \
--to=schwartz@bio.cse.psu.edu \
--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).