From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:39448)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1d8y31-0007Cx-5k
	for guix-patches@gnu.org; Thu, 11 May 2017 20:03:08 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1d8y2w-0008Ry-6D
	for guix-patches@gnu.org; Thu, 11 May 2017 20:03:07 -0400
Received: from debbugs.gnu.org ([208.118.235.43]:36739)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1d8y2w-0008Rs-2L
	for guix-patches@gnu.org; Thu, 11 May 2017 20:03:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1d8y2v-0003S0-Qz
	for guix-patches@gnu.org; Thu, 11 May 2017 20:03:01 -0400
Subject: bug#26339: [PATCH 02/18] system: Add extlinux support.
Resent-Message-ID: <handler.26339.B26339.149454737013246@debbugs.gnu.org>
Date: Fri, 12 May 2017 02:02:43 +0200
From: Danny Milosavljevic <dannym@scratchpost.org>
Message-ID: <20170512020243.5af54ed2@scratchpost.org>
In-Reply-To: <87inl9zruw.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>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
List-Id: <guix-patches.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-patches>,
	<mailto:guix-patches-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-patches/>
List-Post: <mailto:guix-patches@gnu.org>
List-Help: <mailto:guix-patches-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-patches>,
	<mailto:guix-patches-request@gnu.org?subject=subscribe>
Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org
Sender: "Guix-patches" <guix-patches-bounces+kyle=kyleam.com@gnu.org>
To: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: 26339@debbugs.gnu.org

Hi,

On Tue, 09 May 2017 22:40:23 +0200
ludo@gnu.org (Ludovic Court=C3=A8s) wrote:

> > -> It was ok with one bootloader, it's more problematic with multiple =
=20
> > bootloaders. For example switching between two generations with two
> > different bootloaders. =20
>=20
> OTOH, if it turns out to be safer to keep the current bootloader, which
> is likely I think, then perhaps it=E2=80=99s best to not try to change.
>=20
> I mean, I prefer a rollback that doesn=E2=80=99t roll back the bootloader=
 over a
> rollback that tries to do something smart and makes the system
> unbootable.

If there is a switch between extlinux and grub, the bootloader config file =
format (and name, too) will change.

So if you do switch the config file out but don't switch the actual bootloa=
der out it will not boot, right?

That means we have to take care that this doesn't happen.

I still think an easy way would be to just always install the config files =
for all the bootloaders that we support.  That way if there is a bootloader=
 that knows any of the configs, it will boot.  Can't think of a downside ei=
ther.