Announcement

Collapse
No announcement yet.

Systemd 239 Is Being Prepped For Release With Many Changes

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

  • #11
    Originally posted by caligula View Post

    Funny. People complain how systemd is worse than <insert your favorite alternative here>. However when they fix systemd bugs and improve it in other ways, the people will complain even more and more.
    Once you hate something badly enough, everything it does is offensive. Not sure if this link will work.

    https://i.pinimg.com/236x/bd/ae/a6/b...e-journals.jpg

    (I'm picking on the people with an irrational dislike of systemd, not systemd itself.)

    Comment


    • #12
      Originally posted by dlocklear01 View Post
      If systemd is already running before we log in, why not just get rid of a log-in manager and make systemd require a password
      dealing with passwords in an init system is agains security principles and against the Unix philosophy of keeping each daemon's scope focused on a specific topic.
      That functionality is implemented in dedicated daemons, not in the main init system.

      If you need a simpler password dialog than logind+graphical login manager, the systemd project offers a simpler daemon called systemd-ask-password which works fine without a login manager (using plymouth), or without a graphical user interface at all (console or serial console). https://www.freedesktop.org/software...-password.html

      Comment


      • #13
        Systemd sucked for a little while when it first came in, but now that it's stabilised meh. It doesn't really change things one way or another. The only concern I have about it is if there's some gaping security hole in it.

        Comment


        • #14
          Originally posted by DMJC View Post
          The only concern I have about it is if there's some gaping security hole in it.
          That's a tradeoff I can accept. With shell scripts you're almost always sure there is some obscure way you didn't think of where someone could abuse your script.

          Comment


          • #15
            Originally posted by dlocklear01 View Post
            If systemd is already running before we log in, why not just get rid of a log-in manager and make systemd require a password
            Don't give them ideas

            Comment


            • #16
              Originally posted by dlocklear01 View Post
              If systemd is already running before we log in, why not just get rid of a log-in manager and make systemd require a password
              There already is logind (part of the systemd suite), which manages seats and sessions, and PAM, which provides an authentication API. The actual login managers nowadays do little more than display a message asking users to enter their login name and password. So this is arguably one of the rare cases where we don't need more systemd.

              Comment


              • #17
                Why complain about breaking changes? I don't like then either but the systemd guys have starte that they do not have a high priority for maintaining backwards compatibility unless there are very good reasons to do so. systemd is a moving target as distros should pick one 'snapshot' and deal with it. Ideal? Hell no, but at least the changes are documented and systemd actually works quite well.

                http://www.dirtcellar.net

                Comment


                • #18
                  Originally posted by jacob View Post
                  There already is logind (part of the systemd suite), which manages seats and sessions, and PAM, which provides an authentication API. The actual login managers nowadays do little more than display a message asking users to enter their login name and password. So this is arguably one of the rare cases where we don't need more systemd.
                  they still made systemd-ask-password for cases where you want to go lighter than that

                  Originally posted by Templar82 View Post
                  Don't give them ideas
                  too late, systemd-ask-password exists already

                  Comment


                  • #19
                    Originally posted by waxhead View Post
                    systemd is a moving target as distros should pick one 'snapshot' and deal with it. Ideal? Hell no,
                    Depends from the viewpoint. keeping a strict backward compatibility means you eventually end up with baroque contraptions that are a PITA to properly maintain and keep secure.

                    They aren't routinely breaking compatibility on major things though, so that's not a real issue for most downstream projects.

                    Comment


                    • #20
                      Originally posted by caligula View Post

                      Funny. People complain how systemd is worse than <insert your favorite alternative here>. However when they fix systemd bugs and improve it in other ways, the people will complain even more and more.
                      Just to continue my acting...
                      The only permanent fix would be systemds death.

                      Comment

                      Working...
                      X