Re: [9fans] changes in 9load

[Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>]

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

Not quite. Just to clarify the aim of the code I sent:

My proposal was to keep in plan9.ini just that part of /boot
that you consider configuration (venti.conf, fossil.conf mainly).
Otherwise, I keep /boot as it was, readonly, with all the tools in.
However, I'm putting the configuration for fs, fossil, and venti into
plan9.ini. (Now that the alternative is to put that in /boot).

I also thought of making /boot rw, but that would be much more clumsy that
putting the config somewhere else. When thinking about where to put it,
I considered that in fact I had to keep a plan9.ini everywhere, and I
just decided to put the config for the file server in that place too (instead
of adding a different place).

[-- Attachment #2: Type: message/rfc822, Size: 3307 bytes --]

From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] changes in 9load
Date: Wed, 21 May 2003 19:06:58 +0200
Message-ID: <20030521190658.Z7647@cackle.proxima.alt.za>

On Wed, May 21, 2003 at 11:22:24AM -0400, Russ Cox wrote:
>
> I'd rather not see the multiline environment variable hack
> go into plan9.ini.  (Though if it did, I'd name the sections [$var]
> instead of [!var].)
>
> [ Etc. ]

I agree with Russ's sentiments, possibly not for the exact same
reasons.

I couldn't quite find an opportunity earlier, but I'd like to add
a small thought here.  I would have brought it up eventually,
probably after some experimentation, this has given me the chance:

I like the /boot idea.  I'd like it even more if its contents could
be discarded, or maybe made kernel-loadable for real convenience,
but as it stands it is already pretty cool.

In fact, my thinking was that one may be able to construct an AUTH
kernel with its entire complement of tools in /boot, and only the
auth data on disk outside the kernel.  As I mentioned, I was going
to try this out before bringing it up, but perhaps somebody else
wants to give it a try while I'm busy with other, more mundane
activities.

Given such an option, I'd also rather keep the mandatory information
in plan9.ini and its complexity to a bare minimum.  If I understood
Nemo's proposal, it attempts to move as much out of /boot as can
be described by some option in plan9.ini.  Of itself, the idea has
its own merits, but it seems to me to suggest that /boot should be
deprecated, whereas I believe its possibilities should be explored
further instead.

++L