From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <9FCAC89628E7DA56F0E59971CDEC4D38@felloff.net>
Date: Sun,  5 May 2019 17:11:19 +0200
From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
In-Reply-To: CAJQ9t7hpU-8PYrsVbJ6hJqewVpw7RWnm=774DQOGftuH_8snOg@mail.gmail.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
Topicbox-Message-UUID: fff56b62-ead9-11e9-9d60-3106f5b1d025

> Next plan9.ini's "rootdir". It is no longer documented in
> plan9.ini(8), but the little code that uses it in bootrc is odd as
> well as at odds with the legacy documentation.

yes! we got it all wrong! it all makes sense in the /lib/namespace
what should happen, but bootrc does it wrong.

> My hope was to give it "9front" as a value and have Fossil serve
> that as the root for a diskless 9front workstation, as in

>      bind -b $rootdir /

> Instead, I find "mount -c /srv/boot $rootdir" which is definitely not
> it.

you are absolutely correct. this is wrong. here is the fix:

http://code.9front.org/hg/plan9front/rev/1209e04a3af9

> I'm not sure under what circumstances one target a different
> location for the ROOT directory, I would be interested to hear. Of
> course, this conflict needs to be resolved.

> This is starting to get interesting.

yeah. thank you very much! :-)

> Lucio.

--
cinap