From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <CAFSF3XObisA0didLCNmQ4uWO+_g=FXavw0ZY_JpeiFkSi-E9Sw@mail.gmail.com>
References: <FF95EBE4503DE11A2D55CCF361A6FFD8@felloff.net>
	<fd2fd8190522ab8e@orthanc.ca>
	<20190420004408.GA31225@wopr> <fd2fd8276bc91919@orthanc.ca>
	<CAFSF3XObisA0didLCNmQ4uWO+_g=FXavw0ZY_JpeiFkSi-E9Sw@mail.gmail.com>
From: hiro <23hiro@gmail.com>
Date: Sat, 20 Apr 2019 03:41:04 +0200
Message-ID: <CAFSF3XO=oKktz+T2ybr82wF4B=2c5D6cx6KbS_6B23Mwiwu7Gg@mail.gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [9fans] The lost (9front) boot menus ...
Topicbox-Message-UUID: fcd5b9a0-ead9-11e9-9d60-3106f5b1d025

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.

windows bootloader also always had that behavior for their
recovery/boot menus, just that you have to be more careful actually,
to use the correct key.