• Bug#1082657: /scripts/local-bottom/mdadm: 2: /scripts/local-bottom/mdad

    From Daniel Baumann@21:1/5 to All on Tue Jul 22 16:30:01 2025
    Hi,

    hmm.. I had a look at this several times, however, I coudn't find out
    why 'rm' isn't working at that stage/place in initramfs, where it
    clearly works before or afterwards for other packages.

    I'll give it another go tomorrow.

    Regards,
    Daniel

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Chris Hofstaedtler@21:1/5 to Daniel Baumann on Tue Jul 22 17:20:01 2025
    On Tue, Jul 22, 2025 at 04:18:10PM +0200, Daniel Baumann wrote:
    hmm.. I had a look at this several times, however, I coudn't find out why 'rm' isn't working at that stage/place in initramfs, where it clearly works before or afterwards for other packages.

    I just had another look at this bug. It happens only on machines
    which do not have "busybox" installed.

    IIRC initramfs-tools can use various tools either from busybox or
    from coreutils and klibc-utils. I *guess* if busybox is installed,
    busybox and all links to it get installed unconditionally. This does
    not happen if busybox is not installed.

    Probably the easy way out is to unconditionally have the mdadm hook
    script install /bin/rm into the initramfs.

    Chris

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)