Description of problem: Booting with initrd generated by mkinitrd 5.0.2-1 or 5.0.3-1 spits the following messages: .... Switching to new root error dup2'ing fd of 54 to 1: No such file or directory error dup2'ing fd of 54 to 2: No such file or directory This was not the case for 5.0.0-1 and earlier. fd of 54 is from x86_64; on x86 machine I see 72 instead. Version-Release number of selected component (if applicable): mkinitrd-5.0.2-1 and mkinitrd-5.0.3-1 How reproducible: always
Does this still appear to be a problem with more recent versions?
> Does this still appear to be a problem with more recent versions? No, I did not see that for quite a while.