Re: How to change console font in grub2?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Oct 16, 2010 at 12:22 AM, JD <jd1008@xxxxxxxxx> wrote:
>  On 10/15/2010 08:29 PM, Tom H wrote:
>> On Fri, Oct 15, 2010 at 6:18 PM, Tom Horsley<horsley1953@xxxxxxxxx>  wrote:
>>> On Fri, 15 Oct 2010 16:27:37 -0500 Dennis Gilmore wrote:
>>>>
>>>> the path to it being the
>>>> default resides in more usage testing and bug fixing in fedora
>>> The path to it being a viable option first has to go through
>>> the process of the utter elimination of the foolish update-grub
>>> preprocessor to construct the grub.cfg file from a million
>>> bits and pieces.
>>>
>>> Grub originally cleaned lilo's clock primarily because you
>>> didn't have to remember to run extra tools to make the changes
>>> take effect. Now the standard usage for grub2 requires running
>>> extra tools again. Does no one remember how many problems
>>> that caused?
>>>
>>> One of the primary reasons it must not use a preprocessor
>>> (particularly the way it is currently distributed) is that
>>> you cannot actually configure everything you might need to
>>> change. You can fall back on editing various files you
>>> aren't supposed to edit, but the next grub2 update you
>>> get will probably overwrite your changes.
>>>
>>> You can even edit the grub.cfg file if you want to, but the
>>> next kernel update will overwrite your changes.
>>>
>>> Until the one and only place grub config information is
>>> stored is the one grub.cfg file, grub2 is unacceptably
>>> boneheaded and should not be the standard boot loader.
>> You're being unfair to grub2! :)
>>
>> Unlike lilo, grub2-mkconfig doesn't re-write the MBR; a big
>> difference. Also, in grub1, grubby edits "/boot/grub/grub.conf" when a
>> new kernel is installed so grub1's behavior isn't that different from
>> grub2's.
>
> I have not used grubby directly, but when a new kernel is installed,
> the only annoying change is that the new kernel entry is on top
> of all previous entries, AND the default boot number is bumped up by one
> so that default boot is the same kernel you have been booting.
> I find this acceptable and least intrusive of the two options (grub1 vs.
> grub2).

I don't follow. The default for both grub1 and grub2 is that the
latest installed kernel becomes the default unless, for grub1 on
Fedora, you change "UPDATEDEFAULT=yes" in "/etc/sysconfig/kernel",
AFAIK.
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux