281–290 of 902 posts
But they already ship pkexec together with systemd anyway via polkit, why are they again reinventing a wheel they already reinvented? Unit files are a neat concept I don't want to miss again, but everything else done by Lennart seems to be an inceasingly stupid mistake born from hubris.
[flagged]
> The developer talks about the weaknesses of sudo, and how it has a large possible attack surface Poettering's hypocrisy is painful.
Wasn't the recent liblzma attack already exploiting the fact that systemd has its hands in pretty much everything? Wouldn't this expand further the attack surface of systemd and the systems that connect with it?
Earlier quoted context omitted.
This is the main reason why I'm still on Slackware. Pat is keeping the same thing for the last 20-30 years. Sure, he had to introduce some stuff, like NetworkManager or PulseAudio, to keep up with the latest software versions, but every major change is postponed as much as possible. Hell, even systemd is not there yet, and I'm pleased about that.
Same, I am also hiding on Slackware .
Piece by piece, Red Hat is taking over the Linux ecosystem.
Earlier quoted context omitted.
Instead of just hating based on assumptions it would be useful to actually familiarize with the thing you are critizising > But what makes me really upset is this completely unexplainable need to make everything part of one particular init system systemd is not init system, its and umbrella project for various core system components, which includes an init system. > There is absolutely no reason to tie your new sudo…
Half the people here tell me that systemd is great because it tries to create an integrated complete system, the other half tells me I can just pick and choose. Obviously one of these groups is lying.
Earlier quoted context omitted.
The issue is that it's not just ideological. "Do one thing and do it well" is important because if you want to port software to another platform, it's a lot easier to port a single dependency component over to make it work than it is to port over the entire framework. This is a serious problem and it makes it way harder to make things cross platform.
Systemd was written specifically for Linux, hard depends on a list of features provided by the Linux kernel and leverages them to do its work. Porting it to another kernel is a rewrite. Lack of portability is in this case a design tradeoff.
There is very little benefit for most userspace software to tie itself to systemd and by extension linux when otherwise it could be portable to any unix or unix like platform. Especially when an alternative, portable solution already exists and is well established.
Earlier quoted context omitted.
The issue is that it's not just ideological. "Do one thing and do it well" is important because if you want to port software to another platform, it's a lot easier to port a single dependency component over to make it work than it is to port over the entire framework. This is a serious problem and it makes it way harder to make things cross platform.
Systemd was written specifically for Linux, hard depends on a list of features provided by the Linux kernel and leverages them to do its work. Porting it to another kernel is a rewrite. Lack of portability is in this case a design tradeoff.
> One could say, "run0" is closer to behaviour of "ssh" than to "sudo", in many ways. This is an interesting offhand comment. You could implement a very similar tool by SSHing to localhost.
> ssh user@privileged-commands ./do-something