From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: GRUB fallback mechanism [was Re: Brain storming cool Guix features] Date: Fri, 11 Jan 2019 17:32:12 -0500 Message-ID: <20190111223212.GA31011@jasmine.lan> References: <87bm4wwrku.fsf@dismail.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="gBBFr7Ir9EOA20Yy" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:41742) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gi5Lc-00062Q-VG for guix-devel@gnu.org; Fri, 11 Jan 2019 17:32:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gi5Lb-0001XF-T6 for guix-devel@gnu.org; Fri, 11 Jan 2019 17:32:16 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:60189) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gi5Lb-0001X4-KX for guix-devel@gnu.org; Fri, 11 Jan 2019 17:32:15 -0500 Content-Disposition: inline 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: L p R n d n Cc: guix-devel@gnu.org --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jan 07, 2019 at 05:48:39PM +0100, L p R n d n wrote: > - Currently, I think the only way for a GuixSD installation to break is > if something goes wrong with the bootloader. Might be nice to have a > tool (in the install image I suppose) to recover the bootloader. > Maybe 'guix system init' can deal with that king of cases for now, I > don't know, but a dedicated command might be able to use the original > store, restore previous generations etc. Apparently GRUB has a feature that records a "fallback" system to boot if booting fails. Maybe when reconfiguring, Guix could set the current system as the fallback so that it would always boot. If we did that, we'd want to warn the user somehow... not sure how to achieve that. Discussion of this feature at NixOS: https://github.com/NixOS/nixpkgs/issues/26332 --gBBFr7Ir9EOA20Yy Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlw5GWwACgkQJkb6MLrK fwgl/BAAriRwzntC2vl9koZ7m5Z2OwsXa9B10xdTPxpJ9Wu0jXj/UzcVsIyiUj3z 3XH7Pl4b0kWmO2vqupwr7LGsVethgKQOk5lDYVtALfFSv2a9ffmIqlU1HG9N83t0 0MFfYYbjbFFL/oN1t+UWgln6eb/EZXfIguKc/Hgtve5hDLNrQzcKPhOSheOVDEyc Eaa5tz498L+q9iE9uv1XOvd6Dxv8VA8YnYQLsLsyPpaJvhVNJ0zSlJiYHCyPRbMt yYSmnMrUjq45CXRTRFm11i1fu3YL4VCc9lBQGJN7S1CW7fUFB5pFvrRcWUEgALop YNueVn6QI3IkM5v/YbEmSaQ1VzVEWbKXSE/DuCRcX3NFE6bEft++1QvDBqacDfJG vWV8ugRsquEssr08w2ZuZKHr4QelKP2fyrMyXpFTxtqhsUHgKAjdDdf5ESJNpVP1 420xMOcVTuAHTeSzoqgz9K8/tq7kgTfYZKtTj3nL9x27LPB8yNQ8rEkWtGqPNt7E h9T8by9dymsXp0GWnd2gb3kQ2qjNRciUBoPdzJWQMIzvlDWoKnbN9qVWXIziG8dV 2vtb6L2LcJECitF7WC8fbwTRdsohXweMBZb+kvWf9K7XxHSXOQ2BMU06wTGIOJvh VJ8aY/4NfYczLy5Ga5OFJd8SubeQjkho9rd3IGhEdzucFZyqNy8= =UzYp -----END PGP SIGNATURE----- --gBBFr7Ir9EOA20Yy--