Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
What about setting up a new environment correctly instead?
Says the man that just copied and pasted, then checked in 800mb of shitty angular dependencies just to get Jenkins to be able to build his inherited project.
It's ok, they don't pay me enough to support a family and don't give a shit about this project, and it's for internal use.
Thatβs so stupid.
downloads and runs entire Linux distro just to run a python script without managing dependencies
Jenkins
This is where I spat my tea: not because jenkins is super old but because I still have residual PTSD from using it.
My sympathies.
Apparently sometimes you have to remove symlinks to make programs load. I had a very weird bug that made a library fail to load even if the symlink was good. I wrote a bug report to bugs.debian.org and they told me to remove the symlink. That fixed it, wtf
Patient: Doctor, it hurts when I move my arm this way.
Doctor: Well, don't move your arm that way then.
Meanwhile as a guix+nix user i can just build it against that old library version because nothing can conflict with each other anyway
Yea but wheres the fun in that
I remember when games would't work with wine, complaining about some dll, I would get it from some random shady site and drop into the wine system dir. Some of the times, it worked, to even my own surprise
"DLL finder", holy shit I remember tools like that... God, now that I know how shared libraries work, that's kinda terrifying people just saw that error message and downloaded whatever the fuck they found whereever they found it...
Must be how some malware spread.
Look, man, I gotta play Sim Theme Park. If everything else blows up, thatβs a problem for later.
CKAN (mod manager for kerbal space program) created a multi month long battle for me because it started making copies of the original game for mod installs with symlinks to the original game files rather than just copying it outright, this made it impossible to boot certain mods because part of their first time set up was overriding files. Eventually I realized what the problem was and just manually copied the files in to the folder before loading up the mods for the first time.
WHICH IS INFURIATING! The whole reason I made new game installs was so that shit could be overwritten without breaking the base instal! WHY THEY HELL WOULD IT DEFAULT TO SYMLINKS FOR THAT?
Daily nixos behaviour
In my experience, this works about 25% of the time and is cause for extreme nervousness about what will happen if it tries to call a function that isn't actually present in the version it has been fooled into accepting.
It's never actually formatted my entire system even when it's gotten me a little further, perhaps to a different sort of crash, but that fear is always there.
Guys do not do this, it's gonna cause a mess further down the line.
"The problem with creating these links is that they aren't managed in any meaningful way. If that library is removed, the link becomes broken. If the library is upgraded, it may encounter an error because of the link that it doesn't expect to be there."
βThe problem with creating these links is that they arenβt managed in any meaningful way. If that library is removed, the link becomes broken. If the library is upgraded, it may encounter an error because of the link that it doesnβt expect to be there.β
If anyone is forwarding shit the way OP is, I'm pretty sure this is a "move the earth to hack this shit to work right now" action instead of "here are the foundations of my best practice based system"
It is most commonly used to get an older archived program to load a newer library without recompiling the older program, so none of those objections apply, or are serious, because a dangling symlink (when the os moves to a newer library version) just keeps the one program from loading, reproducing (in a way) the error the symlink was introduced to fix.
The user can typically fix the same exact problem in that case. Honestly, those objections read like that meme, "No, not that way!"
Reminds me of when I abused LD_LIBRARY_PATH and installed a Linux from scratch distro on a headless test server that no one was using. I got it all the way to x11 forwarding a full i3 environment without super user privileges.
Why do we even need dynamic linking if we have deduplicating file systems?
As a lay-person, reading these memes and comments, and understanding nothing, is probably the biggest factor that's made me decide that, while I hate windows, I'll never feel comfortable using Linux. I mean, seriously, how much of the time are you frustratingly troubleshooting stuff? I just want something like Windows that won't shove ads and ai bullshit at me and won't brick my laptop after updates π
Let's just say that Linux invites tinkering, and there are consequences. If you install a mainstream (fedora), reliable (fedora) distro, and just do normal stuff, it's unlikely you'll encounter more issues than Windows. Or even a tenth of the issues.
For me, the difference between Windows and Linux is that when I encounter a weird issue on Windows, I might decide to give up, while on Linux, I can always dig deeper if I have enough time
I have a pair of old-ish but expensive Sony bluetooth over-the-ear headphones. On Windows, their microphone doesn't work. I've searched the web and apparently, that's just it, nothing I can do.
Fedora without codecs? That's the reason I don't suggest it to normal users.
Oh no, they have to run sudo dnf group install multimedia once in the terminal!
And add RPM Fusion. Which could give errors when updating to a new major release.
Never happened to me, I think I must have updated 6-8 years of releases with zero issues, even moved the SSD to a new laptop with no problems
It happens if you update too early and the fusion repo isn't on par. But still stuff to troubleshoot for no reason, so no good for new users.
Linux Mint is still the distro I suggest which provides a check to enable codecs when installing, even if I'm a Fedora user.
Derivatives are too risky
Do you mean because it is based on Debian/Ubuntu?
I have been using Linux for 15 years and have never had to do this. As long as you choose a mature, stable distro (not arch or the newest fad) you will have a much easier time.
what's the most mature, stable distro there is? One wherein I can stream and download torrents?
To flip that on it's head, if you do have computer issues, would you rather get help from someone who laughs at these silly memes or a huge ai powered bureaucracy that prioritises upselling and closing tickets?
If it makes you feel any better, everytime I had to do this was because I was going out of my way to fix a linux game I compiled myself or some service I hacked together. I'm 99% sure you can have a hassle-free linux desktop experience if you follow the standard way your distro suggests of doing things. Have you tried testing the waters with a linux live usb stick yet?
Oh I haven't tried anything yet. I'm too scared I'll fuck it up π Anything that has me loading boot screen and entering commands has me thinking I'll just absent mindedly type "delete system/32" somehow
I use Linux Mint since last June and I rarely have to troubleshoot my PC and when I have to, it's obviously my fault for messing around.
Fedora, I think?
The most junk hack I ever did (that somehow worked) was replacing a Tensorflow 1.x library set with the Tensorflow 2.x library set and keeping the original 1.x symlink so that the software using it would think it's still the 1.x. .so file lol.
I presume the API had some deprecated fallback for poorly migrated software, which is why it worked without complaints.
Also bazel is by far the worst build system I have ever used.
COM solved all this stuff over 30 years ago. When you're making breaking changes to an interface, you create a new one while still keeping the old one around (at least for a while). Both interfaces are shipped with the same DLL. Software written for the old interface continues to work, while newer software can take advantage of the extra features in the new interface.
You can do something kinda similar in Linux with sonames, like libfoo.so.1, libfoo.so.2, etc. but there's still a bunch of use cases where you need to use LD_LIBRARY_PATH, and they're entirely separate libraries vs the COM approach where both interfaces are in a single library.
Modern software keeps poorly reinventing the same concept. Software like Home Assistant has breaking changes between releases because they don't have a consistent interface.