From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: "Lucio De Re" <lucio@proxima.alt.za>,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: [sources] 20070410: % cat
Date: Fri, 13 Apr 2007 10:25:28 -0400 [thread overview]
Message-ID: <9ab217670704130725k7baf92b3ve84862ec71130a14@mail.gmail.com> (raw)
In-Reply-To: <4e483a4a1847f6ddc09e55219ca67f11@proxima.alt.za>
2007/4/13, Lucio De Re <lucio@proxima.alt.za>:
> > Then you need two different sets of policy files and to have your
> > initialisation bind the right ones into place. I'm doing this now for
> > a set of diverse machines with different keys, policies, etc. all
> > sharing a single file server.
>
> That does not contradict my statement that it does not scale. Much as
> I appreciate the philosophical value of bind/mount, a trillion
> instances of a configuration file are going to be unmanageable. Ron
> is right that there is no slick solution, but it's worth knowing that
> the current approach deserves exploring further.
>
> ++L
Do you know anybody who has ever come up with a better idea? This is
very similar to Maildir replacing mbox. It sounds good, but when you
have 250k messages, it ends up being slower simply to traverse the
directory. In FreeBSD anyway.
However, it does scale. Much, much better than a case where you have
the same requirement for thousands of systems in a switch () statment.
--dho
next prev parent reply other threads:[~2007-04-13 14:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <12a554de22f1992874430323d774bd88@plan9.bell-labs.com>
2007-04-13 6:00 ` Lucio De Re
2007-04-13 14:25 ` Devon H. O'Dell [this message]
2007-04-13 14:56 ` erik quanstrom
2007-04-13 18:22 ` Lyndon Nerenberg
2007-04-13 21:39 ` Paweł Lasek
2007-04-14 14:51 ` Russ Cox
2007-04-13 15:00 ` Lucio De Re
2007-04-12 18:41 [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF Russ Cox
2007-04-13 4:18 ` [9fans] Re: [sources] 20070410: % cat Lucio De Re
2007-04-13 4:59 ` geoff
-- strict thread matches above, loose matches on Subject: below --
2007-04-12 18:25 [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF ron minnich
2007-04-12 18:38 ` [9fans] Re: [sources] 20070410: % cat geoff
2007-04-12 18:43 ` Devon H. O'Dell
2007-04-12 16:08 [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF Devon H. O'Dell
2007-04-12 17:42 ` [9fans] Re: [sources] 20070410: % cat geoff
2007-04-12 18:00 ` Anthony Sorace
2007-04-12 18:16 ` Russ Cox
2007-04-12 18:57 ` Anthony Sorace
2007-04-13 4:04 ` Lucio De Re
2007-04-13 4:58 ` geoff
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=9ab217670704130725k7baf92b3ve84862ec71130a14@mail.gmail.com \
--to=devon.odell@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=lucio@proxima.alt.za \
/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).