From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46414) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d869Q-0000GK-Jg for guix-patches@gnu.org; Tue, 09 May 2017 10:30:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d869L-0000fp-Ju for guix-patches@gnu.org; Tue, 09 May 2017 10:30:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:59850) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d869L-0000f9-Fs for guix-patches@gnu.org; Tue, 09 May 2017 10:30:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1d869L-0003J1-3w for guix-patches@gnu.org; Tue, 09 May 2017 10:30:03 -0400 Subject: bug#26339: [PATCH 02/18] system: Add extlinux support. Resent-Message-ID: References: <20170402135242.2958-1-m.othacehe@gmail.com> <20170402135242.2958-2-m.othacehe@gmail.com> <87mvanjepx.fsf@gnu.org> <871sryqy3g.fsf@gmail.com> <87bmr29x4q.fsf@gnu.org> From: Mathieu Othacehe In-reply-to: <87bmr29x4q.fsf@gnu.org> Date: Tue, 09 May 2017 16:30:28 +0200 Message-ID: <864lwuje63.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 26339@debbugs.gnu.org, David Craven > Woow, that was fast! :-) I had time to kill during a train trip :) > Good question! I guess we need to store the name of the bootloader type > in the “parameters” file, and then look it up upon switch-generation? > But maybe we also need to store a reference to the bootloader package so > that it isn’t GC’d? We have three options for switch-generation : 1. Do not reinstall bootloader, only update config (current behaviour). -> It was ok with one bootloader, it's more problematic with multiple bootloaders. For example switching between two generations with two different bootloaders. 2. Save the bootloader type in "parameters" and reinstall bootloader (current bootloader build, not necessarily the one used when creating this generation) -> It's the option I choose in my series. 3. Same as 2. but also save bootloader used (store reference) and add a gc-root to keep it around. I can try to implement option 3 if you're ok ? > No better idea, sounds like a good start. > Ok. > I think the most important is to make sure that our current use case, > where people always use GRUB, doesn’t break. With my basic-one-unencrypted-partition setup it work fine, but it would be great if people with more complex setup could try this serie :) Thanks, Mathieu