On 10/26/2014 08:43 PM, Canek Peláez Valdés wrote: > > On Sun, Oct 26, 2014 at 1:41 PM, Canek Peláez Valdés <can...@gmail.com> wrote: >> On Sun, Oct 26, 2014 at 2:33 PM, Giuseppe Pappalardo >> <m...@giuseppepappalardo.eu> wrote: >>> On 10/26/2014 08:23 PM, Canek Peláez Valdés wrote: >>>> >>>> >>>> As to how do I maintain them, I wrote a little utility that I've been >>>> using from the last year or so: >>>> >>>> https://github.com/canek-pelaez/kerninst >>>> >>>> With it, after I install a new kernel using the normal portage >>>> procedure, I just do: >>>> >>>> eselect kernel set <new-version> >>>> kerninst >>>> >>>> And that's it. Be aware that you need to provide your own kernel >>>> configuration. >>>> >>>> Regards. >>>> >>> How does this differs from just enabling the "symlink" USE flag in >>> vanilla-sources? >> >> AFAIU, the symlink USE flag just updates the /usr/src/linux link >> automatically at install time (although I have never used it). >> >> kerninst configures (using a user-provided .config file), compiles, >> and installs the kernel in the correct location (/boot if using GRUB2, >> a more complex location if using Gummiboot), and then it updates the >> configuration of the boot manager (either GRUB2 or Gummiboot). > > Oh, I forgot; it also generates an initramfs for it with dracut. This > is important: kerninst assumes you use an initramfs, and that you use > dracut to create it. Also, it assumes you already configured > dracut.conf. > > Regards. > Got it. Thanks a lot for your clarification.
-- Giuseppe "Pappi" Pappalardo | www.giuseppepappalardo.eu | www.twitter.com/pappi_
