Re: [gentoo-user] Dracut and how to specify names

[Neil Bothwick]

On Fri, 3 Jan 2020 01:27:22 -0600, Dale wrote:

> >> I name my kernels and such this way:
> >>
> >> root@fireball /usr/src/linux # ls -al /boot/kernel*
> >> -rw-r--r-- 1 root root 7061552 Oct 14  2018 /boot/kernel-4.18.12-1
> >> -rw-r--r-- 1 root root 7082032 May 15  2019 /boot/kernel-4.19.40-1
> >> -rw-r--r-- 1 root root 7102512 Jan  2 19:46 /boot/kernel-4.19.40-2
> >> -rw-r--r-- 1 root root 5858496 Jun 17  2016 /boot/kernel-4.5.2-1

> I decided to go back to a older version, just to see if it works.  The
> first example I had saved didn't work but the second did.  First was
> likely from a much older version of dracut.  Do you know what changed
> between dracut-046-r1 and dracut-048-r1?  I ran into this once before
> when a major version number changed. 

There was an elog message when the latest dracut emerged here, that was
to do with naming. I didn't read all of it as it clearly didn't apply
when using the default naming scheme of installkernel.
 
> One reason I'd like to be able to specify everything is to avoid changes
> in future versions.  That way I can use the same command each time
> unless they completely change everything which I'm sure I'd read about
> long before I needed to use it.  Just has a example:
>
> dracut /boot/<kernel name> <initramfs name> -k <path to kernel modules>

If you stick with the standard kernel naming schemes, dracut will follow
them and you shouldn't have such issues. Using make install to install
the kernel instead of copying it manually will ensure you have names that
dracut will find.

Unless you have a good reason to use non-standard naming, I would
recommend sticking with the defaults, there is less likelihood of this
type of breakage.

If you really want to plough your own furrow, try running dracut with the
--debug option. When had issues with dracut recently, -v didn't add
anything but --debug highlighted the problem immediately.


-- 
Neil Bothwick

Help put the "fun" back in "dysfunctional" !