Announcement

Collapse
No announcement yet.

Fedora To Finish Phasing Out System V Init Scripts

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Fedora To Finish Phasing Out System V Init Scripts

    Phoronix: Fedora To Finish Phasing Out System V Init Scripts

    Fedora will be finishing up their System V to systemd unit migration in the months ahead...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Doesn't systemd offer basic System V compatibility? Is it Fedora's policy to specifically disallow such packages in the interest of cohesion?

    Comment


    • #3
      Originally posted by emblemparade View Post
      Doesn't systemd offer basic System V compatibility? Is it Fedora's policy to specifically disallow such packages in the interest of cohesion?
      Yeah systemd guarantees compatibility, this announcement states that if you have a package that still relies on a sysV init script and not a .service file then your package will be auto-dropped from the Fedora repos. You can appeal for an exception, on case-by-case basis, to FESCo. They are not removing systemd compatibility with sysv, however, because they do not want to break legacy third party software that cannot be updated.
      All opinions are my own not those of my employer if you know who they are.

      Comment


      • #4
        Originally posted by emblemparade View Post
        Doesn't systemd offer basic System V compatibility? Is it Fedora's policy to specifically disallow such packages in the interest of cohesion?
        The intention is basically that if you're creating a package for the Fedora repositories, that package must follow the Fedora way of starting services, instead of falling back to SysV compatibility.

        It doesn't mean that upstream developers have to support systemd, nor that third-party packages can't use SysV - only that packages that are officially part of Fedora must follow Fedora conventions.

        Comment


        • #5
          Originally posted by emblemparade View Post
          Doesn't systemd offer basic System V compatibility? Is it Fedora's policy to specifically disallow such packages in the interest of cohesion?
          Yes, but I guess they are treating is as deprecated. Good riddance anyway.

          Comment


          • #6
            It's not like they're disallowing sysv scripts, they're just saying if you don't have systemd support then you will need to add it or plead your case. They don't want to "need" to support packages with sysv scripts, but they don't mind people who want to support them doing so, in other words.

            Comment


            • #7
              Originally posted by emblemparade View Post
              Doesn't systemd offer basic System V compatibility? Is it Fedora's policy to specifically disallow such packages in the interest of cohesion?
              i would guess systemd-sysv is not connected to this. this probably goes for last few services that fedora ships trough it. if you check /etc/init.d there are still few services there and most probably they will replace them with unit files

              Comment


              • #8
                Good riddance!

                Comment


                • #9
                  Originally posted by emblemparade View Post
                  Doesn't systemd offer basic System V compatibility? Is it Fedora's policy to specifically disallow such packages in the interest of cohesion?
                  It is. However, its not a big fun when you have half of system using systemd units and another half comes with init scripts. One of EPIC FAILs of Upstart was the fact they were never managed to persuade software devs and package maintainers to actually use it and all associated goodies. Making it far less useful than it would be otherwise, basically making it a half-baked solution. This led to two-headed frankenstein instead of system. Actually, Ubuntu these days gone a bit further. Now it is a three-headed hydra where one haves both Systemd, some scattered leftovers of upstart (why?) and some sysv init leftovers as well. Whatever, systemd is a clear winner, both in terms of support in software and in terms of features, etc. So let introduce this hydra to occam's razor, too
                  Last edited by SystemCrasher; 01 November 2015, 09:18 AM.

                  Comment

                  Working...
                  X