From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=)
Subject: bug#27007: boot-parameters are not documented
Date: Tue, 23 May 2017 14:24:54 +0200
Message-ID: <87shjvsquh.fsf@gnu.org>
References: <20170520200015.7lkqfgp5pju3clvf@penguin.suse.cz>
	<20170520225234.5414d304@scratchpost.org>
	<20170520210049.bvq4ztjzlrsaebbn@penguin.suse.cz>
	<877f18ubrs.fsf@gnu.org> <8760gsg5nn.fsf@gmail.com>
	<87zie4yors.fsf@gnu.org> <86r2zfkjhb.fsf@gmail.com>
	<87efvfyfz7.fsf@gnu.org> <86poezkdhl.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37631)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1dD8t3-0003jP-MX
	for bug-guix@gnu.org; Tue, 23 May 2017 08:26:07 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1dD8t0-00074B-Ae
	for bug-guix@gnu.org; Tue, 23 May 2017 08:26:05 -0400
Received: from debbugs.gnu.org ([208.118.235.43]:59701)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1dD8t0-000746-74
	for bug-guix@gnu.org; Tue, 23 May 2017 08:26:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1dD8sz-0000Is-V5
	for bug-guix@gnu.org; Tue, 23 May 2017 08:26:01 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.27007.B27007.14955423111106@debbugs.gnu.org>
In-Reply-To: <86poezkdhl.fsf@gmail.com> (Mathieu Othacehe's message of "Tue,
	23 May 2017 13:40:38 +0200")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 27007@debbugs.gnu.org

Mathieu Othacehe <m.othacehe@gmail.com> skribis:

>> and those entries would be =E2=80=9Clowered=E2=80=9D to <boot-parameters=
> somewhere.
>> That way we=E2=80=99d provide the abstraction level that users may expec=
t (=E2=80=9Chow
>> do I add a menu entry for my other distro?=E2=80=9D) and at the same tim=
e reduce
>> the risk of mistakes (=E2=80=9CI didn=E2=80=99t what to put in =E2=80=98=
store-device=E2=80=99 I put my
>> pet=E2=80=99s name there=E2=80=9D).
>>
>> WDYT?  :-)
>>
>
> It seems fine ! So to summarize, <menu-entry> would be moved to (gnu
> bootloader). A procedure menu-entry->boot-parameters would assure
> the mapping in (gnu bootloader).
>
> Each booloader in (gnu bootloader xxx), would add
> bootloader-configuration-menu-entries to generated entries.
>
> I'll be afk for a week, but I'll submit a patch and the updated
> documentation for this point when coming back.

Sounds like a good plan, thank you!

Ludo=E2=80=99.