From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <4638ff903fe76813f3aaa6f6502bb2ef@hamnavoe.com>
To: 9fans@9fans.net
From: Richard Miller <9fans@hamnavoe.com>
Date: Sat, 18 Aug 2012 14:02:27 +0100
In-Reply-To: <20120818133631.68d7ae16@zinc.9fans.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] fossil option -m
Topicbox-Message-UUID: ab5943d2-ead7-11e9-9d60-3106f5b1d025

> But maybe without the leading '*', since they
> aren't kernel parameters.

Probably right, although it's never been clear to me why some things
have '*' and some don't.  For example etherN=XXXXX is used only by
the kernel, but it still gets passed in the normal '#e' environment
to processes.

On further thought, what about generalising a bit more: plan9.ini(8)
already has
        factotumopts=options
          Causes boot(8) to start factotum with the given options,

If we allowed XXXXopts=options, where XXXX is the name of any command
in /boot, my earlier suggestion would be just a particular case of this
with
	fossilopts=-m NN
	ventiopts=-m NN

Is this a simplification or a complication?

I'd actually prefer 'fossil-opts=-M NN' , but we already have the
precedent of factotumopts.