Announcement

Collapse
No announcement yet.

Wayland's Weston Gets Systemd Notification Support

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

  • Wayland's Weston Gets Systemd Notification Support

    Phoronix: Wayland's Weston Gets Systemd Notification Support

    Wayland's Weston system compositor has been hooked up to systemd so it can be used for client notification support...

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

  • #2
    The BORG are here

    It's just a matter of time before wayland gets assimilated by systemd

    Comment


    • #3
      If this continues we might be better off taking our chances with upstart and mir...

      Comment


      • #4
        Originally posted by wargames View Post
        It's just a matter of time before wayland gets assimilated by systemd
        Well, Wayland is to Systemd what Mir is to Upstart.

        Comment


        • #5
          Originally posted by not.sure View Post
          If this continues we might be better off taking our chances with upstart and mir...
          I would rather go to the BSDs in that case.

          Comment


          • #6
            Originally posted by not.sure View Post
            If this continues we might be better off taking our chances with upstart and mir...
            What part of optional dependency didn't you understand? It's only a runtime check... not even compile-time.

            Comment


            • #7
              Wow, so much blinding hate.

              This isn't systemd lock-in, it's simply a patch to tell systemd when Weston can accept client connections. As Tom Gunderson mentions in the followup though the approach they're using shouldn't be necessary because systemd can queue up socket connections before the server is available - there's no need to notify.

              Comment


              • #8
                Originally posted by TheCycoONE View Post
                Wow, so much blinding hate.

                This isn't systemd lock-in, it's simply a patch to tell systemd when Weston can accept client connections. As Tom Gunderson mentions in the followup though the approach they're using shouldn't be necessary because systemd can queue up socket connections before the server is available - there's no need to notify.
                Agreed. Everyone hating on this article is nothing more than a troll. This is about OPTIONAL, runtime-checked support. No hard dependencies, no compile time flag, not even so much as a config edit.

                Comment


                • #9
                  Originally posted by Ericg View Post
                  Agreed. Everyone hating on this article is nothing more than a troll. This is about OPTIONAL, runtime-checked support. No hard dependencies, no compile time flag, not even so much as a config edit.
                  Its getting pretty ridiculous how any news related to systemd gets so many trolls like this.

                  Comment


                  • #10
                    Originally posted by bwat47 View Post
                    Its getting pretty ridiculous how any news related to systemd gets so many trolls like this.
                    that is because they don't use systemd and have never seen a linux system with SSD botting to kdm/gdm in 1 sec or save a ton of ram making your services activate ondemand so they only use resources when needed.

                    sometimes i think lennard goes out at night to bang trolls moms <-- that would explain the blind hate

                    Comment


                    • #11
                      Originally posted by TheCycoONE View Post
                      Wow, so much blinding hate.

                      This isn't systemd lock-in, it's simply a patch to tell systemd when Weston can accept client connections. As Tom Gunderson mentions in the followup though the approach they're using shouldn't be necessary because systemd can queue up socket connections before the server is available - there's no need to notify.
                      I also agree. Besides, I don't think systemd is that bad. Using it can be a little vague at times but it isn't bad, and 1 more feature for wayland makes it that much closer to being usable in everyday situations.

                      Comment


                      • #12
                        Originally posted by jrch2k8 View Post
                        that is because they don't use systemd and have never seen a linux system with SSD botting to kdm/gdm in 1 sec or save a ton of ram making your services activate ondemand so they only use resources when needed.
                        Actually I have seen that. But there is more to an init system than "OMG so fast!!!!!1111111"
                        We will see how that all works out when RHEL 7 comes out and a huge number of RHEL/CentOS admins are confronted with it, you know, on servers, not on "OMG so fast" desktop systems.

                        sometimes i think lennard goes out at night to bang trolls moms <-- that would explain the blind hate
                        Than he would be a necrophiliac. Do you have anything substantial to say or is insulting all you can do?

                        Comment


                        • #13
                          Originally posted by Vim_User View Post
                          Actually I have seen that. But there is more to an init system than "OMG so fast!!!!!1111111"
                          We will see how that all works out when RHEL 7 comes out and a huge number of RHEL/CentOS admins are confronted with it, you know, on servers, not on "OMG so fast" desktop systems.
                          Those admins have plenty times to try a Fedora 18+ Livemedia to get familiar with systemd.
                          Afterall, Fedora is the upstream of RHEL/CentOS.

                          Comment


                          • #14
                            How hard is it to figure out that Wayland is a standard? This isn't even about Wayland, it's about Weston, which is a REFERENCE IMPLEMENTATION of a Wayland compositor, no one is forcing any other Wayland compositor to implement any kind of systemd dependency or compliance or support or whatever. You're entirely free to make your own Wayland compositor and name it "systemdsucksmyballsWM" if you like.

                            Comment


                            • #15
                              Originally posted by finalzone View Post
                              Those admins have plenty times to try a Fedora 18+ Livemedia to get familiar with systemd.
                              Afterall, Fedora is the upstream of RHEL/CentOS.
                              And there is plenty of documentation about it. But that is not what I am talking about. With RHEL 7 we will see the first massive deployment of systemd in professional server environments, where stability and reliability is magnitudes more important than boot times, and we have yet to see how that works out.

                              Comment

                              Working...
                              X