9front - general discussion about 9front
 help / color / mirror / Atom feed
From: petter9@bissa.eu
To: 9front@9front.org
Subject: Re: [9front] Booting with encrypted partitions
Date: Wed, 20 Nov 2019 13:58:15 +0100	[thread overview]
Message-ID: <ffa47566-1a82-fa3e-919f-ac099725f0e4@bissa.eu> (raw)
In-Reply-To: <6D03C80655D49FAF0B96B481DCDEFA30@eigenstate.org>

I like having the hook before the loop now too, as cinap suggested.  In 
the scenario of a user having a partition decryption command in this 
hook and aborting the password prompt; they can now try their different 
boot options without having an annoying password prompt appearing all 
the time.  (The prompt is just a reboot away should they want it again.)

diff -r 8f9f3ee2eacf sys/src/9/boot/bootrc
--- a/sys/src/9/boot/bootrc	Mon Nov 11 13:35:47 2019 -0800
+++ b/sys/src/9/boot/bootrc	Wed Nov 20 11:55:12 2019 +0100
@@ -186,6 +186,12 @@
  # add partitions and binds
  configlocal
  
+# execute hook 'startcmd' from plan9.ini
+if(! ~ $#startcmd 0) {
+	echo $startcmd
+	eval $startcmd
+}
+
  while(){
  	@{main}



I went with 'startcmd', which is still open for debate..


I can help with updating the fqa if something like this patch is committed.


Come to think of; there's also the possibility of having a bootrc.local 
(mimicking termrc and cpurc).  I actually think that seems like a better 
path going forward, but i haven't made any attempts at that.


--
Petter


  parent reply	other threads:[~2019-11-20 12:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13  5:07 ori
2019-11-13 11:45 ` hiro
2019-11-20 12:58 ` petter9 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-12 21:54 cinap_lenrek
2019-11-12 23:51 ` petter9
2019-11-12 20:57 ori

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=ffa47566-1a82-fa3e-919f-ac099725f0e4@bissa.eu \
    --to=petter9@bissa.eu \
    --cc=9front@9front.org \
    /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).