From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF
Date: Thu, 12 Apr 2007 14:41:55 -0400 [thread overview]
Message-ID: <20070412184155.C99371E8C1C@holo.morphisms.net> (raw)
In-Reply-To: <13426df10704121125m1fe1450fw51fdeea162d4cea4@mail.gmail.com>
/cfg is intended for machines with per-node configuration.
If you have 1000 machines that are functionally identical,
you're not supposed to write /cfg directories for any of them.
But if you have one machine that is supposed to do something
a little different (like run a venti server, or be an auth server),
then you can put those differences into /cfg/$sysname/cpurc.
What /cfg replaced was a giant
switch($sysname){
case this
...
case that
...
}
in /rc/bin/cpurc. It's definitely a step forward for that
situation.
The Plan 9 distribution has always been "this works
well at Bell Labs; you might need to change it to suit you",
and that applies to /cfg as much as anything else.
/cfg is just a pragmatic solution for one use model.
If you are running large clusters, you will want something
different. But most Plan 9 installations are not large clusters.
I for one am glad that people can edit cpurc instead of
having to agree on a general startup script mechanism.
Otherwise we might end up with something like /etc/init.d.
Russ
next prev parent reply other threads:[~2007-04-12 18:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5247962e2f1f11c9b374c57d9a9a71db@cat-v.org>
2007-04-12 15:14 ` Uriel
2007-04-12 15:32 ` Devon H. O'Dell
2007-04-12 15:48 ` erik quanstrom
2007-04-12 16:03 ` Devon H. O'Dell
2007-04-12 16:05 ` Russ Cox
2007-04-12 15:56 ` Uriel
2007-04-12 16:08 ` 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
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 18:40 ` [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF erik quanstrom
2007-04-12 18:50 ` Francisco J Ballesteros
2007-04-12 18:41 ` Russ Cox [this message]
2007-04-13 4:18 ` [9fans] Re: [sources] 20070410: % cat Lucio De Re
2007-04-13 4:59 ` geoff
2007-04-12 18:48 ` [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF andrey mirtchovski
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=20070412184155.C99371E8C1C@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).