From: ludo@gnu.org (Ludovic Courtès)
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 1/2] system: Rename grub to bootloader.
Date: Sat, 14 Jan 2017 18:40:05 +0100 [thread overview]
Message-ID: <87ziitleve.fsf@gnu.org> (raw)
In-Reply-To: <CAL1_im=qT68BGm5vqtRX6r6O2ZKpwqaSVe1rqo-ScMTQ9R91=g@mail.gmail.com> (David Craven's message of "Thu, 12 Jan 2017 15:45:53 +0100")
David Craven <david@craven.ch> skribis:
> I need to study for my exams the next week or two, but my current
> thinking on the next steps to accomplish the goal of being bootloader
> agnostic are:
>
> 1. discard <menu-entry> in gnu/system/grub in favor of
> <boot-parameters> from gnu/system - small api changes
Not sure what you mean. <boot-parameters> is an internal things,
whereas <menu-entry> is what users manipulate.
> 2. focus on the code in gnu/system/vm.scm and gnu/build/vm.scm. A lot
> of decisions are being made about the qemu package, the qemu flags,
> the file-system, the bootloader, the architecture and the kernel etc.
> that should be moved elsewhere. - will affect guix/scripts/system and
> probably the system tests infrastructure, the existing api should be
> kept to avoid breakage in those parts.
Agreed.
Ludo’.
next prev parent reply other threads:[~2017-01-14 17:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 18:42 [PATCH 1/2] system: Rename grub to bootloader David Craven
2017-01-10 18:42 ` [PATCH 2/2] scripts: system: Rename --no-grub option to --no-bootloader David Craven
2017-01-10 23:10 ` Danny Milosavljevic
2017-01-11 8:23 ` David Craven
2017-01-10 18:51 ` [PATCH 1/2] system: Rename grub to bootloader David Craven
2017-01-12 14:14 ` Ludovic Courtès
2017-01-12 14:45 ` David Craven
2017-01-14 17:40 ` Ludovic Courtès [this message]
2017-01-13 6:06 ` Chris Marusich
2017-01-10 23:01 ` Danny Milosavljevic
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=87ziitleve.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=david@craven.ch \
--cc=guix-devel@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.