Skip to main content
Topic: [HELP] changing OpenRC-init to sysVinit (Read 758 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[HELP] changing OpenRC-init to sysVinit

Hi, i just converted my arch to OpenRC successfully, for some reasons i need SysVinit since quiet boot argument don't work on openrc's default init. I referred to arch's wiki for sysVinit(AUR) but when i makepkg -si pacman gives me this error:

[qasim@qasim sysvinit]$ sudo pacman -U sysvinit-3.06-1-x86_64.pkg.tar.zst
[sudo] password for qasim:
loading packages...
resolving dependencies...
looking for conflicting packages...

Packages (1) sysvinit-3.06-1

Total Installed Size:  0.26 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                                     [####################################] 100%
(1/1) checking package integrity                                   [####################################] 100%
(1/1) loading package files                                        [####################################] 100%
(1/1) checking for file conflicts                                  [####################################] 100%
error: failed to commit transaction (conflicting files)
sysvinit: /bin exists in filesystem (owned by filesystem)
sysvinit: /sbin exists in filesystem (owned by filesystem)
sysvinit: /sbin/poweroff exists in filesystem
sysvinit: /sbin/reboot exists in filesystem
sysvinit: /usr/bin/halt exists in filesystem (owned by openrc)
sysvinit: /usr/bin/init exists in filesystem (owned by base)
sysvinit: /usr/bin/shutdown exists in filesystem (owned by openrc)
Errors occurred, no packages were upgraded.

Kindly help me out on how can change openrc-init to SysVinit(init-openrc)


Re: [HELP] changing OpenRC-init to sysVinit

Reply #1
.., for some reasons i need SysVinit ...

I would list the reasons in detail.
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "

Re: [HELP] changing OpenRC-init to sysVinit

Reply #2
i think better software compatibility and flexibility like grub's quiet and plymouth

Re: [HELP] changing OpenRC-init to sysVinit

Reply #3
Try "man PKGBUILD" and modify the PKGBUILD to clear the conflicts, it should probably conflict and replace OpenRC, check the PKGBUILD's of OpenRC and other inits for suggestions. Make sure you can chroot into your system because most likely it will take many modifications to get it working and bootable, unless someone has some simple step by step guide. It might be easier to set up plymouth with OpenRC rather than install sysvinit but there's no reason not to try if you like.

Re: [HELP] changing OpenRC-init to sysVinit

Reply #4
I'm pretty sure grub's quiet argument has nothing to do with any init.

Re: [HELP] changing OpenRC-init to sysVinit

Reply #5
If you think openrc is the source of the issue and you want to stay with an Artix supported init then I would think trying either "runit" or "dinit" would be fairly straight forward.
S6 is very different and not something as easy to switch to as "runit" or "dinit".
Artix supports these inits and the service scripts for common services are for the most part present.

The major caveat of switching to "sysvinit" as init means that you are essentially building your own Arch clone distribution.
You will have an unique setup that no one here has.
The end result would mean limited or no help will be available should the need arise.
The risk of breaking the system is high unless you know what you are doing.

Modify the PKGBUILD like this if you want to proceed:
Code: [Select]
conflicts=('systemd-sysvcompat' 'openrc' 'runit' 'dinit' 's6')
replaces=('systemd-sysvcompat' 'openrc' 'runit' 'dinit' 's6')
Caution is advised.