From: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Support for howmany option in grub2
Date: Sat, 03 Oct 2009 14:49:20 +0200 [thread overview]
Message-ID: <4AC74850.809@gmail.com> (raw)
In-Reply-To: <a5d587fb0910021601l54c3c637r62d39405c6ebcf01@mail.gmail.com>
Michal Suchanek wrote:
> 2009/10/3 Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>:
>
>> 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 using 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 (update-grub),
>>>> for generating menu.lst. There was feature - howmany. This option specifies
>>>> 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 usually 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 created this
>>>> patch against version shipped with Debian (1.97~beta3-1) - I don't know if
>>>> there are some Debian specific modifications. Also there should be variable
>>>> 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=548600
>>>>
>>>>
>>> Does anyone else think we want an option for this? It seems like "feature
>>> creep".
>>>
>>>
>>>
>> Many kernels encumber view and may make menu difficult to navigate (I
>> have to scroll through a lot of linux kernels before I get to FreeBSD).
>> But choosing kernels would involve heuristics which are likely to fail
>> if e.g. user is in the middle of git bisect
>> But the core issue is a bad menu organisation. I think we need two-level
>> menu. It seems Bean is already working on issue but I haven't followed
>> that thread closely
>>
>>
>
> I guess it should be possible one way or another once the new menu
> system is ready.
>
> It should be possible to sort the non-linux extra boot options into a
> separate list and thus make them easier to reach, for example.
>
>
I would prefer two level OS/kernel choice. E.g. I first choose that I
want linux from hdX,Y and then I choose the exact kernel. Perhaps normal
keypress enter in first-level menu would boot most recent kernel and
e.g. hitting F6 will offer kernel choice
> Thanks
>
> Michal
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>
--
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git
next prev parent reply other threads:[~2009-10-03 12:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-27 18:04 Support for howmany option in grub2 jezz
2009-10-02 20:53 ` Robert Millan
2009-10-02 21:45 ` richardvoigt
2009-10-03 10:38 ` jezz
2009-10-02 22:00 ` Vladimir 'phcoder' Serbinenko
2009-10-02 23:01 ` Michal Suchanek
2009-10-03 12:49 ` Vladimir 'phcoder' Serbinenko [this message]
2009-10-03 15:21 ` Michal Suchanek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AC74850.809@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.