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...

    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
    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.
                All opinions are my own not those of my employer if you know who they are.

                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

                    Working...
                    X