The Linux Thread - The Autist's OS of Choice

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Why the fuck is there a sed update? What needs to be added to sed?

prollyanotherlurker said:
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.
Click to expand...
Just do it like Slackware and tar -zxvf - -C /
Fuck 'em if they don't know what they need.
 
acid_ra1n said:
Fedi gem
Click to expand...
Miller said:
Brodie got exposed for being a loli enjoyer.
It took them long enough to find that out I guess.
Click to expand...
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.
 
prollyanotherlurker said:
you get a prompt in pacman. Again it's a pretty arbitrary difference. And it's not just pacman that does it like that.
Click to expand...
No, you get a message to stdout, which can easily be ignorantly or inadvertently ignored. You know what a prompt looks like, no?
Code: 
Not ready reading drive A
Abort, Retry, Fail?
or
1777938816415.png
 
acid_ra1n said:
I think lunduke flew too close to the sun here as well lol
Click to expand...
I wish he would fly into the sun.

Take Brodie with him while he is at it.

⠠⠠⠅⠑⠋⠋⠁⠇⠎ ⠠⠠⠊⠎ ⠠⠠⠁ ⠠⠠⠋⠁⠛ said:
No, you get a message to stdout, which can easily be ignorantly or inadvertently ignored. You know what a prompt looks like, no?
Code: 
Not ready reading drive A
Abort, Retry, Fail?
or
View attachment 8958533
Click to expand...
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.
 
Last edited:
SchizoDaemon said:
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.
Click to expand...
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).
 
Last edited:
Paul Revere Pantry Raider said:
Why the fuck is there a sed update? What needs to be added to sed?
Click to expand...
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.
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.
 
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!"
 
⠠⠠⠅⠑⠋⠋⠁⠇⠎ ⠠⠠⠊⠎ ⠠⠠⠁ ⠠⠠⠋⠁⠛ said:
No, you get a message to stdout, which can easily be ignorantly or inadvertently ignored. You know what a prompt looks like, no?
Code: 
Not ready reading drive A
Abort, Retry, Fail?
or
View attachment 8958533
Click to expand...
Yes you don't have an ncurses menu pop up on pacman. Which is overall the norm for package managers for this kind of thing. Apt is the exception here. Most package manager just take a default action that you configure them to take, or do something and let you handle whatever you are going to do, most likely with a builtin too, or a tool included by the distro.

I've never had an issue where it wasn't clear exactly what it meant when I have pacman give the message that their is a pacsave or a pacnew in /etc. And even if you somehow miss it, you can check if there are any pacsave's/pacnew's in /etc every once in a while. The way pacman specifically handles them doesn't really get in the way of normal operations when you have one sitting there. It's not like it takes your manual configuration and does anything to it, it just creates the pacnew file there with the new contents of the /etc file from the update. It's pretty rare I have ever done anything with a pacnew outside of deleting it. The one or two cases where I didn't, I took one line from it, and added it into my actual file.

But like I've been saying, this isn't some obscure behavior pacman has, it's pretty much standard practice for a package manager. Anyone who has used any distro other than debian. Particularly ones that expect you to know how at least a little about managing your system (and even ones that might not). Pretty much do the same thing.

like for instance dnf.

1778002454592.png

Which is used on plenty of other "just works" distros. Where realistically you would be expected to know less than a user on void, arch/artix, gentoo, alpine etc etc.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom