OpenRC is a dependency based init system that works with the system provided init program, normally /sbin/init.

Installation procedure and more information about it available here.

There's actually a project also that imported OpenRC as a full package as well.

https://github.com/w41l/wlsbuild/tree/master/openrc

The author, if it is him, wrote an article on it:

http://www.walecha.web.id/blog/2015/...-dengan-openrc

Both projects are good efforts. Might try it out soon.

1 members found this post helpful.

Just to avoid confusion, the SlackBuilds mentioned by ReaperX7 in the post above are from a different author and predate my efforts.

My SlackBuilds can be found here.

2 members found this post helpful.

Ah thank you.

Do you have a git or svn of the collective work?

Update:

I got OpenRC working with a few modifications of my own. Wasn't easy. A few hiccups, like NetworkManager not cooperating (nothing new as I had issues with it on Runit being a PITA), and Parallel mode seems to be limited due to the way the dependencies are resolved in the scripts (I'm checking this against Funtoo's OpenRC scripts to see what I can optimize), but so far... not too bad.

One thing is for certain, work still is needed to clean up many dependencies in the trees for parallel, but overall it works, and actually stays out of the way.

Dunno why NetworkManager did not work at your end, seems to work here.

The scripts are sourced from the gentoo packages and placed in a git repository. Any modification that is necessary is done at install time by the install* scripts.

Source: https://bitbucket.org/aadityabagga/openrc-services/src

Original source: https://sources.gentoo.org/cgi-bin/v...gi/gentoo-x86/

NetworkManager is finicky as it is. I did get dhcpcd working better. I'm going to keep at it to see how it goes. This software seems interesting.

Some small suggestions:

1.) In /etc/inittab, you should change this:

To this:

This leaves the boot text intact for last minute reviews when starting from the Console rather than X.

2.) The iptables scripts need to point to /usr/sbin rather than /sbin for the iptables tools.

3.) You also should assign the following to boot: fuse, udev, udev-postmount, sysklogd, and alsasound

You should add these to default: consolekit, sshd, acpid, atd (and NetworkManager or dhcpcd)

These, by default, are enabled in Slackware natively with the bsd-scripts.

4.) Check the /path/to of each init script if they have any absolute path entries. Usually this can be solved by exporting a path sequence setting:

per script. This will greatly simplify path resolving for scripts trying to execute binaries.

Otherwise.... Aaditya... This is way too cool. Love it. Love it. Love it.

You should push this to SlackBuilds.org (pending my suggestions).

3 members found this post helpful.

1. Instead of editing inittab, I guess /etc/rc.conf could be edited to set RC_LOGGER=yes, this way the boot logs could be stored in /var/log/rc.log (by default) and retrieved later when required.

2. Corrected.

3. I think I will leave it upto the user to decide which services they want to start, some common ones are listed in the README as well as in the article on docs.slackware.org.

Thx for the feedback

1 members found this post helpful.

I added a 4th, but regardless, udev and udev-postmount are needed for hardware detection. The rest are trivial, but this could be added into the README.Slackware for noting.

Otherwise, this is shaping up rather nicely.

I was able to boot up my system without the udev service (udev-postmount is used with eudev I think).

I booted up an old copy of System Rescue CD that I had and which uses OpenRC, and udev was in the sysinit runlevel.

From my limited understanding, the services in sysinit runlevel get started first, followed by those in boot and then in default.

After some introspection and looking at the enabled services in the System Rescue CD, I decided to enable the following services by default by adding them to the sysinit runlevel: udev, udev-postmount, and kmod-static-nodes.

SlackBuild updated with above changes.

Also, users who use dmcrypt, lvm, or mdraid could add the following services respectively to the boot runlevel:

Although not really a target goal, parallel mode with dependency enforcement enabled boots my system up in about 7 seconds.

Another needed fix, nvidia-persistenced, if I'm not mistaken, is located in /usr/bin rather than /opt/bin (actually this script is not installed but is useful so adding it to the install list might be wise). Same as nvidia-smi and nvidia-settings for the path fixes. The ati drivers might be in the same /usr/sbin directory listing.

Lastly, the other OpenRC project has some scripts for fontcache, ldconfig, glibschema, iconcache, and gtkmodules. (These work well to keep the system themes, cache, etc. up to date.) Importing these might be a good idea.

Package is stable here, so, hopefully you can get this up on SBo.

Added nvidia-persistenced and changed the path for it as well as nvidia-smi, I dont use it so I dont know if it works though...

For ati I dont see a package in SBo, so I guess I will not change the path for that.

I could not find the files for fontcache, ldconfig, glibschema, iconcache or gtkmodules, if you can locate them I could add them. As an alternative one could create a script for them in the /etc/local.d directory (see /etc/local.d/README for more details), by copying the relevant portions from /etc/rc.d/rc.M.

I think I will wait another week before submitting to SBo to see if more bugs can be discovered and fixed

I have the URLs here (I forgot about mimedatabase):

https://github.com/w41l/wlsbuild/blo...it.d/fontcache
https://github.com/w41l/wlsbuild/blo...d/mimedatabase
https://github.com/w41l/wlsbuild/blo...nit.d/ldconfig
https://github.com/w41l/wlsbuild/blo...it.d/iconcache
https://github.com/w41l/wlsbuild/blo...t.d/gtkmodules
https://github.com/w41l/wlsbuild/blo....d/glibschemas

These should help.

Also, on a side note for anyone interested:

To combat the problem of using bsd-style init or OpenRC with packages, I added a small tool inside my SlackBuild scripts at SlackWorks such as follows:

This autodetects the init system in usage (whether it be sysvinit or OpenRC) and does or doesn't create the appropriate system directory as needed to avoid unneeded scripts being placed in the wrong directories.

A similar trigger will be needed in doinst.sh as well, but this does work very effectively.

This might be useful for any package using a custom init script for Slackware.

Also, due to the fact there are things being loaded from the schemas and cache being updated, the boot process will take longer than normal, but on average with everything going, my boot time is about 35-55 seconds depending on what I have enabled for boot time.

Honestly, everything is working, minus ip6tables, which is probably a kernel issue, but overall it works well enough to be release worthy.

I would make sure all the init scripts that are usable by Linux are installed.

Aaditya, you have done well and wisely. Pat yourself on the back kiddo, you just brought Slackware an alternative and completed init system.

The above look custom made, I was looking more for Gentoo provided ones.

Also, as these services are mostly oneshot, I think they are more appropriate as a script in /etc/local.d. So I added rcM.start, which will be installed but will be not be enabled by default. To enable it one can do:

openrc-services SlackBuild updated with this change.

Testing well so far. No problems found.

1 members found this post helpful.