From: Fco.J.Ballesteros <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] directories in server registry (#s)
Date: Mon, 8 Mar 2004 09:40:03 +0100 [thread overview]
Message-ID: <8074a2015162ebe15c8814636b62d983@plan9.escet.urjc.es> (raw)
In-Reply-To: <f3166f99105c319b5355241aabb056df@plan9.bell-labs.com>
> I think we need to think more about permissions before going crazy
> expanding /srv.
I think that it'd be a good thing to let the kernel know about permission
checking in the same way that fossil does. I mean, I'd expect the same
permission rules of /... apply for stuff in #...
Perhaps a control file to write the fossil /adm/user to the kernel plus a
generic routine to check permissions would be a good way to do it.
next prev parent reply other threads:[~2004-03-08 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 17:36 9nut
2004-03-07 16:40 ` David Presotto
2004-03-07 17:59 ` 9nut
2004-03-08 8:40 ` Fco.J.Ballesteros [this message]
2004-03-08 10:45 ` 9nut
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=8074a2015162ebe15c8814636b62d983@plan9.escet.urjc.es \
--to=nemo@lsub.org \
--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).