9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Josh Wood <josh@utopian.net>
To: "corey@bitworthy.net" <corey@bitworthy.net>,
	Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] a few misc. questions...
Date: Wed, 22 Jul 2009 01:35:47 -0700	[thread overview]
Message-ID: <794094C1-38D7-4718-A5C1-5451510766E7@utopian.net> (raw)
In-Reply-To: <200907220031.03865.corey@bitworthy.net>

[-- Attachment #1: Type: text/plain, Size: 694 bytes --]


> As a further question on that point, where would you say would be the
> best place to persist that command?
>
> As far as I'm aware, my likely choices would be one of (in order of
> execution):
>
> /rc/bin/termrc
> /rc/bin/termrc.local
> /cfg/$sysname/termrc

I generally avoid touching termrc, put site-specific stuff for all
machines on the network in termrc.local, and put machine-specific
stuff in /cfg/$sysname/termrc (e.g. one machine supports dma but
another does not.)

"Cpurc" can be read for "termrc" above.


> ( by the way, what to do when I find errors in the man pages? .e.g.,
> in
> the interest of correcting them upstream )

See patch(1).

-Josh


[-- Attachment #2: Type: text/html, Size: 1182 bytes --]

  reply	other threads:[~2009-07-22  8:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22  5:21 Corey
2009-07-22  5:59 ` Josh Wood
2009-07-22  6:08   ` Josh Wood
2009-07-22  7:31   ` Corey
2009-07-22  8:35     ` Josh Wood [this message]
2009-07-22  8:40     ` Richard Miller
2009-07-22 13:13     ` erik quanstrom
2009-07-22 15:04       ` David Leimbach
2009-07-22 17:57         ` hiro
2009-07-22 19:12           ` David Leimbach
2009-07-23  3:36 ` Corey
2009-07-23  4:33   ` Federico G. Benavento
2009-07-24 15:48     ` maht

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=794094C1-38D7-4718-A5C1-5451510766E7@utopian.net \
    --to=josh@utopian.net \
    --cc=9fans@9fans.net \
    --cc=corey@bitworthy.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).