From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1oknRN-0006L0-Sh for mharc-grub-devel@gnu.org; Tue, 18 Oct 2022 10:19:33 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:49780) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oknQp-0006Ex-Kw for grub-devel@gnu.org; Tue, 18 Oct 2022 10:19:08 -0400 Received: from mo4-p01-ob.smtp.rzone.de ([81.169.146.167]:33417) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oknQl-0004qO-Qd for grub-devel@gnu.org; Tue, 18 Oct 2022 10:18:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1666102716; s=strato-dkim-0002; d=aepfle.de; h=References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Cc:Date: From:Subject:Sender; bh=vhiNBxZSYP3vilOtpXXi2VpwfooaHch2tx9V29uJbYc=; b=SCH6OGh1SevE4+QjYkiWEMFjXucx7SGL+u40cm+JiP/myWGtx7D9yfEQJw5ms4Q2BX ogNWGrZMPqzZT+ezU8px85Jfu8R5UCo9XBpfRCNDYTAwGYkftOv/s6Fy14aDVaadt2Fe UnfokEn1KxndP9YGB5ZgJoQE76RgaYFcM3D8nSecFllKycbiVJHkPRjvSg7r7MM9sL0R AG16wLKZNNkpSXXl5WhFoqy6MtlKip82gYFCgF+kfkKPSyVfMrONNCKP/sMEfMNFdd/p TbmHbgj1eWvIcq5Ssb5Xz5d+LJTuTnAfs+dEroBYalQI7Al9ufHt9ggVqheoelAikcNf UsiQ== Authentication-Results: strato.com; dkim=none X-RZG-AUTH: ":P2EQZWCpfu+qG7CngxMFH1J+3q8wa/QLpd5ylWvMDX2j/OiDv7LX1ITFkr8sRtLhQJY8wcRJ+GvY" X-RZG-CLASS-ID: mo00 Received: from sender by smtp.strato.de (RZmta 48.2.0 AUTH) with ESMTPSA id z9e8dfy9IEIZqTs (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Tue, 18 Oct 2022 16:18:35 +0200 (CEST) Date: Tue, 18 Oct 2022 16:18:21 +0200 From: Olaf Hering To: Denton Liu Cc: grub-devel@gnu.org, Daniel Kiper , Oskari Pirhonen , mathieu.desnoyers@efficios.com, rharwood@redhat.com, samuel.thibault@ens-lyon.org, debian-bsd@lists.debian.org, xen-devel@lists.xenproject.org Subject: Re: [PATCH v4] templates: introduce GRUB_TOP_LEVEL_* vars Message-ID: <20221018161821.149ee6fd.olaf@aepfle.de> In-Reply-To: References: <20221017103532.845293-1-liu.denton@gmail.com> <20221018131235.5e70f0bc.olaf@aepfle.de> X-Mailer: Claws Mail 20220819T065813.516423bc hat ein Softwareproblem, kann man nichts machen. MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/=pk9Y9LpQ6oa5YoIJDRURMY"; protocol="application/pgp-signature"; micalg=pgp-sha256 Received-SPF: none client-ip=81.169.146.167; envelope-from=olaf@aepfle.de; helo=mo4-p01-ob.smtp.rzone.de X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_NONE=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2022 14:19:19 -0000 --Sig_/=pk9Y9LpQ6oa5YoIJDRURMY Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Tue, 18 Oct 2022 06:57:36 -0700 Denton Liu : > If I'm understanding correctly, what you're proposing is a mechanism for > setting the default entry. If I'm not mistaken, this seems like an > orthogonal discussion to me. My patch proposes a method of setting the > top-level menu entry while this method only sets the default entry, > which may be hidden behind a submenu. I think this can be done already today. At least YaST offers a way to selec= t a specific item in a submenu and pass it to grub-set-default. This leads = to an entry like this in grubenv: saved_entry=3DAdvanced options for SLE15SP4 (with Xen hypervisor)>Xen hyper= visor, version 4.17.20220823T122205.399bcbf2-xen_unstable.150400.370>SLE15S= P4, with Xen 4.17.20220823T122205.399bcbf2-xen_unstable.150400.370 and Linu= x 5.14.21-150400.24.21-default This entry will be booted as long as both this specific Xen version and thi= s specific kernel version is found. There is a slim chance a SUSE specific = patch exists to enable this functionality. Maybe the patch description lacks a specific example how the proposed chang= e is supposed to be used in your environment. Olaf --Sig_/=pk9Y9LpQ6oa5YoIJDRURMY Content-Type: application/pgp-signature Content-Description: Digitale Signatur von OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE97o7Um30LT3B+5b/86SN7mm1DoAFAmNOta0ACgkQ86SN7mm1 DoALCg//dbAthIrUpj/CgWD2MVsYXsTcxEnduej/jcSyWMLfj8qeRCuNuMx03neD 3OMOhs/3nz6cnbp9fKv8421fP8qaUrgwn+meU6Er/r0bn08pGvlBBrNnetwrV/Sv FfFdXuemnaGTyDLmw3VNvTWGcHMZwGpASjdIPJd7OImLs4XBqO2zLlptCiP/nRCv bBAR3V8J3EbKjNtqqiZVrf1fFdAVNcbyB/0jQIewJ5Fv/lo+grg8Hx6YtchPvJlJ lcE42oQ7G637/HH8y9nZig1Tzm0jat7/WbmbM8wkSTBL0DM+rWeHI9H/85U9l9Sc fC7hq5LafaaTBmHyT6W3kK0anGArLrXB1ii4Cg7ZDz1ClpoXB042BeXujtpOzJMC pAi3uE/7qkVsZkL+TJa45Be47TbLT7MIIzyFpJNTOGmVwCeNkyqLiHAdYwTzojgG im++PkFocBq4w2+SLmSNlzLtbMIv3KufrjM0hTrJga6M30QrRF+Uhu7D+iE/7vpR oFYjtczM7WfETQ6E9In/pqhPp/8l+X/BwpEV4RrEVofxXSsPH4ajMZ7x+LKiOMNC DDlsD2xkRwQMTdqgyboSBWP9GBmDw+jH7WUUEzOBNXsIYMnckLaKi0T1Rb2mSppN +RsP/PReLrCnsB6DwtDespr5lO4Wf1U7laVpqMmC54fwmpxeEVA= =feKy -----END PGP SIGNATURE----- --Sig_/=pk9Y9LpQ6oa5YoIJDRURMY--