* [gentoo-user] [~amd64] Hint for bonehead systemd users (like me)
@ 2013-09-12 0:08 walt
0 siblings, 0 replies; only message in thread
From: walt @ 2013-09-12 0:08 UTC (permalink / raw
To: gentoo-user
I've been struggling with today's update of systemd on ~arch because the
ebuild keeps accusing me of using a "compatibility symlink to run systemd"
during bootup.
Yes, guilty as charged, I told grub2 to use /usr/bin/systemd as 'init', when
/usr/bin/systemd has been, until now, a symlink to /usr/lib/systemd/systemd.
Yes, I pled guilty to this crime and changed my /boot/grub2/grub.cfg to use
/usr/lib/systemd/systemd instead of /usr/bin/systemd -- and yet I got the
same condemnation every time I tried to emerge -auND world.
An additional glass of chardonnay didn't solve this frustration, so I dared
to read the systemd ebuild, which confessed that it reads the value of
/proc/1/cmdline to find me guilty and ignores my new /boot/grub2/grup.cfg,
which would have proved my innocence.
IOW, you must reboot after changing your grub.cfg before the ebuild will
withdraw it's accusation.
HTH someone avoid the same problem.
Cheers :)
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-09-12 0:09 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-09-12 0:08 [gentoo-user] [~amd64] Hint for bonehead systemd users (like me) walt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox