The fix was not supposed to solve the problem of already broken systems. However, reinstalling systemd-sysv-utils should always bring back a correct /sbin/init (which is a symlink). /usr/lib has always been a symlink to lib64 (and /lib is a symlink to lib64).
On Wed, Mar 26, 2014 at 6:20 PM, pierigno <[email protected]> wrote: > still no luck. > > eselect-init was already removed by last update. > > > my grub menu entry has init=/linuxrc but the error message says it > cannot find valid init at /sbin/init init=/linuxrc can be safely removed (genkernel ignores it, actually). If /sbin/init is correctly configured and you don't have a separate /usr (or genkernel is correctly mounting it for you), then the problem is elsewhere and not related to the last changes implemented in systemd. > > After equo install systemd-sysvinit-utils-208 I get: > > # ls -al /sbin/init > lrwxrwxrwx 1 root root 24 26 mar 13.43 /sbin/init -> > ../usr/lib/systemd/systemd Yes, this is correct. This leads me to believe that the problem is elsewhere. Also, I saw in your logs that you have anaconda installed on your system, this looks completely wrong, how did you get that system installed? > > # ls -al /usr/lib > lrwxrwxrwx 1 root root 11 29 gen 2012 /usr/lib -> /usr/lib64/ > > > > Maybe /usr/lib should link to ../usr/lib64 also? I don't have a > virtual machine at the moment to test it though > > > > 2014-03-26 13:11 GMT+00:00 Fabio Erculiani <[email protected]>: >> I should have fixed the issue in the repositories. There are now new >> systemd (from sabayon-distro instead of systemd-love overlay) and >> systemd-sysv-utils (this one blocks eselect-init). >> >> -- >> Fabio Erculiani >> > -- Fabio Erculiani
