GNU bug report logs - #27007
'menu-entry' disappeared from the bootloader API

Previous Next

Full log

View this message in rfc822 format

From: ludo <at> gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: Tomáš Čech <sleep_walker <at> gnu.org>, Mathieu Othacehe <m.othacehe <at> gmail.com>, 27007 <at> debbugs.gnu.org
Subject: bug#27007: boot-parameters are not documented
Date: Fri, 26 May 2017 10:47:02 +0200

Danny Milosavljevic <dannym <at> scratchpost.org> skribis:

> On Tue, 23 May 2017 10:13:11 +0200 ludo <at> gnu.org (Ludovic Courtès)
> wrote:
>> Can we assume that all the bootloaders have a notion of “menu” and
>> “menu entries”?
>
> I think so.
>
> But there are bootloaders that [also can] do the traditional thing:
> When you select an entry, it can chainload the bootsector of that
> partition.  For example Grub can do that.  We don't support that use
> case yet.  Grub can also load Windows NT bootloader directly or
> chainload an UEFI file etcetc - there are actually a lot of different
> kinds of "menu entries" even with the same bootloader.

Right, but this is about the content of the menu entry.  If we want to
support that, we can provide an “escape hatch” in the ‘menu-entry’
object, which would be a string that goes as-is in the bootloader’s
config file.

I wonder if we should support everything you mention though.  OTOH it
would not feel right if we can’t load other free operating systems like
FreeBSD, etc.  Maybe we should just start with support for GNU variants
only and improve it later as people ask for it.

Thoughts?

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.