On Tue, Nov 30, 2010 at 4:45 AM, Volkan YAZICI <yazic...@ttmail.com> wrote: > On Tue, 30 Nov 2010, Tom H <tomh0...@gmail.com> writes: >> >> So 10_linux isn't the problem. Another script is somehow picking up >> 2.6.32... > > It depends. If 10_linux is expected to find currently running kernel as > well, your are right; otherwise, wrong. I thought that the current > kernel is somehow automatically added to the list without an > intervention from /etc/grub.d scripts. Anyway, there still is a problem.
10_linux adds the kernel(s) in the "/boot" of the install with the active grub install. And, yes, there is a problem if the kernel in "/boot" is added by a script other than 10_linux. -- 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/aanlktinf0zrswymtnn_2qnecvcxzyg_6z09tep=lq...@mail.gmail.com
