Hi

Regarding the patching of the "mdraid" code, modules.d/90mdraid/parse-md.sh, to reduce the code amount maintained in ipfire, would it be an idea to rather patch this part of the original dracut code

if { [ -z "$MD_UUID" ] && ! getargbool 0 rd.auto; } || ! getargbool 1 rd.md -d -n rd_NO_MD; then info "rd.md=0: removing MD RAID activation" udevproperty rd_NO_MD=1 else # rewrite the md rules to only process the specified raid array

I.e. to rather patch it to if false; then info "rd.md=0: removing MD RAID activation" udevproperty rd_NO_MD=1 else # rewrite the md rules to only process the specified raid array

That would save about 25 lines of patch code that needs to be maintained, and you would just have one simple line of patch to maintain.

Or is the rationale that if dracut ever changes the code related to mdraid, you want your patch to run into conflict, so you get a hint that you need to put some extra testing effort into systems with mdraid ?

I also read the dracut documentation, to try to understand if you could rather send in some of the parameters that it checks, as part of the dracut invocation, but was unable to figure it out. To me, it seems like these parameters are picked up from the kernel command line from boot.

Regards Alf