19 (Schrödinger’s Cat)
h.reindl at thelounge.net
Fri Sep 6 22:17:57 UTC 2013
Am 06.09.2013 20:26, schrieb Darryl L. Pierce:
> On Thu, Sep 05, 2013 at 11:26:39PM +0200, Reindl Harald wrote:
>> Am 05.09.2013 23:11, schrieb Darryl L. Pierce:
>>> On Thu, Sep 05, 2013 at 10:11:51PM +0200, Reindl Harald wrote:
>>>> * there is *nothing* in this configuration referring to the release name
>>> /boot/grub2/grub.cfg is generated via the grub2-mkconfig script, which
>>> uses settings from /etc/default/grub.
>>> /etc/default/grub uses the content from /etc/system-release to set the
>>> distributor value:
>>> GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
>>> /etc/system-release contains the name of the Fedora release.
>>> Did you change either /etc/default/grub or grub2-mkconfig?
>> i simply edited /boot/grub2/grub.cfg
>> and after that i expect *nothing* to add the release name
>> *but* a lter kernel updates is adding it again
>> i am using Fedor since "Fedora Core 3" and i am maintaining
>> more than 20 fedora setups and *before* F19 nobody and nothing
>> touched "grub.cfg" due kernel update slike F19
>> and as shown before GRUB_DISTRIBUTOR does *not* contain this crap
>> [root at testserver:~]$ cat /etc/default/grub | grep DISTR
>> this file should not matter as in the past
> Have your filed a BZ? What's the BZ#?
don't get me wrong but i expect bugs viewable at every single boot
as fixed without a specific report and to be honest not existing
at all by a wiser release-name selection or drop the useless
release-names at all
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 263 bytes
Desc: OpenPGP digital signature
More information about the devel