From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Craven <david@craven.ch>
Subject: Re: How does install-grub work?
Date: Mon, 29 Aug 2016 23:19:30 +0200
Message-ID: <CAL1_immJZ-FZXOQE6-2_b0PWq4B-MA1ZtAoLxSpFg4hPfFT2-A@mail.gmail.com>
References: <CAL1_im=EbswNGRYfBX+N=fhNqX3GjTZVbmyO6kObnTPkDN7vfg@mail.gmail.com>
	<20160822132018.19828-1-david@craven.ch>
	<20160822132018.19828-6-david@craven.ch>
	<20160827104228.5db67f6a@scratchpost.org>
	<CAL1_imn2JcqFo2TxM9jaQotUkR-fRQ9ncZqi8-QYv4qYiZB5og@mail.gmail.com>
	<20160829123149.0e260af6@scratchpost.org>
	<CAL1_imk6zoGVChd==hJDDCOQwOJKtaUeAGxoOPthkwCZhmKCAQ@mail.gmail.com>
	<CAL1_im=B39fMN2TcUvdUtmQcZVq4YZS-FrqnP6rgTQ2s_iBxAw@mail.gmail.com>
	<20160829161919.5277eb35@scratchpost.org>
	<CAL1_imnsQSMSLg4ibN+zdo4KYFo+Ds=C9tNGpQtdRx+SnM3hrg@mail.gmail.com>
	<20160829201656.4390d2db@scratchpost.org>
	<CAL1_im=WOZ9K8grPA7jqxUk6wnpjWfq7PoN55Qss+G6pN_vKCg@mail.gmail.com>
	<20160829205734.0b49dc92@scratchpost.org>
	<CAL1_im=6UScmG31OMLZLn_XWzBaoNv=aoTjROy9Xu1nP0XVTVA@mail.gmail.com>
	<20160829225056.240c8d0e@scratchpost.org>
	<CAL1_immEYuftUMvopXCWpkQjpZO2DiHa57EAncCWBFJAouc2eA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:40330)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <david@craven.ch>) id 1beTxy-0005P9-8A
	for guix-devel@gnu.org; Mon, 29 Aug 2016 17:19:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <david@craven.ch>) id 1beTxu-00064n-2B
	for guix-devel@gnu.org; Mon, 29 Aug 2016 17:19:37 -0400
Received: from mail-yw0-x233.google.com ([2607:f8b0:4002:c05::233]:34904)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <david@craven.ch>) id 1beTxs-00064K-Pi
	for guix-devel@gnu.org; Mon, 29 Aug 2016 17:19:33 -0400
Received: by mail-yw0-x233.google.com with SMTP id j12so119979ywb.2
	for <guix-devel@gnu.org>; Mon, 29 Aug 2016 14:19:31 -0700 (PDT)
In-Reply-To: <CAL1_immEYuftUMvopXCWpkQjpZO2DiHa57EAncCWBFJAouc2eA@mail.gmail.com>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel <guix-devel@gnu.org>

> Does the u-boot bootloader routine have to do anything other than
> generating the extlinux.conf file? That would be enough so that there
> is an alternative to grub-install for the qemu use case and for actual
> boards, isn't uboot usually written to flash instead of to a MBR?

So I'd say the next steps are:

1. Pick out your changes that are related to renaming grub to
bootloader and add a shim for the uboot parts. That should be enough
to get vm's booting.

2. Add your extlinux.conf generation/install code.

3. We can still add an install uboot to MBR procedure if it's necessary.

This would break the changes down into easy to review patches and subgoals...