dracut: depend on net-lib module

[LaszloGombos]

[Discuss dracut upstream change]

Somewhat abusing the PR process a bit I wanted to reach out from the dracut upstream team to get feedback on an upstream PR that we hope would benefit this project as well.

Upstream dracut is considering to introduce a new dracut module called net-lib that would manage installing net-lib.sh (so that bootengine does not need to do that "manually)

dracutdevs/dracut#2250

If upstream lands, that would be only be release around Dec this year or later, so plenty of time to coordinate this work.

Please feel free to comment directly on the upstream bug (and if desired close this PR)

[pothos]

Thanks for reaching out, good to know that when updating

[LaszloGombos]

@pothos would you say that this is a welcomed/good change from your project perspective ?

[pothos]

No real opinion, I think we only use the ip_to_var function of it in our parse-ip-for-networkd.sh script

[LaszloGombos]

@pothos The more I learn about Flatcar Linux the more I think this is a great and fascinating way to deploy Linux.

I noticed that https://github.com/flatcar/scripts/tree/main/sdk_container/src/third_party/coreos-overlay/sys-kernel/dracut seem to point to a somewhat old version of dracut. Is this version in use for Flatcar. If in use, can I help in any way to update this version ?

I also did noticed that https://github.com/flatcar-hub/gentoo/tree/master/sys-kernel/dracut point to an up-to-date version of dracut, but I was not able to comprehend how the very different versions of dracut actually used.

Please let me know if there is a better way to engage with the project than this issue.

[pothos]

I noticed that https://github.com/flatcar/scripts/tree/main/sdk_container/src/third_party/coreos-overlay/sys-kernel/dracut seem to point to a somewhat old version of dracut. Is this version in use for Flatcar. If in use, can I help in any way to update this version ?

Thanks! Yes, that is the file that needs updating following these steps. For PRs there is a CI run that we have to trigger - it helps if you have a local build env but it's not a hard requirement.

The other gentoo repo is for upstream PRs.