From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: Re: How to use custom grub? Date: Thu, 3 Nov 2016 17:50:51 +0100 Message-ID: <20161103175051.1588de9f@scratchpost.org> References: <8737j85yek.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47600) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c2LED-0005Fd-5S for guix-devel@gnu.org; Thu, 03 Nov 2016 12:51:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c2LEA-0000AQ-1r for guix-devel@gnu.org; Thu, 03 Nov 2016 12:51:01 -0400 Received: from dd1012.kasserver.com ([85.13.128.8]:33931) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c2LE9-0000A2-KA for guix-devel@gnu.org; Thu, 03 Nov 2016 12:50:57 -0400 In-Reply-To: <8737j85yek.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Marius Bakke Cc: guix-devel@gnu.org Hi Marius, yeah, I've noticed that problem, too. David and I got some steps in the direction of fixing it (for U-Boot support): The U-Boot support patch generalized this, see my E-Mail to this list, subject "[WIP PATCH] gnu: add U-Boot support to operating-system" on 09 Sep 2016 at 20:09. The relevant part is: - guix/scripts/system.scm: The "install" routine is changed to also accept the bootloader package as argument (variable is called "grub" to keep the number of trivial patch chunks low). - guix/scripts/system.scm: The new "install-bootloader*" routine is introduced instead of "install-grub*" to also accept the bootloader package as argument. If you want you can cherry-pick these changes. I've reconfigured and booted with that patch. It works. I'm not sure how the build side picks up which package's grub-install is invoked (gnu/build/install.scm just invokes "grub-install" without any further path specification). I've asked about it before (multiple times now) and apparently nobody knows. If someone finds out, gnu/build/install.scm install-grub after the patch accepts the grub-name and could just invoke grub-install correctly. I *think* it's fine to just (string-append grub-name "/bin/grub-install") or something - but that's something I don't want to guess. David knows more about the VM side - the patch also addresses this by carring around the bootloader als variable "grub" (which is not necessarily actually grub). I hope that helps.