--98e8jtXdkpgskNou
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 23, 2003 at 03:25:23PM -0400, Thor Lancelot Simon wrote:
> On Thu, Oct 23, 2003 at 02:22:10PM -0500, Eric Haszlakiewicz wrote:
> >
> > 	well, my knee jerk reaction here is "deal with it.  the keys are
> > only one row apart".  On the other hand, I can understand how annoying
> > it can be to have to change a old ingrained behaviour.  If switching
> > F1-F4 and 1-4 makes the common case now more similar to the common case
> > before, then I'd say go ahead.
>=20
> I don't agree -- it's basically impossible to know what key combination
> on a serial console will generate what the bootselector thinks is "F1";
> on some terminals, *there may be no such key combination*.  I've had
> truly horrible experiences with this exact issue making it impossible to
> enter serial BIOS configuration screens without hooking up an actual AT
> keyboard.

Then that means that the current tool is still broken. While the current=20
tool doesn't use Fn often, it uses them to switch between drives. Which=20
still won't work well in the case you describe above.

It's our multi-boot tool. We can configure what each setting does, what=20
the default is, and what the timeout is. Would it be that hard to=20
configure the keys?

For serial console we really want 1-n for partitions and something else
(not F1-Fn) for drives. For my desktop, I want F1-Fn for partitions (I
don't really care about drives, but 1-n would work there). Some folk may
now like the current scheme.

Take care,

Bill

--98e8jtXdkpgskNou
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQE/mDU0Wz+3JHUci9cRArP8AJ9DPIhmIkubcdfGtiXi+fSAUe6j9ACeOX5F
5JjsiIViCOBxeZIKtbbtX6w=
=IXLK
-----END PGP SIGNATURE-----

--98e8jtXdkpgskNou--