On Mon, Sep 15, 2008 at 09:14:03PM +0300, Vesa Jääskeläinen wrote: > Felix Zielcke wrote: > > Am Donnerstag, den 04.09.2008, 21:45 +0200 schrieb Robert Millan: > >> Since we're going for a change, why not fix the CLI while at it? > >> > >> It'd be much more flexible and consistent if the command was meant to > >> *generate* a grub.cfg rather than update the canonical /boot/grub/grub.cfg. > >> > > > > Attached is now a patch which renames it to grub-mkconf and prints it to > > stdout instead of grub.cfg file. > > I kept the Found kernel/initrd etc. stuff to stderr, but maybe this > > should be removed ? > > mkconf? > > Could it be a bit more verbose ;)... if we are to go path of > grub-mkconfig (or even grub-make-config).
I like my bikeshed with "config" in it, too. ;-) > Thou I prefer myself > grub-update-config being more descriptive on what it does. With the proposed behaviour, it wouldn't be "updating" anything. That depends on how it is used (one could just want to generate grub.cfg a single time, or so). > grub-update-config --out <file> could be easily used to override where > to save the generate configuration file. Why not '-o' for consistency with grub-mk*image ? -- 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." _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
