• mkinitrd geninitrd - how are they triggered

    From Marco Moock@mm@dorfdsl.de to alt.os.linux.slackware on Sat Jul 11 12:35:32 2026
    From Newsgroup: alt.os.linux.slackware

    Hello!

    I just installed a test system with encrypted /.

    I used the mkinitrd_command_generator.sh script and it worked, I will
    see how that works after the kernel update.

    Although, I see the geninitrd command exists, but has no manpage.

    http://www.slackware.com/releasenotes/15.0.php
    I'd strongly recommend using a generic kernel for the best kernel module compatibility as well. It's easier to do that than in previous releases
    - the
    installer now makes an initrd for you, and the new geninitrd utility will rebuild the initrd automatically for the latest kernel packages you've installed on the system.#

    What exactly does it and how is it triggered?
    --
    kind regards
    Marco

    Junk-Mail bitte an trashcan@stinkedores.dorfdsl.de

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Eric Pozharski@apple.universe@posteo.net to alt.os.linux.slackware on Sun Jul 12 22:23:35 2026
    From Newsgroup: alt.os.linux.slackware

    with <112t69k$1vtls$1@dont-email.me> Marco Moock wrote:

    I just installed a test system with encrypted /.
    I used the mkinitrd_command_generator.sh script and it worked, I will
    see how that works after the kernel update.
    Although, I see the geninitrd command exists, but has no manpage.
    *SKIP* [ 6 lines 1 level deep]
    What exactly does it

    Luckily, it's a shell script.

    how is it triggered?

    Automagically, any time new kernel arrives.

    # grep -l geninitrd /var/lib/pkgtools/scripts/*
    --
    Torvalds' goal for Linux is very simple: World Domination
    Stallman's goal for GNU is even simpler: Freedom
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Marco Moock@mm@dorfdsl.de to alt.os.linux.slackware on Sun Jul 19 12:04:49 2026
    From Newsgroup: alt.os.linux.slackware

    Am 13.07.26 um 00:23 schrieb Eric Pozharski:
    with <112t69k$1vtls$1@dont-email.me> Marco Moock wrote:

    I just installed a test system with encrypted /.
    I used the mkinitrd_command_generator.sh script and it worked, I will
    see how that works after the kernel update.
    Although, I see the geninitrd command exists, but has no manpage.
    *SKIP* [ 6 lines 1 level deep]
    What exactly does it

    Luckily, it's a shell script.

    how is it triggered?

    Automagically, any time new kernel arrives.

    # grep -l geninitrd /var/lib/pkgtools/scripts/*

    Thanks for that info.

    Although the automatic script is not suitable if LUKS/LVM is needed,
    unless modified.
    --
    Gru|f
    Marco

    Spam bitte an abfalleimer2001@stinkedores.dorfdsl.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thomas Zajic@zlatko@gmx.at to alt.os.linux.slackware on Sun Jul 19 13:45:27 2026
    From Newsgroup: alt.os.linux.slackware

    * Eric Pozharski <apple.universe@posteo.net>

    with <112t69k$1vtls$1@dont-email.me> Marco Moock wrote:

    I just installed a test system with encrypted /.
    I used the mkinitrd_command_generator.sh script and it worked, I will
    see how that works after the kernel update.
    Although, I see the geninitrd command exists, but has no manpage.
    *SKIP* [ 6 lines 1 level deep]
    What exactly does it

    Luckily, it's a shell script.

    how is it triggered?

    Automagically, any time new kernel arrives.

    # grep -l geninitrd /var/lib/pkgtools/scripts/*

    Hm, that's news to me ... Slackware64-15.0 here:

    [root@next:~]# grep -l geninitrd /var/lib/pkgtools/scripts/*
    [root@next:~]# grep -l mkinitrd /var/lib/pkgtools/scripts/* /var/lib/pkgtools/scripts/mkinitrd-1.4.11-x86_64-28
    [root@next:~]# ls -la /var/lib/pkgtools/scripts/kernel-*
    -rwxr-xr-x 1 root root 236425 Sep 13 2025 /var/lib/pkgtools/scripts/kernel-firmware-20250912_f0f4634-noarch-1
    -rwxr-xr-x 1 root root 358 Jun 3 08:24 /var/lib/pkgtools/scripts/kernel-generic-5.15.209-x86_64-1
    -rwxr-xr-x 1 root root 72 Jun 3 08:25 /var/lib/pkgtools/scripts/kernel-headers-5.15.209-x86-1
    -rwxr-xr-x 1 root root 222 Jun 3 08:27 /var/lib/pkgtools/scripts/kernel-modules-5.15.209-x86_64-1
    -rwxr-xr-x 1 root root 8119 Jun 3 08:52 /var/lib/pkgtools/scripts/kernel-source-5.15.209-noarch-1

    The only thing that the kernel-generic script does is fixing the symlinks
    in /boot. I always invoke geninitrd manually after upgrading my kernel-* packages.

    Thomas
    --
    =-------------------------------------------------------------------------=
    - Thomas "ZlatkO" Zajic <zlatko@gmx.at> Linux-6.18 & slrn-1.0.3a -
    - "In layman's terms: speedy thing goes in, speedy thing comes out." - =-------------------------------------------------------------------------=
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Marco Moock@mm@dorfdsl.de to alt.os.linux.slackware on Sun Jul 19 20:56:30 2026
    From Newsgroup: alt.os.linux.slackware

    Am 19.07.26 um 13:45 schrieb Thomas Zajic:
    The only thing that the kernel-generic script does is fixing the symlinks
    in /boot. I always invoke geninitrd manually after upgrading my kernel-* packages.

    /var/lib/pkgtools/setup/setup.01.mkinitrd seems to be the place.
    --
    Gru|f
    Marco

    Spam bitte an abfalleimer2001@stinkedores.dorfdsl.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thomas Zajic@zlatko@gmx.at to alt.os.linux.slackware on Mon Jul 20 14:13:48 2026
    From Newsgroup: alt.os.linux.slackware

    * Marco Moock <mm@dorfdsl.de>

    Am 19.07.26 um 13:45 schrieb Thomas Zajic:
    The only thing that the kernel-generic script does is fixing the symlinks in /boot. I always invoke geninitrd manually after upgrading my kernel-* packages.

    /var/lib/pkgtools/setup/setup.01.mkinitrd seems to be the place.

    Yes, but that's only relevant for the initial OS installation. It does
    *not* get invoked automagically on "upgradepkg kernel-generic".

    The only thing that gets run automatically on "installpkg" or "upgradepkg"
    is the "install/doinst.sh" script, if one is included in the package.

    Or are we actually discussing the inital installation of Slackware here?
    I have to admit that I missed the beginning of this thread. O:-)

    Thomas
    --
    =-------------------------------------------------------------------------=
    - Thomas "ZlatkO" Zajic <zlatko@gmx.at> Linux-6.18 & slrn-1.0.3a -
    - "In layman's terms: speedy thing goes in, speedy thing comes out." - =-------------------------------------------------------------------------=
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Eric Pozharski@apple.universe@posteo.net to alt.os.linux.slackware on Mon Jul 20 14:08:26 2026
    From Newsgroup: alt.os.linux.slackware

    with <113i7g1$1rg4$1@solani.org> Marco Moock wrote:
    Am 13.07.26 um 00:23 schrieb Eric Pozharski:
    with <112t69k$1vtls$1@dont-email.me> Marco Moock wrote:

    I just installed a test system with encrypted /. I used the
    mkinitrd_command_generator.sh script and it worked, I will see how
    that works after the kernel update. Although, I see the geninitrd
    command exists, but has no manpage.
    *SKIP* [ 3 lines 3 levels deep]
    Automagically, any time new kernel arrives.
    # grep -l geninitrd /var/lib/pkgtools/scripts/*
    *SKIP* [ 1 line 0 level deep]
    Although the automatic script is not suitable if LUKS/LVM is needed,
    unless modified.

    I'm not user of 'geninitrd' itself (it's disabled as soon it manifested
    its presence) but it's companion to 'mkinitrd'. And as of the latter it
    works with LVM fine (as much as my limited usage of LVM goes). Can't
    say anything about LUKS -- not a user.
    --
    Torvalds' goal for Linux is very simple: World Domination
    Stallman's goal for GNU is even simpler: Freedom
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From kaukasoina3dore73js4@kaukasoina3dore73js4@sci.fi (Petri Kaukasoina) to alt.os.linux.slackware on Tue Jul 21 08:46:43 2026
    From Newsgroup: alt.os.linux.slackware

    Thomas Zajic <zlatko@gmx.at> wrote:
    The only thing that gets run automatically on "installpkg" or "upgradepkg"
    is the "install/doinst.sh" script, if one is included in the package.

    In -current, the doinst.sh script runs geninitrd. Not yet in 15.0.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Henrik Carlqvist@Henrik.Carlqvist@deadspam.com to alt.os.linux.slackware on Tue Jul 21 10:22:08 2026
    From Newsgroup: alt.os.linux.slackware

    On Tue, 21 Jul 2026 08:46:43 +0000, Petri Kaukasoina wrote:

    Thomas Zajic <zlatko@gmx.at> wrote:
    The only thing that gets run automatically on "installpkg" or
    "upgradepkg"
    is the "install/doinst.sh" script, if one is included in the package.

    In -current, the doinst.sh script runs geninitrd. Not yet in 15.0.

    There is also a hint about this in ChangeLog.txt, in current it simply
    says something like this:

    -8<--------------------------------------------
    +--------------------------+
    Sat Jul 18 23:57:46 UTC 2026
    a/kernel-firmware-20260716_924d73c-noarch-1.txz: Upgraded. a/kernel-generic-6.18.39-x86_64-1.txz: Upgraded. a/xfsprogs-7.1.1-x86_64-1.txz: Upgraded.
    ap/htop-3.5.2-x86_64-1.txz: Upgraded.
    d/kernel-headers-6.18.39-x86-1.txz: Upgraded. k/kernel-source-6.18.39-noarch-1.txz: Upgraded. l/mozilla-nss-3.126-x86_64-1.txz: Upgraded. x/intel-media-driver-26.3.0-x86_64-1.txz: Upgraded. x/xclock-1.2.1-x86_64-1.txz: Upgraded.
    isolinux/initrd.img: Rebuilt.
    kernels/*: Upgraded. testing/packages/linux-7.1.x/kernel-generic-7.1.4-x86_64-1.txz: Upgraded. testing/packages/linux-7.1.x/kernel-headers-7.1.4-x86-1.txz: Upgraded. testing/packages/linux-7.1.x/kernel-source-7.1.4-noarch-1.txz: Upgraded. usb-and-pxe-installers/usbboot.img: Rebuilt.
    +-------------------------+
    -8<--------------------------------------------

    While the stable version 15.0 ChangeLog.txt says something like this:

    -8<--------------------------------------------
    +--------------------------+
    Tue Jun 2 02:32:11 UTC 2026 patches/packages/linux-5.15.209/kernel-generic-5.15.209-x86_64-1.txz: Upgraded.
    This update fixes security issues:
    rxrpc: Fix missing validation of ticket length in non-XDR key preparsing
    rxrpc: Fix anonymous key handling
    rxrpc: only handle RESPONSE during service challenge
    rxrpc: Fix recvmsg() unconditional requeue
    rxrpc: reject undecryptable rxkad response tickets
    rxrpc: Fix call removal to use RCU safe deletion
    rxrpc: Fix key quota calculation for multitoken keys
    rxrpc: proc: size address buffers for %pISpc output
    For more information, see:
    https://www.cve.org/CVERecord?id=CVE-2026-31696
    https://www.cve.org/CVERecord?id=CVE-2026-31676
    https://www.cve.org/CVERecord?id=CVE-2026-23066
    https://www.cve.org/CVERecord?id=CVE-2026-31637
    https://www.cve.org/CVERecord?id=CVE-2026-31642
    https://www.cve.org/CVERecord?id=CVE-2026-31630
    (* Security fix *) patches/packages/linux-5.15.209/kernel-headers-5.15.209-x86-1.txz:
    Upgraded.
    patches/packages/linux-5.15.209/kernel-huge-5.15.209-x86_64-1.txz:
    Upgraded.
    This update fixes security issues:
    rxrpc: Fix missing validation of ticket length in non-XDR key preparsing
    rxrpc: Fix anonymous key handling
    rxrpc: only handle RESPONSE during service challenge
    rxrpc: Fix recvmsg() unconditional requeue
    rxrpc: reject undecryptable rxkad response tickets
    rxrpc: Fix call removal to use RCU safe deletion
    rxrpc: Fix key quota calculation for multitoken keys
    rxrpc: proc: size address buffers for %pISpc output
    For more information, see:
    https://www.cve.org/CVERecord?id=CVE-2026-31696
    https://www.cve.org/CVERecord?id=CVE-2026-31676
    https://www.cve.org/CVERecord?id=CVE-2026-23066
    https://www.cve.org/CVERecord?id=CVE-2026-31637
    https://www.cve.org/CVERecord?id=CVE-2026-31642
    https://www.cve.org/CVERecord?id=CVE-2026-31630
    (* Security fix *) patches/packages/linux-5.15.209/kernel-modules-5.15.209-x86_64-1.txz: Upgraded.
    patches/packages/linux-5.15.209/kernel-source-5.15.209-noarch-1.txz: Upgraded.
    Be sure to upgrade your initrd after upgrading the kernel packages.
    If you use lilo to boot your machine, be sure lilo.conf points to the correct
    kernel and initrd and run lilo as root to update the bootloader.
    If you use elilo to boot your machine, you should run eliloconfig to
    copy the
    kernel and initrd to the EFI System Partition.
    +--------------------------+
    -8<--------------------------------------------

    Please note the last lines about the need to manually updating your
    bootloader and any initrd.

    regards Henrik
    --- Synchronet 3.22a-Linux NewsLink 1.2