So, firstly, about the nomenclature: initrd (initial ram disk) and initramfs (initial ram file system) are usually used interchangeably as far as I know. For example, even though my Debian uses initramfs-tools
, the generated images are called /boot/initrd.img-*
. (Edit: There is a technical difference but an initramfs may be referred to as an initrd (like in this case) due to how similar they are.)
For example, when installing a kernel, apt
shows this output on my Debian machine:
linux-image-6.12.6-amd64 (6.12.6-1) wird eingerichtet ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.12.6-amd64
What you're talking about is probably the software used to generate this initial ramdisk, which on Debian is done using initramfs-tools
(which contains the mkinitramfs
command), while on other distros dracut
(command: mkinitrd
) might be used.
I will say it strikes me as weird that Devuan doesn't use initramfs-tools
since it's a Debian derivative. Maybe you are mistaken about this? Possibly no initrd/initramfs is used at all on this specific Pi version of Devuan? IDK.
Edit: See my other comment. I'm wrong. There is an actual technical difference between initrd and initramfs, but I don't think that's actually relevant in this situation. Or rather, both are functionally the same, so it doesn't really matter from the perspective of the user or distro that there's a difference. I will keep the rest of the comment as is, since I do reckon OP's problem is unrelated to this difference, and that probably something else is tripping up OP.
Yeah sorry then. It would be good to not use
ls
in your example though, someone who doesn't know about that might read this discussion and think that's reasonable.As for your original question, doing the
foreach
as a personal alias is fine. I wouldn't use it in any script, since if anyone else reads that, they probably already know aboutxargs
. So using yourforeach
would be more confusing to any potential reader I think.