“Just follow the build instructions on GitHub”
1000 error messages ensue.
Here is a basic way to configure the service:
…
But this method has significant drawbacks and probably won’t work for most use cases, so do what works for you.
No other info whatsoever.
And then you go hunting for other people’s config files.
And those configs are clearly the result of someone else stitching together three different examples from different versions, with some settings that are silently ignored in the latest version or only exist when compiled with special flags.
But hey, it works for them, so 🤷… they have no idea how BTW, but it does work…
This is some unnecessary red circle shit right here.
Clearly added for emphasis, crucial instructions, we might mistake for other instructions in the picture.
But look how pretty it is 😊.
It’s hard enough to express this in a first language
What is a first language?
Oh bro, it’s the Art of War.
OpenSUSE microOS guys be like
- dont install any RPMs
- we wont help you adding RPM repos
- you need to install RPMs for drivers and stuff
😂
POCKET GUIDE TO TIGHTENING TECHNIQUE https://www.atlascopco.com/content/dam/atlas-copco/industrial-technique/general/documents/pocketguides/9833864801_L.pdf
I did not think there was that much to tightening. I read the whole damn thing.
Thanks for the red circle, I was really lost there for a moment
As someone who works in manufacturing this makes prefect sense and wish more instructions were this clear
How 🤨… tighten, but don’t…
It means “put all of the screws in the holes in order to start guiding the surfaces that you’re screwing together into the correct position, but don’t firmly tighten down all the screw until you have put all of them in so that you can ensure proper alignment of everything before you lock it in.”
Like put them in a few threads but don’t tighten then yet until you complete the next step
Tighten but don’t overtighten them, probably.
Tighten them but tighten them not too much but make sure not to tighten them too less, I guess
To screw or not to screw.
A little bit of both 🤷…
“Just gotta enable the OEIS menu in the .sysbin folder and it’ll make that program CHIM, that should solve your problem”
What it looks like when I ask “how do I put Cura on the taskbar”
“The real problem is that you’re using Cura and not Orca”
I’m concerned if CHIM is what I think it is, I don’t think I want the computer doing that.
You don’t want your computer to gain incredible, godlike powers?
I don’t know why such answers get so many upvotes.
The real answer is: Right-click -> Pin to Taskbar. (In sane desktop environments like KDE. If you choose to install Fancy DE Alpha 0.0.2, you know what you got into!)
Yeah we are in a meme community, still I like my memes based on reality, makes them way funnier.
(Also having a standard place for documentation for everything is a blessing!)
Sure but it’s not a rarity that forum answers expect you to be very familiar with linux file structures and terminal commands. If you’re a beginner who runs into an issue (as beginners do), you oftentimes need to find a tutorial and then tutorials that explain the tutorial. It gets even worse if you’re not on a debian/ubuntu based distro (although, to be fair, if you’re a newbie, that’s sorta asking for trouble).
Or you just use Arch and have one place for all the apps (AUR) and one place for all the manuals (ArchWiki)
And when using endeavourOS you get an easy install on top it, and as a bonus a nice tool to install / uninstall nvidia proprietary drivers using a single command as well.
Pure love 🥰
Ah, and just typing yay, updates everything 👌🏻
“Why dont windows users switch to Linux???”
Clear your mind. Simply “be” the screws. Do not aim for completion, for one is never complete. Also, it’s upside-down.
If you did tighten, DO NOT LOOSEN.
This is why I’m still on Windows 3.1
Hi, still on Windows 3.1. I’m dad.
This is why I’m still on Windows 7.