Page 1 of 4 123 ... LastLast
Results 1 to 10 of 36

Thread: Wayland's Weston Gets Systemd Notification Support

  1. #1
    Join Date
    Jan 2007
    Posts
    14,344

    Default 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. #2
    Join Date
    Sep 2012
    Posts
    279

    Default The BORG are here

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

  3. #3
    Join Date
    Oct 2009
    Location
    .ca
    Posts
    398

    Default

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

  4. #4
    Join Date
    Nov 2012
    Location
    France
    Posts
    538

    Default

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

  5. #5
    Join Date
    Jan 2013
    Posts
    1,116

    Default

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

  6. #6
    Join Date
    Sep 2007
    Posts
    293

    Default

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

  7. #7
    Join Date
    May 2010
    Posts
    121

    Default

    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.

  8. #8
    Join Date
    Aug 2012
    Location
    Pennsylvania, United States
    Posts
    1,860

    Default

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

  9. #9
    Join Date
    May 2010
    Posts
    684

    Default

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

  10. #10
    Join Date
    Jun 2009
    Posts
    1,095

    Default

    Quote 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

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •