The Linux Thread - The Autist's OS of Choice

[Paul Revere Pantry Raider]

Why the fuck is there a sed update? What needs to be added to sed?

If you want to know how an actually shit package manager handles it. Look at what happens when you try making any change to a flatpak runtime.

Just do it like Slackware and tar -zxvf - -C /
Fuck 'em if they don't know what they need.

 

[blackshirt]

Why the fuck is there a sed update? What needs to be added to sed?

Security fix probably

 

[Paul Revere Pantry Raider]

Security fix probably

Much like the 2017 crypto issue AI found- well, that took awhile.

 

[SchizoDaemon]

Fedi gem

Brodie got exposed for being a loli enjoyer.
It took them long enough to find that out I guess.

Quite a number of the Linux YouTubers are insufferable in one way or another, and I don't think they really know much beyond being able to apt-get install <thing>and rice their ~/.bashrc. I am not surprised that quite a few of them are gooners/degens etc.

 

[acid_ra1n]

Brodie got exposed for being a loli enjoyer.
It took them long enough to find that out I guess.

I think lunduke flew too close to the sun here as well lol

 

[⠠⠠⠅⠑⠋⠋⠁⠇⠎ ⠠⠠⠊⠎ ⠠⠠⠁ ⠠⠠⠋⠁⠛]

you get a prompt in pacman. Again it's a pretty arbitrary difference. And it's not just pacman that does it like that.

No, you get a message to stdout, which can easily be ignorantly or inadvertently ignored. You know what a prompt looks like, no?

Not ready reading drive A
Abort, Retry, Fail?

or

 

[SchizoDaemon]

I think lunduke flew too close to the sun here as well lol

I wish he would fly into the sun.

Take Brodie with him while he is at it.

No, you get a message to stdout, which can easily be ignorantly or inadvertently ignored. You know what a prompt looks like, no?

Not ready reading drive A
Abort, Retry, Fail?

or
View attachment 8958533

Many config files are merged now using the partial config files that go in the ".d" directories. So while it isn't wrong to edit the main file, it is often seen as causing yourself problems. You shouldn't use that screen if you use the partial config files (I think). It has been that way since Debian 12 IIRC.

 

[⠠⠠⠅⠑⠋⠋⠁⠇⠎ ⠠⠠⠊⠎ ⠠⠠⠁ ⠠⠠⠋⠁⠛]

Many config files are merged now using the partial config files that go in the ".d" directories. So while it isn't wrong to edit the main file, it is often seen as causing yourself problems. You shouldn't use that screen if you use the partial config files (I think). It has been that way since Debian 12 IIRC.

I 100% agree. I don't think I've seen more than one of those debconf prompts in several years, and that was because I was customizing the main nginx.conf file when I shouldn't have.

My point is not to say- it's good to customize those primary files under /etc and that you should do it and embrace getting a nonobvious warning method (Arch) or a prompt that YOU DONE FUCKED UP (Debian) and then manually merge changes. My point is that a well set up distribution explicitly works to make sure you don't need to- if upstream thinks differently, they can suck a dick- and then makes it very very clear if you do fuck up to you in a way that you cannot avoid that you did make changes where you really shouldn't have- which in these times, is typically because you were following instructions from an LLM (or the Arch wiki).

 

[Battlefield42]

Fedi gem

Brodie got exposed for being a loli enjoyer.
It took them long enough to find that out I guess.

i listened to brodies podcast yesterday. am i pedonigger now?

 

[Dante Alighieri]

i listened to brodies podcast yesterday. am i pedonigger now?

yes, please get into the woodchipper

 

[Billy Herrington "Aniki"]

I changed my mind, I use KDE now.

 

[⠠⠠⠅⠑⠋⠋⠁⠇⠎ ⠠⠠⠊⠎ ⠠⠠⠁ ⠠⠠⠋⠁⠛]

Why the fuck is there a sed update? What needs to be added to sed?

You must not use sed for searching and replacing text in files where lines are larger than 2GB in length. That was crashing. Nasty bug, that.

https://lists.gnu.org/archive/html/sed-devel/2026-04/msg00027.html

I mean, there are some 'security bugs' fixed, in that the (non-POSIX) --follow-symlinks option (used with the in place editing flag) had a race condition where if you ran sed against a symlink and changed the symlink to point somewhere else it would read data from the initial target of the symlink and write it to the new target.

I am really, really not sure how this actually would cause any vulnerability. It seems like there would need to be a script that could be arbitrarily run with more privileges than a user should have, that takes arbitrary parameters for the data to be replaced, and operates on files that a regular user has access to repoint at files that they shouldn't be able to edit.

 

[Dread First]

View attachment 8960104
I changed my mind, I use KDE now.

I'm definitely guilty of daily driving Fedora, but I maintain my stance that the Xorg spins are actually pretty good. Fedora Cinnamon far and away mogs the shit out of Fedora Plasma and Fedora Workstation.

 

[GoysGoneWild]

I actually appreciate Lunduke on this for once. loliniggers have been getting away with it for far too long and normalizing their bullshit.

Call a lolinigger a loser, a troon, a leftie white hating freak, it all runs off him like water off a raincoat. Call him a pedo and see how he recoils, how he shrinks away, how hurt he is, "I've been found out!"

 

[Paul Revere Pantry Raider]

You must not use sed for searching and replacing text in files where lines are larger than 2GB in length.

Caught me. I draw the line on my lines at about 1.78 GB, otherwise I just can't get vim to fit it all on the screen, even using ProFont.