Arch Linux

Shelly

Member

Registered: 2012-03-10

Posts: 9

[SOLVED] systemd-sysvcompat /sbin/init exists in filesystem

Hi,

I switched to systemd a few weeks ago, everything worked fine, but now these errors occurred running

pacman -Syu

systemd-sysvcompat: /sbin/halt exists in filesystem
systemd-sysvcompat: /sbin/init exists in filesystem
systemd-sysvcompat: /sbin/poweroff exists in filesystem
systemd-sysvcompat: /sbin/reboot exists in filesystem
systemd-sysvcompat: /sbin/runlevel exists in filesystem
systemd-sysvcompat: /sbin/shutdown exists in filesystem
systemd-sysvcompat: /sbin/telinit exists in filesystem
systemd-sysvcompat: /usr/share/man/man8/halt.8.gz exists in filesystem
systemd-sysvcompat: /usr/share/man/man8/poweroff.8.gz exists in filesystem
systemd-sysvcompat: /usr/share/man/man8/reboot.8.gz exists in filesystem
systemd-sysvcompat: /usr/share/man/man8/runlevel.8.gz exists in filesystem
systemd-sysvcompat: /usr/share/man/man8/shutdown.8.gz exists in filesystem
systemd-sysvcompat: /usr/share/man/man8/telinit.8.gz exists in filesystem

Any ideas?

Last edited by Shelly (2012-10-01 10:24:50)

Ramses de Norre

Member

From: Leuven - Belgium

Registered: 2007-03-27

Posts: 1,289

Re: [SOLVED] systemd-sysvcompat /sbin/init exists in filesystem

  pacman -Qo /sbin/init

Shelly

Member

Registered: 2012-03-10

Posts: 9

Re: [SOLVED] systemd-sysvcompat /sbin/init exists in filesystem

pacman -Qo /sbin/init
error: No package owns /sbin/init

I forgot to mention this:

pacman -Syu
looking for inter-conflicts...
:: util-linux and eject are in conflict. Remove eject? [y/N] y

Ramses de Norre

Member

From: Leuven - Belgium

Registered: 2007-03-27

Posts: 1,289

Re: [SOLVED] systemd-sysvcompat /sbin/init exists in filesystem

You must have done something pretty strange to have those files without them belonging to some package... I guess the only way to proceed is to delete the files manually (or force the install of systemd-sysvcompat).
Maybe you should try to figure out what could've caused this as well, because this shouldn't happen. Is /sbin/init a symlink to the systemd binary or the sysv init binary (or is that a script?)?

techryda

Member

Registered: 2012-10-01

Posts: 50

Re: [SOLVED] systemd-sysvcompat /sbin/init exists in filesystem

What repos do you have enabled? w/o following the mailing list you never know whats going on in testing.

I'm not sure how those files got unowned, but assuming you just have core, extra, and community enabled. The following should get you fixed up.

pacman -Syu --ignore systemd-sysvcompat && pacman -Sf systemd-sysvcompat

Go ahead and say Yes to the question about removing eject

Last edited by techryda (2012-10-01 10:15:54)

Shelly

Member

Registered: 2012-03-10

Posts: 9

Re: [SOLVED] systemd-sysvcompat /sbin/init exists in filesystem

You must have done something pretty strange to have those files without them belonging to some package... I guess the only way to proceed is to delete the files manually (or force the install of systemd-sysvcompat).
Maybe you should try to figure out what could've caused this as well, because this shouldn't happen. Is /sbin/init a symlink to the systemd binary or the sysv init binary (or is that a script?)?

ll /sbin/init                                                           
lrwxrwxrwx 1 root root 26 Sep 28 02:58 /sbin/init -> ../usr/lib/systemd/systemd

What repos do you have enabled?

core, extra, community, multilib, archlinuxfr

This solved the problem:

pacman -Syu --ignore systemd-sysvcompat && pacman -Sf systemd-sysvcompat

Go ahead and say Yes to the question about removing eject

Thanks techryda & Ramses de Norre

techryda

Member

Registered: 2012-10-01

Posts: 50

Re: [SOLVED] systemd-sysvcompat /sbin/init exists in filesystem

Glad that worked for you.  Ramses de Norre is right though, the state your system was in should never have happened.  Try to figure out what might have caused it.
/var/log/pacman.log is a good place to start looking.