9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: corey@bitworthy.net, 9fans@9fans.net
Subject: Re: [9fans] a few misc. questions...
Date: Wed, 22 Jul 2009 09:40:09 +0100	[thread overview]
Message-ID: <c7959fe8764baa874482df050df11908@hamnavoe.com> (raw)
In-Reply-To: <200907220031.03865.corey@bitworthy.net>

> /rc/bin/termrc
> /rc/bin/termrc.local
> /cfg/$sysname/termrc

> ... but which would be considered the most logical place to deal with
> things such as setting hd parameters for the machine on bootup like
> the 'echo dma on > /dev/sdC0/ctl' example above?

In /cfg/$sysname/termrc, because you might not want it for every
machine you run.

> What's the conventional wisdom regarding which of those scripts
> are used for what purposes? i.e., when to prefer one over the

Roughly speaking:

/rc/bin/termrc - applies to all Plan 9 terminals everywhere
/rc/bin/termrc.local - applies to all terminals on your network
/cfg/$sysname/termrc - applies to one particular terminal

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

Submit a patch(1).

> Ok, so I may simply generally disregard any mention of kfs in any docs or
> scripts and config files I might happen upon?

Yes, if you have only fossil installed.




  parent reply	other threads:[~2009-07-22  8:40 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
2009-07-22  8:40     ` Richard Miller [this message]
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=c7959fe8764baa874482df050df11908@hamnavoe.com \
    --to=9fans@hamnavoe.com \
    --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).