I misremembered. the correct command is indeed the mkconfig one. I'd recommend backing up your old config first or outputting to stdout so you can check everything first. On Jan 24, 2014 1:20 PM, "Dale" <rdalek1...@gmail.com> wrote:
> Andrés Becerra Sandoval wrote: > > > Hi James, > > If you put the kernels in /boot with proper names and launch: > > grub2-mkconfig -o /boot/grub/grub.cfg > > Grub will set up the kernels for you. > > If you want (not likely) to create a manual entry, put it in > /etc/grub.d/40_custom > > > -- > Andrés Becerra Sandoval > > > > That has been my experience so far as well. Little info for OP. > > root@fireball / # ls -al /boot/kernel* > -rw-r--r-- 1 root root 5148896 Dec 6 21:05 /boot/kernel-3.11.6-1 > -rw-r--r-- 1 root root 5023696 Oct 18 08:31 /boot/kernel-3.9.5-NEWMOBO > -rw-r--r-- 1 root root 5020432 Oct 20 22:30 /boot/kernel-3.9.5-NEWMOBO-1 > root@fireball / # > > root@fireball / # grub2-mkconfig -o /boot/grub2/grub.cfg > Generating grub configuration file ... > Found linux image: /boot/kernel-3.11.6-1 > Found linux image: /boot/kernel-3.9.5-NEWMOBO-1 > Found linux image: /boot/kernel-3.9.5-NEWMOBO > done > root@fireball / # > > > What I have not figured out yet, how to know that it sees and applies that > init thingy that dracut made. It doesn't mention finding it so I don't > know if it does or not. Hmmmm. > > Dale > > :-) :-) > > -- > I am only responsible for what I said ... Not for what you understood or how > you interpreted my words! > >
