On 06/18/2010 08:17 AM, Kevin O'Gorman wrote:
> I'm running grub 2 it seems. I don't know when that started, or what
> difference it makes compared to legacy grub. I guess I don't need to
> know. But a recent post had me looking at use-flags, and I was a bit
> surprised to find (ncurses -static). If this refers to the part of grub
> that I run when setting up or tweaking while Linux is already running, I
> guess that's sensible. But does it have any effect on the boot sequence
> (because both of those would strike me as badly broken).
>
> I also wonder what -custom-cflags would be used for, and I don't get any
> sensible answer from flagedit(1).
>
> Just an inquiring mind...
>
> [I] sys-boot/grub
> Available versions: 0.92-r1 0.94-r1 0.96-r1 0.96-r2 ~0.96-r3 ~0.97
> 0.97-r2 0.97-r3 0.97-r4 0.97-r5 0.97-r6 ~0.97-r8 0.97-r9 **1.98 **9999
> {custom-cflags debug multislot ncurses netboot static truetype}
> Installed versions: 0.97-r9(06:16:18 AM 03/03/2010)(ncurses
> -custom-cflags -netboot -static)
> Homepage: http://www.gnu.org/software/grub/
> Description: GNU GRUB 2 boot loader
I think it's used in both places, Kevin. You certainly see ncurses when
you're in grub and doing a setup for instance, but you'd need ncurses at
boottime in order to highlight which grub record you wanted to edit and
all the fancy stuff it does out there before the OS begins.
My hunch about -custom-cflags is that, by default, grub would want to
make its binary as generic as possible. But if you want to see your grub
menus that many nanoseconds sooner, you could always apply your own über
mega hyper powered extra special smokin' grub.
And finally, don't even mention how braindead the "new" improved grub
is. I wonder how anyone can feel that having to write six paragraphs in
some one-off bash-like language, which needs to be debugged, is better
than four lines in a config file.
Bill
