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: Rename update-grub to grub-update?
Date: Thu, 20 Mar 2008 14:10:46 +0100	[thread overview]
Message-ID: <20080320131046.GA16344@thorin> (raw)
In-Reply-To: <20080212113451.GB19144@thorin>

On Tue, Feb 12, 2008 at 12:34:51PM +0100, Robert Millan wrote:
> On Tue, Feb 12, 2008 at 12:51:13AM -0500, Pavel Roskin wrote:
> > Hello!
> > 
> > All grub binaries installed in $prefix/bin and $prefix/sbin start with  
> > "grub-" except mbchk and update-grub.  mbchk is probably not meant to  
> > be grub specific, but update-grub is.
> > 
> > I think it would be logical to rename update-grub to grub-update.  
> > Objections?
> 
> I picked this name for historical reasons, since it was aimed at replacing
> a Debian-specific script that performed the same functionality.
> 
> Calling it "update-grub" has a big advantage: for many GRUB Legacy users,
> when seeing a script called like this they will instantly know what it
> does.
> 
> That aside, I agree the name is quite unfortunate.  What would you think of
> postponing this untill GRUB Legacy has been replaced?  It's already a big leap
> to migrate from GRUB Legacy to GRUB 2;  I suggest we don't make it bigger yet.

On a second thought, this wouldn't be much of an issue if Debian can have its
own "update-grub" which wraps around "grub-mkconfig" or whatever you want to
call it.

Additionally, this would allow us to change the CLI to something that doesn't
hardcode /boot/grub/grub.cfg and provides greater flexibility, e.g.:

  grub-mkconfig -o /boot/grub/grub.cfg

which is also useful for Debian.

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)



  parent reply	other threads:[~2008-03-20 13:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12  5:51 Rename update-grub to grub-update? Pavel Roskin
2008-02-12  7:23 ` Yoshinori K. Okuji
2008-02-12  9:09   ` Franklin PIAT
2008-02-12 22:37   ` Pavel Roskin
2008-02-12 11:34 ` Robert Millan
2008-02-12 22:37   ` Pavel Roskin
2008-02-13 15:49     ` Robert Millan
2008-03-20 13:10   ` Robert Millan [this message]
2008-03-20 15:31     ` Pavel Roskin

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=20080320131046.GA16344@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.