Comment 9 for bug 1892367

------- Comment From <email address hidden> 2020-11-10 10:24 EDT-------
The zdev:early parameter in the chzdev command is a work-around for this issue.

The Actual issue is,the fact that unlike SUSE or Red Hat, Canonical always want to copy all udev rules to the initial RAM-disk. As this is different between distributions, we cannot just change zdev to always update the RAM-disk as this would potentially introduce problems with SUSE and Red Hat distributions.

As discussed internally with the team, what could be done is, to provide a build-time switch, a MACRO that allows Canonical to specify that whenever a persistent device configuration changed, the RAM-disk is updated (this could be implemented via a modified root_check() function in s390-tools/zdev/root.c that only returns if a persistent device configuration was changed).
The functionality mentioned above is same as having "zdev:early=1" on this usecase. But, we would like to avoid this extra parameter and make it work like other distros.

We would like to get a go from Canonical on this.