Systemd-220 with OpenMandriva Lx 3 using dracut-041 After rebuilding initrd to get use of new systemd, my system stop to boot on initrd stage. Systemd boot drop to dracut shell and i get error: systemd-fsck-root.service: Failed at step EXEC spawning /usr/lib/systemd/systemd-fsck: No such file or directory systemctl status systemd-fsck-root.service points to a file /run/systemd/generator/systemd-fsck-root.service which contain this: ExecStart=/usr/lib/systemd/systemd-fsck /dev/disk/by-uuid/SOME-UUID Above is wrong, because systemd-fsck lives in /lib/systemd because of used --split-usr Please fix this, as this is a regression from 219.
Sounds like this is a potential culprit http://cgit.freedesktop.org/systemd/systemd/commit/src/fstab-generator/fstab-generator.c?id=2e8522767e27d5686206794c69e0aa95da6e798b
Fixed in http://cgit.freedesktop.org/systemd/systemd/commit/?id=77eb82f9f0.
Thanks. For a future releases, it would be nice to at least to a give mimimal testing for systemd how it performs on a real installation, jut to avoid such issues.
(In reply to Tomasz Paweł Gajc from comment #3) > Thanks. > > For a future releases, it would be nice to at least to a give mimimal > testing for systemd how it performs on a real installation, jut to avoid > such issues. We do test systemd regularly, but not in all configurations, and not in the specific configuration chosen by OpenMandriva. And we cannot really do that, as we have so many options that explode the test matrix. We rely on downstream to test things for us in the configuration they need if they want their configuration to be first class supported. We of course try to keep things working for everybody in all configurations, but this will break unless tested, and we don't have the manpower to test all ourselves.
(In reply to Lennart Poettering from comment #4) > We do test systemd regularly, but not in all configurations, and not in the > specific configuration chosen by OpenMandriva. And we cannot really do that, > as we have so many options that explode the test matrix. > > We rely on downstream to test things for us in the configuration they need > if they want their configuration to be first class supported. We of course > try to keep things working for everybody in all configurations, but this > will break unless tested, and we don't have the manpower to test all > ourselves. Lennart i appreciate your concern, please notice there are still few distros out there which are using --split-usr. You are still supporting this feature, so testing is also required. Anyways thanks for resolving this.
(In reply to Tomasz Paweł Gajc from comment #5) > (In reply to Lennart Poettering from comment #4) > > > We do test systemd regularly, but not in all configurations, and not in the > > specific configuration chosen by OpenMandriva. And we cannot really do that, > > as we have so many options that explode the test matrix. > > > > We rely on downstream to test things for us in the configuration they need > > if they want their configuration to be first class supported. We of course > > try to keep things working for everybody in all configurations, but this > > will break unless tested, and we don't have the manpower to test all > > ourselves. > > Lennart i appreciate your concern, please notice there are still few distros > out there which are using --split-usr. You are still supporting this > feature, so testing is also required. No. We support this only to the level the community is willing to test this. We will not test this in the systemd core team, we do not use any distro that still needs that.
Ok i understand that. For i furthere releases of systemd i'll try to do more testing before i mush new version for OpenMandriva.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.