From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: Re: How does install-grub work? Date: Mon, 29 Aug 2016 23:57:35 +0200 Message-ID: <20160829235735.7e48bf1b@scratchpost.org> References: <20160822132018.19828-1-david@craven.ch> <20160822132018.19828-6-david@craven.ch> <20160827104228.5db67f6a@scratchpost.org> <20160829123149.0e260af6@scratchpost.org> <20160829161919.5277eb35@scratchpost.org> <20160829201656.4390d2db@scratchpost.org> <20160829205734.0b49dc92@scratchpost.org> <20160829225056.240c8d0e@scratchpost.org> 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]:48468) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1beUYs-0007YH-AV for guix-devel@gnu.org; Mon, 29 Aug 2016 17:57:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1beUYo-0004m2-8z for guix-devel@gnu.org; Mon, 29 Aug 2016 17:57:45 -0400 Received: from dd1012.kasserver.com ([85.13.128.8]:52364) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1beUYo-0004lw-1w for guix-devel@gnu.org; Mon, 29 Aug 2016 17:57:42 -0400 In-Reply-To: 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: David Craven Cc: guix-devel Hi, On Mon, 29 Aug 2016 23:19:30 +0200 David Craven wrote: > 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. Yes. Note that Ludo said that it might make sense to separate the build side (gnu/build/install.scm and gnu/build/vm.sc) from the host side (other stuff) also for the patches. > 2. Add your extlinux.conf generation/install code. Yes. This one is the most important part. On the other hand, Part 3 below is actually not that important even for actual ARM hardware. Usually U-Boot is there when you buy it anyway - usually there's no need to fiddle with it directly. > 3. We can still add an install uboot to MBR procedure if it's necessary. Sometimes MBR, sometimes random location in the middle of nowhere with a magical sector number. There's still a "FIXME" in gnu/build/install.scm install-bootloader about how to detect on the build side which bootloader to use and then call either install-grub or install-u-boot. I don't know how to do that. I've asked before about whether it's (1) possible and (2) desireable to just compare the config-filename to "extlinux.conf" and hardcode u-boot then. But *which* u-boot package does it use? How would it know? This is a very important part that is both missing and necessary - and I've not found an answer to that so far. > This would break the changes down into easy to review patches and subgoals... Yes, I agree that that would be good.