From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: [sources] 20070410: % cat
Date: Thu, 12 Apr 2007 14:43:46 -0400 [thread overview]
Message-ID: <9ab217670704121143w706774a9ic02c2d3251e6948f@mail.gmail.com> (raw)
In-Reply-To: <a7ade0c795647581f55c26d59c22de78@plan9.bell-labs.com>
2007/4/12, geoff@plan9.bell-labs.com <geoff@plan9.bell-labs.com>:
> You only need files in /cfg for a machine if that machine is an
> exception to your normal policies (in cpurc, namespace, consoledb,
> etc.). I would expect that a cluster would need zero or one such
> exceptions, as the machines are supposed to be interchangeable, right?
In my mind, this is not entirely the case. The other reason to use it
is to avoid actually touching cpurc, so that you don't have to
remember to type -s '/rc/bin/cpurc' when I pull, after backing it up
and merging any changes back in. Since pull is the primary means of
keeping the system up to date, it's a real pain to try to merge all
these changes.
--dho
next prev parent reply other threads:[~2007-04-12 18:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5247962e2f1f11c9b374c57d9a9a71db@cat-v.org>
2007-04-12 15:14 ` [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF 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 [this message]
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
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
[not found] <12a554de22f1992874430323d774bd88@plan9.bell-labs.com>
2007-04-13 6:00 ` [9fans] Re: [sources] 20070410: % cat Lucio De Re
2007-04-13 14:25 ` Devon H. O'Dell
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
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=9ab217670704121143w706774a9ic02c2d3251e6948f@mail.gmail.com \
--to=devon.odell@gmail.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).