Announcement

Collapse
No announcement yet.

An Update On The SystemD System & Session Manager

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

  • An Update On The SystemD System & Session Manager

    Phoronix: An Update On The SystemD System & Session Manager

    There's an update on systemd by Lennart Poettering, the Berlin developer that created this project to serve as a new system and session manager for Linux. The systemd manager is compatible with existing SysV and LSB init scripts while it leverages D-Bus activation, heavily supports parallelization, and has many other features that makes it of interest to distribution vendors and end-users. Red Hat has already switched from SysVinit to systemd with Fedora 14 and judging from Lennart's blog post today it will likely gain more acceptance based upon the recent improvements...

    http://www.phoronix.com/vr.php?view=ODUzOA

  • #2
    Sounds like something to try and benchmark

    Comment


    • #3
      You forgot to commend the last part of the web page http://www.freedesktop.org/wiki/Software/systemd

      Packages:

      Fedora (Where we are: http://lists.fedoraproject.org/piper...ly/138855.html)

      OpenSUSE (Instructions: http://en.opensuse.org/SDB:Systemd)

      Debian

      Gentoo

      ArchLinux

      Nope, no packages for Ubuntu. Go figure.
      bold added by me.

      Comment


      • #4
        Fedora not using sysvinit

        Originally posted by phoronix View Post
        Red Hat has already switched
        I think it would be more accurate to say that they are in the process of switcing, since Fedora 14 isn't due to be released until November.

        from SysVinit to systemd with Fedora 14
        Fedora hasn't been using sysvinit for more than two years now. Starting with Fedora 9, Fedora has been using upstart.

        Comment


        • #5
          Originally posted by wpoely86 View Post
          Sounds like something to try and benchmark
          See this comment by Lennart on LWN.

          Comment


          • #6
            Originally posted by KDesk View Post
            You forgot to commend the last part of the web page http://www.freedesktop.org/wiki/Software/systemd

            ...

            bold added by me.
            Surprised? SystemD is something new, under development primarily by a Fedora person, and not yet in any formally released distro. It may turn out to be the future, but why on earth would Ubuntu be supporting it already?

            Comment


            • #7
              Originally posted by KDesk View Post
              You forgot to commend the last part of the web page http://www.freedesktop.org/wiki/Software/systemd
              Nope, no packages for Ubuntu. Go figure.
              Now that's just silly Ubuntu/Canonical bashing, and IMO a little unprofessional to put that on the freedesktop Wiki.

              Comment


              • #8
                Originally posted by monraaf View Post
                Now that's just silly Ubuntu/Canonical bashing, and IMO a little unprofessional to put that on the freedesktop Wiki.
                Maybe Ubuntu/Canonical can put in a retort in their next upstream commit. Oh wait a minute.....

                Comment


                • #9
                  Originally posted by Delgarde View Post
                  Surprised? SystemD is something new, under development primarily by a Fedora person, and not yet in any formally released distro. It may turn out to be the future, but why on earth would Ubuntu be supporting it already?
                  Well, xorg-edgers does exist, doesn't it? Ubuntu often packages stuff that's still in development. Then again, upstart is by Canonical and they Ubuntu guys might not be all too happy at a replacement coming in. I'd expect this to be the basis for the rather harsh comment. Suspicion that Ubuntu packagers are holding a grudge.

                  Comment


                  • #10
                    Originally posted by nanonyme View Post
                    Well, xorg-edgers does exist, doesn't it? Ubuntu often packages stuff that's still in development. Then again, upstart is by Canonical and they Ubuntu guys might not be all too happy at a replacement coming in. I'd expect this to be the basis for the rather harsh comment. Suspicion that Ubuntu packagers are holding a grudge.
                    That, and replacing your 'init' system isn't a trivial exercise. Replacing the X server with a bleeding-edge version is no big deal - it might not work, but it's easy to do, and easy to revert. The same can't be said for ripping out upstart or sysvinit and dropping in systemd instead.

                    Besides, this kind of dispute is silly. Lennart and co have written a new init daemon, which Fedora and SuSe are adopting. That's nice, but why should Ubuntu immediately ditch the system they built, and move to the shiny new one? Remember, systemd is *very* new, less than a year old, and there's really no good reason for Ubuntu to adopt it just now.

                    Comment


                    • #11
                      Originally posted by Delgarde View Post
                      Besides, this kind of dispute is silly. Lennart and co have written a new init daemon, which Fedora and SuSe are adopting. That's nice, but why should Ubuntu immediately ditch the system they built, and move to the shiny new one? Remember, systemd is *very* new, less than a year old, and there's really no good reason for Ubuntu to adopt it just now.
                      Did you notice even Debian had packages for it? Why then not Ubuntu? Is there any other possible reason than that Ubuntu packagers don't want Ubuntu users to try it out?

                      Comment


                      • #12
                        Lost chance to remove distro-specific differences

                        A new init system is a great opportunity for distros to eliminate the minor (yet damaging) differences, such that a service written for one distro is 100% compatible in another distro. A single code base also has the advantage of heavy testing and extermination of bugs.

                        By including special code for non-standard stuff like "SUSE extensions", systemd is just putting a bandaid on the problem instead of fixing it. And that's a shame.

                        Comment


                        • #13
                          This is a hobby project of Lennart and it's not tied to Red Hat. Lennart has said to be happy to cooperate with any large distro, including Ubuntu, so... Draw your own conclusions here...

                          Comment

                          Working...
                          X