From: lew.pitcher@digitalfreehold.ca   
      
   On Sat, 21 Aug 2021 18:03:21 +0000, Lew Pitcher wrote:   
      
   > On Sat, 21 Aug 2021 19:46:56 +0200, Aragorn wrote:   
   >   
   >> On 21.08.2021 at 15:57, Lew Pitcher scribbled:   
   >>   
   >>> On Sat, 21 Aug 2021 15:34:15 +0000, root wrote:   
   >>>   
   >>> > I don't want to see the intrusive elogind display   
   >>> > that comes after the login prompt but before   
   >>> > I can log in. I tried chmoding -x the entry   
   >>> > in /etc/rc.d but that didn't kill the daemon.   
   >>> >   
   >>> > I know this is needed by Gnome, which I thought   
   >>>   
   >>> To quote the Gentoo wiki...   
   >>>   "elogind is the systemd project's logind,   
   >>>   extracted to a standalone package. It's   
   >>>   designed for users who prefer a non-systemd   
   >>>   init system, but still want to use popular   
   >>>   software such as KDE/Wayland or GNOME that   
   >>>   otherwise hard-depends on systemd."   
   >>>   
   >>> I think the key phrase here is "to use popular   
   >>>   software such as KDE/Wayland ... that   
   >>>   otherwise hard-depends on systemd."   
   >>>   
   >>> Apparently, if you want KDE, you must have   
   >>> elogind.   
   >>   
   >> No, only if you want KDE Plasma running on top of Wayland instead of   
   >> on top of X.org.   
   >   
   > OK. Good to know.   
   >   
   > So, I wonder why Pat included elogind.   
      
   To answer my own question...   
      
   Slackware 15 will include an option to run Wayland. It will also include   
   KDE. KDE/Wayland requires elogind, and elogind can substitute for the   
   existing ConsoleKit2.   
      
   So, PV moved from ConsoleKit2 to elogind to facilitate KDE under Wayland   
   on Slackware 15.   
      
   --   
   Lew Pitcher   
   "In Skills, We Trust"   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)