On Tue, Nov 30, 2010 at 4:25 AM, Volkan YAZICI <yazic...@ttmail.com> wrote: > > TL;DR --- /etc/grub.d/10_linux causes update-grub to match same Linux > image twice. (Debian GNU/Linux Squeeze, up-to-date as of date.) > > # ls -1F /boot > config-2.6.32-5-686 > grub/ > initrd.img-2.6.32-5-686 > System.map-2.6.32-5-686 > vmlinuz-2.6.32-5-686 > > # dpkg -l | grep linux-image > ii linux-image-2.6.32-5-686 2.6.32-28 Linux 2.6.32 for modern PCs > > # update-grub > Generating grub.cfg ... > Found linux image: /boot/vmlinuz-2.6.32-5-686 > Found initrd image: /boot/initrd.img-2.6.32-5-686 > Found linux image: /boot/vmlinuz-2.6.32-5-686 > Found initrd image: /boot/initrd.img-2.6.32-5-686 > Found Debian GNU/Linux (5.0.7) on /dev/sda2 > done > > # mv /etc/grub.d/10_linux ~/ > # update-grub > Generating grub.cfg ... > Found linux image: /boot/vmlinuz-2.6.32-5-686 > Found initrd image: /boot/initrd.img-2.6.32-5-686 > Found Debian GNU/Linux (5.0.7) on /dev/sda2 > done
So 10_linux isn't the problem. Another script is somehow picking up 2.6.32... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktiéhhrx8fkbsgvwjbd+ymjzytpjct7+fcsu...@mail.gmail.com
