On Sat, 9 Jul 2022 at 10:31, Andy Smith via BitFolk Users <
users(a)mailman.bitfolk.com> wrote:
Hi Kamal,
On Sat, Jul 09, 2022 at 09:52:35AM +1000, Kamal Shaker via BitFolk Users
wrote:
grub2-tools which does call:
/sbin/grub2-switch-to-bls-cfg
That looks like the culprit, the man page for it says: "reconfigures
grub-mkconfig to use BLS-style config files"
In the previous thread at:
https://mailman.bitfolk.com/mailman/hyperkitty/list/users@mailman.bitfolk.c…
we had got as far as working out that it's grub2-tools which
triggered this, but although you can disable this by putting
Yes, sorry, read it too quickly.
GRUB_ENABLE_BLSCFG=false
in /etc/default/grub and doing
# grub2-mkconfig -o /boot/grub2/grub.cfg
it's unclear to me whether the system continues then updating
grub.cfg on new kernel install or not.
I suppose my most pressing questions are:
- Does the above revert this configuration?
Yes is does, but...
- Does it stay reverted or does every update of
grub2-tools put
BLSCFG back even if GRUB_ENABLE_BLSCFG=false is set?
It appears up or downgrading reverts this back to 'true' every time, which
is really quite annoying.
- Does grub.cfg keep getting updated properly on new
kernel
installs?
As long as the /etc/default/grub has the correct settings, yes. But see
above.
According to the rpmspec of grub2-tools, the file shouldn't be replaced *1:
%files
%config(noreplace) %ghost %attr(0644, root, root) %verify(not md5 size link
mtime) "/etc/default/grub"
That fles appears to be in all versions of the package with the same line.
So I suspect it's a bug somewhere, because there's a .rpmsave file:
[root@localhost default]# ll
total 12
-rw-r--r--. 1 root root 322 Jul 10 02:23 grub
-rw-r--r--. 1 root root 323 Jul 10 02:23 grub.rpmsave
I think it could be the %ghost directive, which may just be replacing the
file. *2
But that's about as far as I'm going to dig into this.
Kamal.
*1:
https://www.cl.cam.ac.uk/~jw35/docs/rpm_config.html
*2:
http://ftp.rpm.org/max-rpm/s1-rpm-inside-files-list-directives.html