will systemd-shim affect antiX?

Forum Forums News News will systemd-shim affect antiX?

This topic contains 4 replies, has 3 voices, and was last updated by dolphin_oracle May 9-5:50 am.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #21324
    Member
    linuxdaddy
    linuxdaddy

    Will the systemd-shim problem D.O. posted on distrowatch affect antiX
    and what’s being looked at and proposed as possibilities?

    Normal == 🙂
    depends on the surrounding crowd ?!

    #21325
    Member
    caprea
    caprea

    At least not on the direct way, antiX does not need and never needed systemd-shim.

    #21350
    Forum Admin
    dolphin_oracle
    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.

    #21352
    Member
    linuxdaddy
    linuxdaddy

    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.

    Normal == 🙂
    depends on the surrounding crowd ?!

    #21358
    Forum Admin
    dolphin_oracle
    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.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.