#115 Issue closed: fedora17: systemd is broken (booting blocks)

Labels: bug

gdha opened issue at 2012-06-21 13:17:

Apparently after changes made to /lib into /usr/lib on Fedora 17 systemd seems to be broken. I could fix most systemd stuff after moving the /lib to /usr/lib in our skel structure. However, it still blocks at

[FAILED] Failed to start Rear run-syslog script.
                See 'systemctl status rsyslog.service' for details.

However, nothing happens after this point - no prompt. A bit more debugging is required...

gdha commented at 2012-06-25 13:53:

commited changes to the skel tree (mv /lib to /usr/lib). Need some more testing as Jeroen changed usr/share/rear/build/GNU/Linux/39_copy_binaries_libraries.sh

gdha commented at 2012-06-26 13:57:

it works again - /usr/lib/systemd is the main track to use.

jhoekx commented at 2012-06-26 14:03:

Gratien, wouldn't it be useful to link /lib/systemd to /usr/lib/systemd to not break previous fedora versions?

gdha commented at 2012-06-27 07:12:

/lib is linked to /usr/lib - so that is covered

On Tue, Jun 26, 2012 at 4:03 PM, Jeroen Hoekx <
reply@reply.github.com

wrote:

Gratien, wouldn't it be useful to link /lib/systemd to /usr/lib/systemd to
not break previous fedora versions?


Reply to this email directly or view it on GitHub:
https://github.com/rear/rear/issues/115#issuecomment-6576353


[Export of Github issue for rear/rear.]