All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Keyboards
Date: Sat, 7 Feb 2009 23:50:34 +0100	[thread overview]
Message-ID: <20090207225034.GT6343@thorin> (raw)
In-Reply-To: <498A05F3.9080605@earthlink.net>

On Wed, Feb 04, 2009 at 04:17:39PM -0500, BandiPat wrote:
> /boot/vmlinuz-2.6.28.3 and should be booted as default. So after copying 
> a new kernel to but I'll have to update my grub.cfg, too. Or is it 
> posible to specify some "default settings" in that way:
> 
> set root=(hd0,2)
>         linux   (hd0,2)/boot/vmlinuz-2.6.*.* root=/dev/sda2 ro 
> splash=silent vga=794
> }
> Which would list all vmlinuz-2.6.*.* kernels as menuentry and 
> automatically set the highest version number as default. This would be 
> cool :-D

The idea about letting grub-mkconfig do such things is that since it has
access to a complete Unixy environment, it can be smarter than what GRUB
would do.  Also, this design allows GRUB to be smaller/faster that it
would be if we had to do everything at every boot.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



      parent reply	other threads:[~2009-02-07 22:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04 21:17 Keyboards BandiPat
2009-02-05 11:32 ` Keyboards Felix Zielcke
2009-02-05 13:30   ` Keyboards BandiPat
2009-02-07 22:48 ` Keyboards Robert Millan
2009-02-07 22:50 ` Robert Millan [this message]

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=20090207225034.GT6343@thorin \
    --to=rmh@aybabtu.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.