Live data from Hacker News

Run0, a systemd based alternative to sudo, announced

mastodon.social

351–360 of 902 posts

Re: Run0, a systemd based alternative to sudo, announced

#351

Earlier quoted context omitted.

The follow argument is identical to tail `-f`. `sudo journalctl -f -u `

And what would be the equivalent to, "Oh, I don´t know the name of the log for this process I can see in 'ps aux', let me cd into /var/log and see what filenames I can find ... or grep everything until I can find a couple of words that make some sense so I can keep digging further"? The lack of explorability in journalctl, the "need" to keep everything locked behind their own flavor of tools and magic file types, is…

systemctl status will show you the unit and helpfully the last few lines of log from it. Journalctl -u will then show you the full logs

Re: Run0, a systemd based alternative to sudo, announced

#352
post #226
post #121

I wonder what other existing programs Will Systemd attempt to replace in the future. My bet is /bin/sh, maybe they went further to replace the entire POSIX utilities.

Guix will reimplement POSIX utils and extras with tools written in Gule.

Please say this is a joke

Re: Run0, a systemd based alternative to sudo, announced

#353

I have seldom come across unix multiuser environments getting used anymore for servers. Its generally just one user on one physical machine now a days. I understand run0's promise is still useful but i would really like to see the whole unix permission system simplified for just one user who has sudo access.

NixOS may be helping multiuser make a comeback, at least it is for me and my home servers. I no longer have to containerize my apps, i can have one baremetal server with a dozen+ services, all with their own users and permissions, and i don't have to actually think about any of the separation. Plus there’s network shares. Multiple people in my home with linux PCs, each with their own slice of the NFS pie based on use…

DietPi does exactly the same using Debian

Re: Run0, a systemd based alternative to sudo, announced

#354
post #4

I'm really starting to hate the sub-community in Linux that tries to constantly change it. I don't want to learn a new network config alternative with every update (Ubuntu changed its net config tool again with 24.04). I don't want an immutable os. I don't want to learn to write new config files. I just want to do what I've been doing but with new packages. If there's a problem with something, just fix it. Don't thro…

>I don't want an immutable os. (...)

But I do. So I use one, and contribute to a project that tries to create one. Am I a part of some sub-community that wants constant change? Or do I just have an unusual use-case and want to support it?

The beauty of OS is that anyone can decide which tool to use, contribute to it, and even fork it.

Re: Run0, a systemd based alternative to sudo, announced

#355
post #307

Just a reminder that there are plenty of systemd-less distros available. Also a reminder that those distros would have been safe from the nearly-solar-winds-level backdooring of Linux distros from XZ utils.

Can you even hear what you are saying? Don't you find it ridiculous to blame the XZ backdoor on systemd, instead of the actual hacker? Even if systemd did not exist, the hacker would have just picked something else to infiltrate.

Of course, the actual hacker was to blame, but systemd was implicated. The fact that the attacker was willing to settle for compromising just Debian and Red Hat systems indicated that they perceived the path from xz to libsystemd was the easiest way to effect the backdoor and that doing it any other way would have been too much work for marginally little gain (Red Hat and Debian systems being so common).

Re: Run0, a systemd based alternative to sudo, announced

#357

Why do they have to do this? This is really, really stupid. My issue isn't even that someone tries to replace sudo. That may or may not be a completely fine thing to do, depending on the state of sudo and what improvements can be made. But what makes me really upset is this completely unexplainable need to make everything part of one particular init system. There is absolutely no reason to tie your new sudo replaceme…

>This is a completely insane way to develop software, instead of creating a new piece of software in a separate project I appreciate and respect the KISS sentiment of doing one thing and doing it well, but oftentimes I also think open source programs' lack of integration with each other at a fundamental level is also one of its biggest downsides. Being a Windows wizard unlike most folks around these parts, seeing and…

Linux is "just" an OS kernel. Integrations between user space programs have to be done by other people (like the systemd developers).

Re: Run0, a systemd based alternative to sudo, announced

#358
post #336

I have seldom come across unix multiuser environments getting used anymore for servers. Its generally just one user on one physical machine now a days. I understand run0's promise is still useful but i would really like to see the whole unix permission system simplified for just one user who has sudo access.

Visit the research computing environment sometime, for instance. The libzma SSH compromise was considered very worrying, after all.

That didn't need multi-users.

Re: Run0, a systemd based alternative to sudo, announced

#359

I have seldom come across unix multiuser environments getting used anymore for servers. Its generally just one user on one physical machine now a days. I understand run0's promise is still useful but i would really like to see the whole unix permission system simplified for just one user who has sudo access.

I've never understood the need for sudo(1) on single-user, physical machines: I keep a root shell (su(1)) around for admin tasks, and it's always been sufficient.

Its just maybe easier way to not have to go to the root shell.

Re: Run0, a systemd based alternative to sudo, announced

#360
post #45

systemd has been a net positive for the linux ecosystem. remember when you had to write bash scripts to start, stop, restart services and handle any other signals you want to send it? nowadays it's a unit file (basically just an ini file) away with relatively straightforward API. and you can actually declare startup dependencies and other useful relationships past just "prepend a number signifying when it should run…

I don't resent systemd for existing, but I don't want to be forced to accept Lennart's shitty design decisions and it's clear he wants me to be since he successfully agitated for other critical components to hard depend on it. I want the option of opting out, which Lennart would deny me if he could.

At the end of the day, I just run Void (or MX Linux if I want something more Debian-flavored) and get on with my life.

Post reply on HN