←back to thread

Run0, a systemd based alternative to sudo, announced

(mastodon.social)
466 points CoolCold | 5 comments | 29 Apr 24 23:59 UTC | HN request time: 0.001s | source
Show context
fn-mote ◴[30 Apr 24 16:01 UTC] No.40212557[source]▶
Overall, this seems great.

However...

> [...] by default it will tint your terminal background in a reddish tone while you are operating with elevated privileges

?!! ouch ... seems orthogonal to the actual important parts.

Disclaimer: I didn't try it.

replies(4): >>40212686 #>>40215695 #>>40219040 #>>40225604 #
NekkoDroid ◴[30 Apr 24 16:15 UTC] No.40212686[source]▶
I tried it a bit ago (when it was still called uid0, pre-release), I also wasn't a fan of the tinting.

I like the intent behind it, but some terminals already tint the header color when running sudo, I haven't tested if its done specifically for sudo or if its in a more generic way that could handle this as well.

replies(2): >>40212858 #>>40213006 #
Karellen ◴[30 Apr 24 16:30 UTC] No.40212858[source]▶
> I also wasn't a fan of the tinting.

From the linked mastodon thread:

> For example, by default it will tint your terminal background in a reddish tone while you are operating with elevated privileges. That is supposed to act as a friendly reminder that you haven't given up the privileges yet, and marks the output of all commands that ran with privileges appropriately. (If you don't like this, you can easily turn it off via the --background= switch).

(emphasis mine)

replies(3): >>40215782 #>>40215796 #>>40217102 #
1. gh02t ◴[30 Apr 24 20:16 UTC] No.40215782[source]▶
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.
replies(1): >>40215811 #
2. zamadatix ◴[30 Apr 24 20:20 UTC] No.40215811[source]▶
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.
replies(2): >>40216003 #>>40217458 #
3. gh02t ◴[30 Apr 24 20:36 UTC] No.40216003[source]▶
True, I was thinking a simple environment variable or systemd configurable would be fine but I guess an alias is a good idea.
4. tolciho ◴[30 Apr 24 22:54 UTC] No.40217458[source]▶
I accidentally compile color support out of st, or set xterm*colorMode:false to avoid seeing the backside of a unicorn randomly rubbed all over the terminal, on account of git and other wares being bad at their inability to not spew color codes. A sensible default would be to set no colors, in the event that the colors are unreadable (due to colorblindness, etc) or distracting, but that ship sailed. Most of my vim config on RedHat linux was disabling wacky vendorisms, and back when I used linux I did have a "special terminal" for some NVIDIA installer that mandated colors to be usable. Maybe the terminal title was set to Fisher-Price, maybe not.
replies(1): >>40222748 #
5. shrimp_emoji ◴[01 May 24 13:16 UTC] No.40222748{3}[source]▶
Dang. I wish I had the autism to bristle at colors. Think about all the lost hours agonizing over themes! Not feeling the agonizing tension between the fact that cool-retro-term made your terminal into an awesome monochrome CRT but that it's monochrome green so your syntax highlighting is all messed up!

> back when I used linux

What do you use now? :0 BSD? Plan 9???