From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] The lost (9front) boot menus ...
Date: Sat, 20 Apr 2019 08:33:34 -0400 [thread overview]
Message-ID: <eab5f564-3deb-45bc-881f-bb6f7567a48b@www.fastmail.com> (raw)
In-Reply-To: <CAFSF3XO=oKktz+T2ybr82wF4B=2c5D6cx6KbS_6B23Mwiwu7Gg@mail.gmail.com>
9front boots via an initrd with a script, doesn't it? That script could be modified to present a menu/prompt, perhaps only if a certain variable is set in plan9.ini.
On Sat, Apr 20, 2019, at 2:42 AM, hiro wrote:
> hell. i have to do *exactly* the same with same dimension of timeouts
> slightly earlier for my bios to be allowed to select my boot disk,
> too. it's a totally common mechanism.
I hate all boot-time time-outs! I can understand why they exist, but at times my health makes them dreadful to actually use. Even when my health is good, it becomes a trial when rebooting repeatedly. A prompt helps, especially with hardware which refuses to recognize keys held down when the keyboard is initialized. I guess that's no longer common, but it was a horrible problem with the old hardware I had in the 90s. Then there was the problem where Lilo's prompt wouldn't display until 2 or 3 seconds into the timeout. I'm still not sure whether that was a problem with Lilo or the display hardware.
next prev parent reply other threads:[~2019-04-20 12:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 23:01 cinap_lenrek
2019-04-19 23:09 ` Lyndon Nerenberg
2019-04-20 0:33 ` Lyndon Nerenberg
2019-04-20 0:44 ` Kurt H Maier
2019-04-20 0:46 ` Lyndon Nerenberg
2019-04-20 1:39 ` hiro
2019-04-20 1:41 ` hiro
2019-04-20 12:33 ` Ethan Gardener [this message]
2019-04-20 22:15 ` hiro
2019-04-21 4:51 ` Lucio De Re
2019-04-21 11:09 ` hiro
2019-04-21 11:31 ` Lucio De Re
2019-04-21 11:37 ` hiro
-- strict thread matches above, loose matches on Subject: below --
2019-04-20 2:53 cinap_lenrek
2019-04-19 22:29 cinap_lenrek
2019-04-19 22:47 ` Lyndon Nerenberg
2019-04-19 22:12 Lyndon Nerenberg
2019-04-19 22:19 ` Nick Owens
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=eab5f564-3deb-45bc-881f-bb6f7567a48b@www.fastmail.com \
--to=eekee57@fastmail.fm \
--cc=9fans@9fans.net \
/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).