Summary: | sys-apps/systemd-234: symlink does not work with dracut | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Maciej Piechotka <uzytkownik2> |
Component: | Current packages | Assignee: | Gentoo systemd Team <systemd> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Maciej Piechotka
2017-07-17 18:59:24 UTC
Thanks for reporting this. The news item does mention that you should rebuild your initramfs after upgrading -- that should cause /lib/systemd/systemd to be called directly. I guess it really has more to do with your kernel command line (init=/lib/systemd/systemd). Anyway, I'll look into using a relative symlink again. Yes. Sorry for not being clear enough - I meant init= (removing /usr fixed the problem). I just tested with init=/usr/lib/systemd/systemd, and did not have any trouble booting with a dracut-045 initramfs. Please provide more exact instructions to reproduce the problem. https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fe9f13cf6189140f1e89481cb87a0f544a50657c commit fe9f13cf6189140f1e89481cb87a0f544a50657c Author: Mike Gilbert <floppym@gentoo.org> Date: Tue Jul 18 12:56:24 2017 -0400 sys-apps/systemd: use relative symlinks for systemd and systemd-shutdown Bug: https://bugs.gentoo.org/625462 Package-Manager: Portage-2.3.6_p16, Repoman-2.3.2_p84 sys-apps/systemd/{systemd-234-r1.ebuild => systemd-234-r2.ebuild} | 4 ++-- sys-apps/systemd/systemd-9999.ebuild | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) |