From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mu20e-00033l-1Y for mharc-grub-devel@gnu.org; Sat, 03 Oct 2009 06:38:40 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mu20c-00032e-AI for grub-devel@gnu.org; Sat, 03 Oct 2009 06:38:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mu20a-00031n-NY for grub-devel@gnu.org; Sat, 03 Oct 2009 06:38:37 -0400 Received: from [199.232.76.173] (port=33673 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mu20a-00031f-Hy for grub-devel@gnu.org; Sat, 03 Oct 2009 06:38:36 -0400 Received: from relay.hkfree.org ([89.248.240.5]:54087 helo=mail.hades.hkfree.org) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mu20Z-0000uA-MQ for grub-devel@gnu.org; Sat, 03 Oct 2009 06:38:36 -0400 Received: from jezz-ipv6.hivenew.hkfree.org (jezz-pc1.hive.hkfree.org [10.107.31.218]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.hades.hkfree.org (Postfix) with ESMTP id DAE8FB6360 for ; Sat, 3 Oct 2009 12:38:21 +0200 (CEST) Received: from jezberam by jezz-ipv6.hivenew.hkfree.org with local (Exim 4.69) (envelope-from ) id 1Mu20M-0003Qe-23 for grub-devel@gnu.org; Sat, 03 Oct 2009 12:38:22 +0200 Date: Sat, 3 Oct 2009 12:38:22 +0200 From: jezz@hkfree.org To: The development of GRUB 2 Message-ID: <20091003103821.GA11605@titan> References: <20090927180451.GA23688@titan> <20091002205346.GB19103@thorin> <2e59e6970910021445y6029a95ekf3e341df16159cbb@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline In-Reply-To: <2e59e6970910021445y6029a95ekf3e341df16159cbb@mail.gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Subject: Re: Support for howmany option in grub2 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Oct 2009 10:38:38 -0000 --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On P=C3=A1 2.=C5=99=C3=ADj, richardvoigt@gmail.com wrote: > On Fri, Oct 2, 2009 at 3:53 PM, Robert Millan wrote: > > On Sun, Sep 27, 2009 at 08:04:51PM +0200, jezz@hkfree.org wrote: > >> Hello, > >> I am using Debian GNU/Linux as my primary system. As a loader I am usi= ng GRUB. > >> Actually I have upgraded to GRUB2. I don't know, if it was feature of = original > >> (legacy) GRUB or it was functionality provided by debian scripts (upda= te-grub), > >> for generating menu.lst. There was feature - howmany. This option spec= ifies > >> number of kernels, that user wants to have in boot menu. Script, that = modifies > >> menu.lst, use this variable. I like this feature, because I have usual= ly more > >> kernels, but I want to see only last two versions in GRUB menu. I have= created > >> patch, that add support for this to /etc/grub.d/10_linux. I have creat= ed this > >> patch against version shipped with Debian (1.97~beta3-1) - I don't kno= w if > >> there are some Debian specific modifications. Also there should be var= iable > >> GRUB_HOW_MANY propagated from /etc/default/grub (my patch don't do > >> this). > >> Kernel and it's rescue variant is counted as one kernel. > >> > >> I have already reported this bug to Debian BTS: > >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D548600 > > > > Does anyone else think we want an option for this? =C2=A0It seems like = "feature > > creep". >=20 > IMO this is the responsibility of the distro. The distro's package > manager is presumably what adds and removes kernels, there's no way > that the grub scripts should be expected to know when past kernels > have been removed. >=20 > With more manual-install oriented distros like gentoo, trying to have > grub maintain the kernel list like this would be insane, since the > local admin determines the naming convention. >=20 I thought that 10_linux script belongs to debian, so I have reported this enhancement to debian first. Now I know, that this script is distributed wi= th grub. Debian developer suggests me to submit this to upstream. I know, that distribution is responsible for adding/removing kernels. That = is the standard way - if I have two kernels installed, then I have two kernels= in menu. With old grub (and debian infrastructure) I have option to limit numb= er of kernels in menu. So I have three kernels, but only two kernels in menu. With grub it is possible to boot kernel not listened in configuration - this was my use case. This feature means only to modify shell script - grub is not modified. And = it is really simple modification. The script is already doing some black magic= - sorting list of kernels by version. When you add limit then you will have l= ast two (or what is configured) kernels in menu. > > > > -- > > Robert Millan > > > > =C2=A0The DRM opt-in fallacy: "Your data belongs to us. We will decide = when (and > > =C2=A0how) you may access your data; but nobody's threatening your free= dom: we > > =C2=A0still allow you to remove your data and not access it at all." > > > > > > _______________________________________________ > > Grub-devel mailing list > > Grub-devel@gnu.org > > http://lists.gnu.org/mailman/listinfo/grub-devel > > >=20 >=20 > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/grub-devel --=20 Jezz mail: jezz@hkfree.org jabber: jezz@njs.netlab.cz --wRRV7LY7NUeQGEoC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkrHKZ0ACgkQqyAtJTO7yRJwhwCeJsO6fH+s4cS6fsbT8tnFvMCQ o/wAoIxj/37fM1XqPMOsk9NbLfqyevGL =2XPo -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC--