From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Creating new mail users; mail -c
Date: Mon, 22 Mar 2010 14:24:53 -0700 [thread overview]
Message-ID: <3e1162e61003221424j77534f93te1d7d56a9087964c@mail.gmail.com> (raw)
In-Reply-To: <44e316d676994d41d7b0811b31da8b08@brasstown.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
On Mon, Mar 22, 2010 at 1:55 PM, erik quanstrom <quanstro@quanstro.net>wrote:
> On Mon Mar 22 16:22:15 EDT 2010, nemo@lsub.org wrote:
> > It would help being able to "append" to a directory, i.e., being able to
> > create new files but not to, say, remove, already created files.
>
> i considered modifying the fileserver to do something similar
> for nupas. perhaps reusing the 'a' bit. but in the end, i didn't
> do it as we weren't having a problem. i use the mode 773 for
> mailboxes which can be delivered to by other users and 700
> for mailboxes which can't be delivered to by other users. denying
> read access at least makes it annoying to guess all the mail files
> in the mbox.
>
> (thanks to anthony for a recent fix to splitmbox.)
>
> russ had a specific objection to "append" directories. i don't
> recall how the argument went.
>
Is it because you can bind in new stuff to a directory if you need it?
>
> - erik
>
>
[-- Attachment #2: Type: text/html, Size: 1524 bytes --]
next prev parent reply other threads:[~2010-03-22 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 3:53 Anthony Sorace
2010-03-22 5:40 ` Russ Cox
2010-03-22 13:37 ` erik quanstrom
2010-03-22 14:50 ` roger peppe
2010-03-22 20:20 ` Francisco J Ballesteros
2010-03-22 20:55 ` erik quanstrom
2010-03-22 21:24 ` David Leimbach [this message]
2010-03-22 21:29 ` erik quanstrom
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=3e1162e61003221424j77534f93te1d7d56a9087964c@mail.gmail.com \
--to=leimy2k@gmail.com \
--cc=9fans@9fans.net \
/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).