Re: yum update kernel, culprit?

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

 



On Nov 6, 2013, at 12:07 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote:

> 
> On Nov 6, 2013, at 12:34 AM, Frank Murphy <frankly3d@xxxxxxxxx> wrote:
> 
>> Anyone else see this?
>> 
>> the last two kernels, I have updated with yum update
>> put the following into /boot/grub2/grub.cfg
>> <snipped>
>> linux	/vmlinuz-kernel-3.11.7-300.fc20.x86_64
>> root=/dev/mapper/luks-alphanumericbit
>> 
>> Has to be fixed before reboot with grub2-mkconfig
>> which puts in:
>> root=root=UUID=alphanumericbit
> 
> The former is the vernacular used by grubby, so if the entry doesn't work it may be due to a change in dracut and systemd expecting UUID rather than the older vernacular. Open question if the older usage is deprecated and thus a grubby bug.

During alpha or maybe early beta, I noticed that grub2-mkconfig would use different syntax when called by anaconda with the installed system chrooted, vs called directly. The former (installer) produced grub.cfg used e.g. root=/dev/sda2, whereas a grub2-mkconfig once booted from sda2 would produce e.g. root=UUID=<uuid>. So it's possible something else is going on, because I think grubby just does uses an existing boot entry as a template for the new kernel entry.


Chris Murphy
-- 
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test





[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux