Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Run0, a systemd based alternative to sudo, announced

mastodon.social

Post reply on HN
Print view View original

321–330 of 902 posts

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

#321

Post by cyberpunk »

iforgotpassword wrote: post #264
cyberpunk wrote: post #242

Earlier quoted context omitted.

I’ve been running Ubuntu boxes in prod since 12.x — there is no “improved” way to put an ip address on an interface besides writing something to a file in /etc, but every update this file changes, or it’s format does. It’s bullshit and I wish it would end. Alas, keeps the consultant bucks flooding in when we have to rewrite a load of cfgmgt to go to 24.04 I guess..

I just switch every system to systemd-networkd immediately. The same .ini sytax as for service files, and dependencies are easy to handle, e.g. on one system I have two physical Interfaces eth0 and eth1, I want two vlans on eth0, and then bridge one of those vlans with eth1 and then run a DHCP client on that bridge but at the same time assign an additional IP address. This is dead simple to describe with one .ini fil…

Eh, I could. But I'm quite sure that the method of switching to systemd-networkd also requires the same if not much more maintenance as simply changing the ifconfig template every few years...

I really don't care about interface configurations that much. It's an annoyance, but one that's quite easy to fix. I think introducing yet another network configuration here isn't the answer, but my linux fleet just run k8s anyway and network config on the linux level is quite simple before we get into cillium/istio/etc :}

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

#322

Post by airocker »

rpgwaiter wrote: post #318
airocker wrote: post #310

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…

NixOS at it again :)

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

#323

Post by mzs »

throw0101b wrote: post #205

First comment at the LWN: > […] I think calling the flags "setuid" (as lwn appears to prefer?) just blurs things, since that's the name of a syscall (setuid()), which does something related, but is not actually involved in the concept that the inode SUID flag is about. > Hence, I am a bit confused what that comment here is supposed to achieve? It just creates confusion? > Lennart * https://lwn.net/Articles/971747/ Re…

the right person to replace sudo, not: https://github.com/systemd/systemd/issues/6237

PS: https://pwnies.com/systemd-bugs/

edit, this one went on for more than a year: https://github.com/systemd/systemd/issues/6632

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

#324

Post by tapoxi »

cogman10 wrote: post #319
tapoxi wrote: post #313

Earlier quoted context omitted.

It's just journalctl -u apache -f, assuming your distribution calls the unit file "apache", and the last few messages of the logfile appear with systemctl status apache And you don't need to worry about "is this service rotating logs appropriately?"

The important thing for me at least isn't he `-u apache` but rather knowing that `apache` exists as one of the installed services on this box. In the old ways, that was apparent because of the presence of the log file. Granted, this isn't the problem it used to be for us, however, it would come up because we'd have our services named things like `foo-ws` and knowing that `foo-ws` existed on a given box might be trick…

I mean "systemctl status" shows all services and their hierarchy, there's also "systemctl list-unit-files" if you want to see things that aren't part of the current target (runlevel).

It's much easier in the systemd world to see the state of the system, the state of the service, and the logs of a service because it enforces this consistency.

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

#325

Post by mort96 »

mid-kid wrote: post #84
mort96 wrote: post #19

Earlier quoted context omitted.

Is it? Does systemd's sudo replacement also have a lot of complex code running as root in a suid binary? Because that's what he's complaining about

systemd has a lot of complex code running as root (that can be reached without privileges more often than not) and has had its fair share of CVEs. The hypocrisy is in calling out a different project for being an overengineered tool running with too high privileges.

It's not just about running as root though, but as being in a SUID binary.

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

#327

Post by delta_p_delta_x »

slackfan wrote: post #262
paulddraper wrote: post #250

Earlier quoted context omitted.

100% Systemd unit files make Linux feel like a rational OS.

Only if your marker for a rational OS is NT.

Not the parent commenter. Windows has a lot of rubbish user-level interaction which belie how good an OS NT really is. Anyone who blindly disses it because 'Windoze' and 'M$ bad' is not really worthy of any attention whatsoever.

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

#328

Post by _flux »

stoperaticless wrote: post #298
saghm wrote: post #278

Earlier quoted context omitted.

> journalctl supports -f, which by your own account you were already using for tail, so I'm not clear what's worse there Yeah, this is a bit of an odd complaint. If I were this bothered by having to type those, I'd just make an alias to "journalctl --follow --nopager"` and would have forgotten about it years ago.

Never tried it, but if the complainer wrote: tail -f *.logs Which involves glob’ing. I assume it allows to monitor several services at the same time. Can systemd do that?

It's the basic function what journalctl -f does by default: follow the global log all jobs write into. -u etc are for filtering that.

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

#329

Post by gh02t »

zamadatix wrote: post #308
gh02t wrote: post #303

Earlier quoted context omitted.

It was a bit unclear to me from the thread, is there a persistent configuration option for this? I like the idea of tinting the terminal, but I also want to be able to turn it off with a global config option rather than having to type out a --background flag every invocation.

Aliasing the command as the command + your default arguments is the easiest general solution to this kind of problem. I'm not sure if there is a "systemd way" to permanently set it though.

True, I was thinking a simple environment variable or systemd configurable would be fine but I guess an alias is a good idea.

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

#330

Post by mintplant »

tapoxi wrote: post #315
stoperaticless wrote: post #298

Earlier quoted context omitted.

Never tried it, but if the complainer wrote: tail -f *.logs Which involves glob’ing. I assume it allows to monitor several services at the same time. Can systemd do that?

Yes, journalctl -u postgres -u redis -f etc

Or just `journalctl -f` to follow all logs.
Post reply on HN