- This topic has 4 replies, 3 voices, and was last updated May 9-5:50 am by dolphin_oracle.
-
Posts
-
Anonymous
Will the systemd-shim problem D.O. posted on distrowatch affect antiX
and what’s being looked at and proposed as possibilities?
caprea
At least not on the direct way, antiX does not need and never needed systemd-shim.
dolphin_oracle
it won’t affect antiX at all. In fact, the movements toward elgoind feature parity with systemd-logind, as well as libelogind0 being at parity with libsystemd0, makes life a little easier on antiX.
thx caprea and dolphin_oracle for clarifying that, I wasn’t sure right off hand
if MX has to switch bases how it would affect..since both use the same build tools.
and the same debian repos and share some development
And also how deep and dark systemd goes.
I’m sure if there was any concerns you or anti would post some news on it.dolphin_oracle
thx caprea and dolphin_oracle for clarifying that, I wasn’t sure right off hand
if MX has to switch bases how it would affect..since both use the same build tools.
and the same debian repos and share some development
And also how deep and dark systemd goes.
I’m sure if there was any concerns you or anti would post some news on it.it can be confusing, but we really aren’t switching bases. the main impact is that we can’t have systemd and sysVinit installed at the same time, which is what MX currently does. so we have to pick 1.
- You must be logged in to reply to this topic.
