9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] mysterious auth
Date: Sat, 23 Jan 2010 08:12:25 +0200	[thread overview]
Message-ID: <d6c19c770e458a2955034df23a735b6b@proxima.alt.za> (raw)
In-Reply-To: <25638d2949fca1a94387ae1ab3e10fbb@9netics.com>

> it would be better to create a /cfg/example.auth/cpurc that includes
> keyfs and trusted services in it and remove them from /rc/bin/cpurc,
> since they come after /cfg/$sysname/cpurc is run.

You could submit a patch...

I have a feeling that the philosophy is for /cfg to be entirely
optional, so putting examples in there is not encouraged.  But what
about (late in /rc/bin/cpurc):

	# cpu-specific late startup
	if(test -e /cfg/$sysname/cpustart)
		. /cfg/$sysname/cpustart

?

++L




      parent reply	other threads:[~2010-01-23  6:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11 22:22 Skip Tavakkolian
2010-01-11 22:46 ` erik quanstrom
2010-01-12  2:10 ` Federico G. Benavento
2010-01-12  6:10   ` Skip Tavakkolian
2010-01-22 23:27     ` Skip Tavakkolian
2010-01-23  3:18       ` erik quanstrom
2010-01-23  6:12       ` lucio [this message]

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=d6c19c770e458a2955034df23a735b6b@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@9fans.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).