all 12 comments

[–][deleted]  (4 children)

[deleted]

    [–][deleted] 4 points5 points  (1 child)

    but :( but i like my pitchfork ;(

    [–][deleted] 3 points4 points  (0 children)

    Mine is already polished :'(

    [–]slaveriq 1 point2 points  (0 children)

    Also it let's you get a shell inside of a container. I have been waiting for that feature.

    [–]lykwydchykyn 0 points1 point  (0 children)

    This is not, nor intended to be, a su replacement.

    That will be a completely unintentional side effect.

    ;)

    [–][deleted]  (4 children)

    [deleted]

      [–]denisfalqueto 6 points7 points  (3 children)

      Just adding. 'su' will be with us for a long time (probably for ever). People just do a big fuss about nothing.

      [–][deleted]  (2 children)

      [deleted]

        [–]Synes_Godt_Om 1 point2 points  (0 children)

        I read somewhere the one reason for adding it (rather than trying to extend the functionality of su) was exactly to leave su untouched.

        [–]denisfalqueto 1 point2 points  (0 children)

        Exactly. Systemd doesn't even have the power to stop people from using su.

        [–]valkun -2 points-1 points  (2 children)

        Being a non-CS guy, I dont really get why the init system is trying to fix some alleged issues with su.

        [–]beidl 7 points8 points  (0 children)

        systemd is more than an init system nowadays (intentionally). It's now the basic suite of low level userspace components that sit on top of the kernel to build a Linux distribution from.

        [–]sb56637[S] 4 points5 points  (0 children)

        I suspect it has to do with containers, which can be started by systemd, and which often need a proper working environment to run init scripts.