From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from duke.felloff.net ([216.126.196.34]) by ewsd; Tue Nov 12 16:54:47 EST 2019
Message-ID: <2072D5F64C86C326359F41C953C1B7E6@felloff.net>
Date: Tue, 12 Nov 2019 22:54:37 +0100
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] Booting with encrypted partitions
In-Reply-To: B0E769F36C892538837A92242C2B2E77@eigenstate.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: wrapper TOR over YAML out-scaling information method-based rich-client manager 

notice that this mechanism has nothing specitic to
disk/cryptsetup and is just a hook to get arbitrary
code run.

which is *FINE*. just in the wrong place for something
like cryptsetup and has the wrong name.

you see the main function in bootrc can get run multiple
times. which is not what you'd want i think.

... also what Ori said, the empty test is wrong.

but otherwise i'm not against such a hook, which could
be usefull for other things as well.

probably do it right after the configlocal line in boorc.
(and dont forget the </dev/cons redirection to make
prompts work).

any suggestions for a good name? $start? $setup?
$autoexec? $DEVICEHIGH?

the name probably depends on what OTHER hooks we'r going
to add in some strategic places. any suggestions?

--
cinap