From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40621) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d99XH-0008B7-68 for guix-patches@gnu.org; Fri, 12 May 2017 08:19:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d99XC-00010E-Oh for guix-patches@gnu.org; Fri, 12 May 2017 08:19:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:37215) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d99XC-0000za-LJ for guix-patches@gnu.org; Fri, 12 May 2017 08:19:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1d99XC-0007sN-2x for guix-patches@gnu.org; Fri, 12 May 2017 08:19:02 -0400 Subject: bug#26339: [PATCH 02/18] system: Add extlinux support. Resent-Message-ID: MIME-Version: 1.0 In-Reply-To: <87k25ms3wi.fsf@gnu.org> 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> <864lwuje63.fsf@gmail.com> <87inl9zruw.fsf@gnu.org> <20170512020243.5af54ed2@scratchpost.org> <87d1betr8y.fsf@gnu.org> <20170512132630.1eeb75bc@scratchpost.org> <87k25ms3wi.fsf@gnu.org> From: Mathieu Othacehe Date: Fri, 12 May 2017 14:18:37 +0200 Message-ID: Content-Type: multipart/alternative; boundary="94eb2c0d4530845325054f52b4ef" 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 --94eb2c0d4530845325054f52b4ef Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi ! > So it should probably pick the current (not the newest) bootloader type. I'm not fan of installing every bootloader config because it means multiple gcroots and filling /boot with possibly useless stuff. However, reading the "parameters" of current system, extracting bootloader type, and reinstalling *only* the bootloader configuration file for this type seems a good idea to me. I'll use this solution for v4. Plus we can come up later with a more intelligent solution, storing bootloader store path in "parameters" and creating a gcroot for it. Thanks, Mathieu 2017-05-12 13:36 GMT+02:00 Ludovic Court=C3=A8s : > Hi, > > Danny Milosavljevic skribis: > > > On Fri, 12 May 2017 10:26:53 +0200 > > ludo@gnu.org (Ludovic Court=C3=A8s) wrote: > > > >> > If there is a switch between extlinux and grub, the bootloader confi= g > file format (and name, too) will change. > >> > > >> > So if you do switch the config file out but don't switch the actual > bootloader out it will not boot, right? > >> > >> Unless you regenerate the bootloader=E2=80=99s config file upon > >> =E2=80=98switch-configuration=E2=80=99. > > > > Yes, for the last-guix-installed bootloader (presumably the > still-installed one). Good point. > > > > That would mean only the bootloader type of the newest system generatio= n > would be checked - also when restoring older generations. > > > > Can the newest system generation be deleted? Then eventually Guix coul= d > read the wrong bootloader type (of a bootloader which isn't actually > installed at the time). > > The newest generation can be deleted, but the current one cannot (it=E2= =80=99s > possible that the current one is not the newest if you picked an old > entry in the boot menu.) > > So it should probably pick the current (not the newest) bootloader type. > > Ludo=E2=80=99. > --94eb2c0d4530845325054f52b4ef Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi !

> So it should probably pick the current (n= ot the newest) bootloader type.

I'm not fan of installing every = bootloader config because it means
multiple gcroots and filling /boot wi= th possibly useless stuff.

However, reading the "parameters&quo= t; of current system, extracting
bootloader type, and reinstalling *only= * the bootloader configuration
file for this type seems a good idea to m= e.

I'll use this solution for v4. Plus we can come up later with= a more
intelligent solution, storing bootloader store path in "par= ameters" and
creating a gcroot for it.

Thanks,

Mathie= u


20= 17-05-12 13:36 GMT+02:00 Ludovic Court=C3=A8s <ludo@gnu.org>:
=
Hi,

Danny Milosavljevic <dannym@sc= ratchpost.org> skribis:

> On Fri, 12 May 2017 10:26:53 +0200
> ludo@gnu.org (Ludovic Court=C3=A8s= ) wrote:
>
>> > If there is a switch between extlinux and grub, the bootloade= r config file format (and name, too) will change.
>> >
>> > So if you do switch the config file out but don't switch = the actual bootloader out it will not boot, right?
>>
>> Unless you regenerate the bootloader=E2=80=99s config file upon >> =E2=80=98switch-configuration=E2=80=99.
>
> Yes, for the last-guix-installed bootloader (presumably the still-inst= alled one).=C2=A0 Good point.
>
> That would mean only the bootloader type of the newest system generati= on would be checked - also when restoring older generations.
>
> Can the newest system generation be deleted?=C2=A0 Then eventually Gui= x could read the wrong bootloader type (of a bootloader which isn't act= ually installed at the time).

The newest generation can be deleted, but the current one cannot (it= =E2=80=99s
possible that the current one is not the newest if you picked an old
entry in the boot menu.)

So it should probably pick the current (not the newest) bootloader type.
Ludo=E2=80=99.

--94eb2c0d4530845325054f52b4ef--