mkinitrd in -current missing lukstrim

sramov · 05-08-2017, 03:27 PM

I'm getting `cat: /lukstrim: No such file or directory` or something like that while booting with generic kernel and initrd. I think `initrd-tree.tar.gz` is missing an empty `/lukstrim` file.

This seems to be related with this update:

Code:

Mon Mar 20 20:43:14 UTC 2017
a/mkinitrd-1.4.9-x86_64-1.txz:  Upgraded.
  Support FSTRIM on LUKS devices unlocked at boot.  Note that the expected name
  of a root LUKS device has changed -- please see the revised README_CRYPT.TXT.
  Thanks to Mason Loring Bliss for the initial patch, and Robby Workman
  for a few adjustments and documentation.

GazL · 05-09-2017, 03:21 AM

Yeah, it's because it's missing from /usr/share/mkinitrd/initrd-tree.tar.gz

Also, while we're on the subject of mkinitrd, I've mentioned this before but there's an annoying /sbin/crda not found during the initrd owing to 85-regulatory.rules being copied to the initrd without the supporting executable. May I suggest adding this rule file to LIBUDEV_BLACKLIST in /sbin/mkinitrd.

moesasji · 05-13-2017, 02:04 AM

Quote:

Originally Posted by GazL

Also, while we're on the subject of mkinitrd, I've mentioned this before ...

As this post will hopefully trigger a look at mkinitrd by I assume AlienBob(?)

While doing that it would be great if the bug that prevents slackware 14.2 (and I assume current) to boot from btrfs subvolumes get fixed. That bug bites me every time I install a machine. Details in this topic: http://www.linuxquestions.org/questi...6/#post5650641

The actual patch for it is in the first post.