From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Booting with encrypted partitions
Date: Wed, 13 Nov 2019 12:45:43 +0100 [thread overview]
Message-ID: <CAFSF3XOwKoZZs8oDq390T7zXLvp5j9FO780iywN0x1o_ZmyfTw@mail.gmail.com> (raw)
In-Reply-To: <6D03C80655D49FAF0B96B481DCDEFA30@eigenstate.org>
if more ideas are needed:
perhaps refer to the next thing it precedes: "pre-bootprompt" ?
doesn't seem to be convention here, but i like that on other OS's the
order of execution is sometimes visible e.g. by having a number
prefixed, or in the style of pre-something/post-something scripts or
interface-up/interface-down....
next prev parent reply other threads:[~2019-11-13 11:45 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 [this message]
2019-11-20 12:58 ` petter9
-- 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=CAFSF3XOwKoZZs8oDq390T7zXLvp5j9FO780iywN0x1o_ZmyfTw@mail.gmail.com \
--to=23hiro@gmail.com \
--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).