From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /lib/namespace vs /rc/bin/*rc
Date: Tue, 24 Apr 2007 18:08:58 -0400 [thread overview]
Message-ID: <20070424220900.C24451E8C26@holo.morphisms.net> (raw)
In-Reply-To: <7d07056781f74b48f508a2975885be3a@coraid.com>
> right. i'm not sure i see the advantage of hiding #t. surely
> this isn't a performance argument?
i see no point to putting a file into everyone's
name space when only one user has permission
to open it or when approximately everyone will
have no need for it.
you are free to customize the system if you wish
to use it in a different way.
russ
prev parent reply other threads:[~2007-04-24 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 21:36 erik quanstrom
2007-04-24 21:47 ` Russ Cox
2007-04-24 22:01 ` erik quanstrom
2007-04-24 22:08 ` Russ Cox [this message]
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=20070424220900.C24451E8C26@holo.morphisms.net \
--to=rsc@swtch.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).