From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 8297B158020 for ; Thu, 8 Dec 2022 20:55:47 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1CCEEE08FC; Thu, 8 Dec 2022 20:55:43 +0000 (UTC) Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 91C6CE08E0 for ; Thu, 8 Dec 2022 20:55:42 +0000 (UTC) Received: by mail-lj1-x22b.google.com with SMTP id s10so2899186ljg.1 for ; Thu, 08 Dec 2022 12:55:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=cqO0ZVqFviYvG1GivzjTYK59YGCR11P7PugMrG/IxOs=; b=C8mGu29o4/Wu+YCpg3nC7Kz180rBV0xMGtZt7glsiLJ5HYFDq4M0Y3fHJFJEDElUuM afsrqAi9LY0mmyfepuXXI3FbI+QmRLcxlB6iTag5BSTuMGuBrbrSUe3WcG3DSRku7Jxo A4ahwHxPEOBEGfS0FpZ/PnPktLio4aqpCaLXzRcZBPD3csNLjd6lCntN/urzIOVuHkpP tUyX6jUYDTRrsWKyKFkouDA1/YqmlN3Y+5iwOiCg1bVrE2UAalOUaM/tfnUnfQRBlp6K Jf9Fcw2E/DmFFnbmhS1JpKBTmUKwhFBQLKUgY0DsV1D/zZapuAfp0StkBFST8RhgQx+c qt+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=cqO0ZVqFviYvG1GivzjTYK59YGCR11P7PugMrG/IxOs=; b=CtMb9V0k9XOH114JQsvTtG5WLT4acVbbkWTt9bCMkv7B4nHc0gV18dsK1Dwtxq1QIE Njtevz1vcfp7ZczR9qF3wlNlY3Yk8rOMbUDSghMI/DA+vKXjXTGWNuFXVeqA3eCQ4K32 3V3UPxdf+Pc3r/oYuecAtU9U3F3/D8N5zHkasJlBXtjQgl3KNc5ScuWZQVjovMGUJ0eQ RL4u8laIAAxhzO8r8kmqA1kT7qMQlcT6hzgvWCqYtYxs5nN4bbyQVJa8BUgbzbFXw1Pd kgmWapOB7CUFsThexWFL0uOya1BUEHLSyZhwCCyKue8rSKOIBAc3857cCVYUKmvzTihU eo8g== X-Gm-Message-State: ANoB5pm3lRpgdUxy46lsi58afSmryvr/BxbCCRultVZu98jiWSDtk64+ X5leauUljMRx/BM9vGKv5UMfuxDe29VrD5M2gpk2fMQk X-Google-Smtp-Source: AA0mqf6bt7Y/uuI/GCbgYjyoMSQMLaWUKFgoJuigxQAExpTxgnq8o7bm221ERjucH37ue9dqz0VBm3dDIm2TeRCzwew= X-Received: by 2002:a2e:9d4e:0:b0:278:d139:74be with SMTP id y14-20020a2e9d4e000000b00278d13974bemr30239767ljj.162.1670532941012; Thu, 08 Dec 2022 12:55:41 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 From: Mark Knecht Date: Thu, 8 Dec 2022 13:55:30 -0700 Message-ID: Subject: [gentoo-user] Duel boot - How to verify boot loader updates? To: Gentoo User Content-Type: multipart/alternative; boundary="00000000000088e22205ef5742c3" X-Archives-Salt: ae18afc3-0eaa-47df-85bc-e24db980f63c X-Archives-Hash: c13ad9125391b5dd5a6bf91174328ef4 --00000000000088e22205ef5742c3 Content-Type: text/plain; charset="UTF-8" Hi, This is a bit of a conceptual question, simplified but based on a machine I do own, from someone who knows very little about boot loader implementations. (I.e. - me) Thanks in advance for any pointers you can provide. Assume a machine with two separate M.2 SSDs. The M.2 devices are identical in size and from the same manufacturer. For the sake of discussion they are partitioned identically and they both have the same distro installed. One is stable, the other is bleeding edge. For simplicity there are no other disk drives involved in either installation. Both installs have the same boot loader, grub2 I guess, and both have configurations that boot themselves by default but offer the other drive as a second option. Assume the bleeding edge system (or the other - it doesn't matter to me) gets a grub2 update, and further assume the update is either automatic or done by someone other than yourself. Whoever did the updates 'tests' the machine by booting into both versions, and both versions are tested as default in BIOS so that no matter what everything appears to be working. THE QUESTION: After the fact, if I wanted to look at the two installations in detail, how would I determine that the grub update was done to the installation doing the update and not done to the other (nearly) identical installation? Thanks in advance, Mark --00000000000088e22205ef5742c3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
=C2=A0 =C2=A0This is a bit of a conceptual questio= n, simplified but based on a machine I do own, from someone who knows very = little about boot loader implementations. (I.e. - me) Thanks in advance for= any pointers you can provide.

=C2=A0 =C2=A0Assume= a machine with two separate M.2 SSDs. The M.2 devices are identical in siz= e and from the same manufacturer. For the sake of discussion they are parti= tioned identically and they both have the same distro installed. One is sta= ble, the other is bleeding=C2=A0edge. For simplicity there are no other dis= k drives involved in either installation. Both installs have the same boot = loader, grub2 I guess, and both have configurations that boot themselves by= default but offer the other drive as a second option.

=
=C2=A0 =C2=A0Assume the bleeding=C2=A0edge system (or the other - it d= oesn't matter to me) gets a grub2 update, and further assume the update= is either automatic or done by someone other than yourself. Whoever did th= e updates 'tests' the machine by booting into both versions, and bo= th versions are tested as default in BIOS so that no matter what everything= appears to be working.

=C2=A0 =C2=A0THE QUESTION:= After the fact, if I wanted to look at the two installations in detail, ho= w would I determine that the grub update was done to the installation doing= the update and not done to the other (nearly) identical installation?

Thanks in advance,
Mark
--00000000000088e22205ef5742c3--