From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <s.ivanov@proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (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 lists.proxmox.com (Postfix) with ESMTPS id 88A207647D for <pve-devel@lists.proxmox.com>; Fri, 23 Apr 2021 11:05:06 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6C4D125956 for <pve-devel@lists.proxmox.com>; Fri, 23 Apr 2021 11:05:06 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (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 firstgate.proxmox.com (Proxmox) with ESMTPS id C4DED25934 for <pve-devel@lists.proxmox.com>; Fri, 23 Apr 2021 11:05:04 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 9E97644F81 for <pve-devel@lists.proxmox.com>; Fri, 23 Apr 2021 11:05:04 +0200 (CEST) From: Stoiko Ivanov <s.ivanov@proxmox.com> To: pve-devel@lists.proxmox.com Cc: Thomas Lamprecht <t.lamprecht@proxmox.com> Date: Fri, 23 Apr 2021 11:04:50 +0200 Message-Id: <20210423090451.2279-9-s.ivanov@proxmox.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20210423090451.2279-1-s.ivanov@proxmox.com> References: <20210423090451.2279-1-s.ivanov@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH pve-kernel-meta v2 8/8] proxmox-boot: run p-b-t refresh on update-grub X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Fri, 23 Apr 2021 09:05:06 -0000 If the system seems to be using proxmox-boot, simply run it, in addition to warning the user about the situation. Since the warning is only printed when update-grub is not called by dpkg or proxmoxmox-boot-tool, this should be safe, and potentially help keeping systems bootable. Suggested-by: Thomas Lamprecht <t.lamprecht@proxmox.com> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com> --- v1->v2: * newly added (as an optional addition - feel free to not apply it) proxmox-boot/000_proxmox_boot_header | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/proxmox-boot/000_proxmox_boot_header b/proxmox-boot/000_proxmox_boot_header index e230aef..c7bcff6 100755 --- a/proxmox-boot/000_proxmox_boot_header +++ b/proxmox-boot/000_proxmox_boot_header @@ -15,8 +15,10 @@ if proxmox-boot-tool status --quiet; then if [ -z "$DPKG_RUNNING_VERSION" ] && [ -z "$PVE_EFIBOOT_UNSHARED" ]; then warn "W: This system is booted via proxmox-boot-tool:" warn "W: Running update-grub does not update the correct config!" - warn "W: Run 'proxmox-boot-tool refresh' instead." + warn "W: Running: 'proxmox-boot-tool refresh'." warn "" + + proxmox-boot-tool refresh fi fi -- 2.20.1