From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: [RFC] rename update-grub to update-grubcfg
Date: Thu, 04 Sep 2008 14:22:08 +0200 [thread overview]
Message-ID: <1220530928.4167.49.camel@fz.local> (raw)
There was already the topic to rename update-grub to grub-update[0]
On Debian such things are always called update-something not
something-update[1]
I just told again in a Debian Bugreport to use grub-install to update
grub in real.
So I suggest to rename update-grub to something like update-grubcfg or
update-grub-cfg in the hope this makes it more clear for people that
this is mainly for /boot/grub/grub.cfg and not for updating everything
else for grub too.
[0] http://lists.gnu.org/archive/html/grub-devel/2008-02/msg00354.html
[1]
fz@fz:/usr/sbin$ ls update-* *-update
ls: cannot access *-update: No such file or directory
update-alternatives update-fonts-alias update-gdkpixbuf-loaders update-icon-caches update-mime update-rc.d
update-ca-certificates update-fonts-dir update-grub update-inetd update-pangox-aliases update-usbids
update-catalog update-fonts-scale update-grub2 update-initramfs update-passwd update-xmlcatalog
update-flashplugin-nonfree update-gconf-defaults update-gtk-immodules update-locale update-python-modules
--
Felix Zielcke
next reply other threads:[~2008-09-04 12:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 12:22 Felix Zielcke [this message]
2008-09-04 13:56 ` [RFC] rename update-grub to update-grubcfg Pavel Roskin
2008-09-04 17:38 ` Vesa Jääskeläinen
2008-09-04 17:50 ` Felix Zielcke
2008-09-04 19:45 ` Robert Millan
2008-09-15 17:56 ` Felix Zielcke
2008-09-15 18:14 ` Vesa Jääskeläinen
2008-09-17 13:56 ` Robert Millan
2008-09-17 14:31 ` Vesa Jääskeläinen
2008-09-17 15:24 ` Felix Zielcke
2008-09-24 9:49 ` Robert Millan
2008-09-24 11:04 ` Felix Zielcke
2008-09-24 13:22 ` Robert Millan
2008-09-24 13:34 ` Felix Zielcke
2008-09-24 13:54 ` Robert Millan
2008-09-29 14:57 ` Felix Zielcke
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=1220530928.4167.49.camel@fz.local \
--to=fzielcke@z-51.de \
--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.