[lug] Fedora 19, Grub2 Misbehaving

[stimits at comcast.net]

>> ...>> On 03/17/2015 06:47 PM, stimits at comcast.net wrote:>> I know F19 is>> old, but it still has updates available, and my system is>> updated>> daily. >> >It doesn't. No new updates to F19 are released any more.>> >> I guess that's why I haven't noticed any updates recently :)
 
>Yeah, as of january 6th: >https://lists.fedoraproject.org/pipermail/announce/2015-January/003248.html
 
I actually have the adobe repository set up. I don't pay a lot of attention to what gets updated, so long as it updates daily...I guess the few updates I've noticed are probably from them.
 
>> I guess that is the question then...where is the right place to>> edit? /boot/grub2/ no longer has a menu file except for one that says>> "don't edit this it is automatically generated" (or something close>> to that). Additionally, I do not see "rhgb" or "quiet" in any of the>> files within /boot/grub2/. There seems to be some sort of "saved">> menu it uses, but it is not plain english and does not have anything>> recognizable as rhgb or quiet or user-editable entries. Is it safe to>> use grub2-mkconfig and not erase or overwrite existing entries? I'm>> getting frustrated figuring out how this "feature" is being turned on>> and being wary of killing my boot loader on my only working machine>> which dual boots.
 
>If the machine dual boots, are you sure you are changing the right grub>config? Perhaps the grub thats being used is reading it's config from>another OS/boot partition?
 
As of today it does not seem to be doing this anymore. The same boot configuration has been used without change (other than what yum update does) since F19 first came out, dual booting with windows, as well as having some prior setups available. The /boot partition has remained constant and unchanged except for yum updates. Even from previous installs all the way back to F16 the boot partition has been the same partition on the same disk. I'm scratching my head as to how this could change overnight. I realize now though that I have not watched this machine boot for quite some time...I turn on the power in the morning and walk away, coming back after it has already booted. All I did was remove the rhgb quiet from /etc/default/grub.
 
The grub2.cnf says:
# DO NOT EDIT THIS FILE## It is automatically generated by grub2-mkconfig using templates# from /etc/grub.d and settings from /etc/default/grub 
Further down there are functions such as "savedefault". I'm wondering if maybe there was something that could have "saved" like a temporary file? This would be about the only way I could see the rhgb/quiet suddenly appearing while at the same time not in the grub.cfg. Oh well, I guess it doesn't matter now (but it can be kind of disturbing to see a boot loader change "all by itself").
 
>On Fedora at least you should be able to directly edit >/boot/grub2/grub.cfg or /boot/efi/EFI/fedora/grub.cfg and then grubby>will use the default entry when adding new kernels (which shouldn't>actually be a problem as there will never be any new kernels for f19). 
 
It might be time for me to be looking at F21. I just hate to risk taking this machine down when I'm not absolutely positive it would upgrade without issue. FYI, in the past I always edited grub.cfg by hand, it's that comment boilerplate about automatic generation of the file which keeps me from direct edits.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20150318/f21629d2/attachment.html>