grub-mkconfig loop
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I use a self compiled linux kernel (make-kpkg) with a somewhat unusual
name (/boot/vmlinuz-3.15.4+ and /boot/initrd.img-3.15.4+) on debian sid.
It worked previously (sadly I can't be more precise here) but today
update-grub ran into a loop where my custom kernel was detected by
/etc/grub.d/10_linux over and over again.
The variable $list contained the correctly detected installed kernels
but my kernel would not be removed from $list at the end of the big
while loop in the line with "list=`echo $list | tr ' ' '\n' | grep -vx
$linux | tr '\n' ' '` . (line 349 for me)
Therefore $linux in the next round of this big while loop would be my
custom kernel again and again.
For me changing the line to "list=`echo $list | tr ' ' '\n' | grep -v
$linux | tr '\n' ' '` fixed the problem.
Is there any reason the x option was used in the first place or $linux
was not put in quotes? Is my fix a bad idea for some reason?
Best regards
Heimo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJTu+IzAAoJEJz2q6aG5VRzU3cQALlqZNHq41j5Plz3CHUY/I41
w5r/sH1vkVCYquF5qxU2YCA/pjnwBYEE7p5QNJoRWuGSU7A890N19Lyi01lu12oF
A6/ezrQIokNyeC0utrR6Fkb095v6yAVHgnDpHcLo0VAKqtc4CK3nfPPT+1/5+xD6
RJ1i/fSkwI1OtKNapDNP0lVKLUH6RPHYThq3zIcvFusPKbnx9CbOO9zb9pVuDs8M
j+misgxtsHHNuBD8mbhtR5Wt5ZuADLviCcu4vQO39YSs2BwtbbuyM2hCLYNFWRAj
vdB1vStCVtnkfWKlGI8ouv4SntlPWlSWkTKk0vs9xb3zkSCyi3ToijPTSG8m7/KV
FhZWkmrAwRfNkvbeLUFUHUTma/lSBccOJzTxUT/B+zIfJn94R5Nosj3Pn9OLHou5
mSuU6ofoibiqD6hV+Ba5EGxUIweYWLZfmvHs5WpbBb77/VilNIn0URzqxFt2LVyj
PbYcNS98X17+xelD4PiuikTgAMbuZMObNRxzRx65a1urzX9wuwMU/QWlfv5w8qbp
0TPd3fyqtoacsZv/AP4UA8pK5zACQOH2xjG4Va4aWDUMz+VSrLHDsPakjGDHFLNF
39QM7JEIhib8aHF4m4zIzKocHU6+2tMmO/5TuQScHtKWCKUZAhGEKedu/boesUjx
U6ZYjld8c5tFIjpVg8sV
=eD/l
-----END PGP SIGNATURE-----
Reply to: