You are not logged in.
Today, when I upgraded my Arch, I got the following message:
:: Replace sysvinit-tools with core/procps-ng? [Y/n]
I didn't find anything in the news. I later chose 'yes', but I wanted to know what this message means, just curiosity. Doesn't sysvinit is a init daemon, like systemd?
└─[$] <> sudo pacman -Syyuu
[sudo] password for thiago:
:: Synchronizing package databases...
core 105.3 KiB 932K/s 00:00 [----------------------------------------------------] 100%
extra 1521.8 KiB 1208K/s 00:01 [----------------------------------------------------] 100%
community 2.0 MiB 1199K/s 00:02 [----------------------------------------------------] 100%
multilib 109.4 KiB 1032K/s 00:00 [----------------------------------------------------] 100%
:: Starting full system upgrade...
:: Replace sysvinit-tools with core/procps-ng? [Y/n] n
resolving dependencies...
looking for inter-conflicts...
:: procps-ng and sysvinit-tools are in conflict. Remove sysvinit-tools? [y/N] ^C
Interrupt signal receivedOffline
$ pkgfile -l sysvinit-tools | grep bin
core/sysvinit-tools /usr/bin/
core/sysvinit-tools /usr/bin/bootlogd
core/sysvinit-tools /usr/bin/fstab-decode
core/sysvinit-tools /usr/bin/killall5
core/sysvinit-tools /usr/bin/last
core/sysvinit-tools /usr/bin/lastb
core/sysvinit-tools /usr/bin/pidof
$ pacman -Ql procps-ng | grep bin
procps-ng /usr/bin/
procps-ng /usr/bin/free
procps-ng /usr/bin/pgrep
procps-ng /usr/bin/pidof
procps-ng /usr/bin/pkill
procps-ng /usr/bin/pmap
procps-ng /usr/bin/ps
procps-ng /usr/bin/pwdx
procps-ng /usr/bin/slabtop
procps-ng /usr/bin/sysctl
procps-ng /usr/bin/tload
procps-ng /usr/bin/top
procps-ng /usr/bin/uptime
procps-ng /usr/bin/vmstat
procps-ng /usr/bin/w
procps-ng /usr/bin/watch
$ pacman -Qi procps-ng | grep Replace
Replaces : procps sysvinit-toolssysvinit-tools is not an init system, it was a package that provided tools that used to be associated with sysvinit. Procps-ng now provides those sames tools and thus replaces sysvinit-tools.
EDIT: oops - many of the tools in sysvinit-tools are not provided by procps-ng. pidof is the only one I'd use anyways, and that one is covered. Perhaps the others are specific to sysvinit, I'm not sure.
Last edited by Trilby (2013-12-09 15:49:38)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
OK, great. Thanks for the concise but clarifying explanation, Trilby.
Now I see this (changed procps-ng) and this (sysvinit-tools).
Actually, these links from arch-commits just show the changes, "upstream update" wouldn't really catch my attention at first, but OK
.
EDIT: yeah, I realized that too, but I never used these tools, so I guess it won't affect me.
Last edited by thiagowfx (2013-12-09 16:01:13)
Offline
So is it safe to replace, or will something break?
Offline
So is it safe to replace, or will something break?
Yes, it is supposed to be replaced. It is perfectly safe,
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline
Offline
EDIT: oops - many of the tools in sysvinit-tools are not provided by procps-ng. pidof is the only one I'd use anyways, and that one is covered. Perhaps the others are specific to sysvinit, I'm not sure.
https://mailman.archlinux.org/pipermail … 25581.html
The next release of procps-ng will contain pidof and clash with sysvinit-tools.
$ pacman -Qo /usr/bin/pidof
/usr/bin/pidof is owned by procps-ng 3.3.9-1Offline
EDIT: oops - many of the tools in sysvinit-tools are not provided by procps-ng. pidof is the only one I'd use anyways, and that one is covered. Perhaps the others are specific to sysvinit, I'm not sure.
If you ever need killall5, you could use the busybox variant. For fstab-decode and bootlogd you might have to create your own package because of the conflict.
Last edited by progandy (2013-12-10 09:52:07)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline