Email or username:

Password:

Forgot your password?
Top-level
Ariadne Conill 🐰

@sertonix s6-rc being at feature parity with openrc (which also lacks features wanted in alpine) isn’t a good argument.

s6-rc also lacks a good user interface story, at least in terms of how alpine tools are supposed to feel and be invoked. alpine tools are very much about noun/verb invocation (think: apk add foo, lbu commit /dev/fd0, etc), while s6-rc uses switches for everything.

the main thing missing is event handling, for example launching cups to print only when you’re printing, rather than having it always running and wasting memory. or launching iwd when you plug in a usb wifi stick, or whatever.

openrc’s “hotplug” run level is too clunky to be usable.

2 comments
Sertonix

@ariadne
With the interface I understand what you mean. But if you look at things like alpine-conf these are wrapper script for alpine linux specifically. It wouldn't be fair to compare it with a tool that targets portability. We could add rc-service like commands very easily.

Even if s6-rc doesn't have native event handling it should be easy to create an event handler service that starts/stops services on events. (to be tested)

Ariadne Conill 🐰

@sertonix sure, alpine could build its own frontend to s6-rc.

but then alpine will have to also build suitable replacement polyfills for everything else that is presently buggy.

or alpine could use systemd and allocate resources to other projects.

Go Up