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…
Computers are as much ritual and magic as they are understanding. The Tech Priests of WH40k had the right of it.
“Just follow the build instructions on GitHub”
1000 error messages ensue.
That’s your own darn fault. You were supposed to know the 0.0.1 version was GA instead of assuming 0.0.3-alpha was stable. You would have known if you read the 2000 line README. On the second dependency there is no README though, so just use the latest and hope it’s still compatible.
Last commit 8 years ago “Updated for Linux 4.5”
Then do some digging and find that the GitHub instructions omitted some particular dependency, make a mental note to contribute a PR to the documentation later once you’ve got it working, get it working, promptly forget contributing that documentation, move distro later, try to reinstall the same program, make the same mistake, same discovery, learn nothing, repeat ad nauseam.
I’m trying to learn Houdini. I thought, “Oh, I’ll just download a template and see how it should look.”
Even already-made templates are apparently out-of-my-depth.
Don’t use sudo to run this command, but do so if it doesn’t work. Using sudo may break your system.
The sudo thing should really be explained like “if you want this implemented system wide, run it with sudo, if not, don’t use it”.
This is some unnecessary red circle shit right here.
But look how pretty it is 😊.
Clearly added for emphasis, crucial instructions, we might mistake for other instructions in the picture.
Tighten’t.
It’s hard enough to express this in a first language
What is a first language?
The first one you learned or became fluent in. For example, it’s often English for USA people or Spanish for Spanish people, or Japanese for Japanese people
Often also called mother tongue or primary language.
Otherwise, it can be the one you are most comfortable with or default to.
Ahh, I see, I think it is a translation issue where the tect got too long ant cut. I suppose the missing words are “… too much”.
That said in my first language: “zie d schruube ah, pass aber uf dass sie ned zu fest aziesch”
What dialect is that? Sounds like Pfälzisch to me but I never was good at placing other dialects
It is a flavour of german talked in Zurich, Switzerland. I personally have some influence from cantons east of Zurich. There are no rules about how to write, we just write phonetically. Official stuff is written in German German.
Way off the mark then, embarrassing. Particularly since I’m from Southwest Germany, you’d think I’d recognise Schwyzerdütsch. I definitely need more exposure to dialects.
Oh yeah I think it was a translation issue. Translators have trouble with conjugation and synonyms. But the result is the same.
A regional dialect doesn’t a whole language make
That is not just a regional dialect. And in my opinion dialects are more first language than the learning “real language” afterwards. That is clearly the second language…
English is slightly ambiguous here. As tighten has 2 meanings. Turning a screw clockwise is to tighten it, as opposed to loosen it anticlockwise. But it’s quite loose. Finally, to make it tight and secure, you tighten it with one last turn.
Shouldn’t “screw in the screw” be used instead of “tighten the screw” when you’re just inserting it fully but not tightening it?
Makes sense. You should design furniture manuals for IKEA.
I’m actually fairly good with writing tutorials… or so I’ve been told.
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.
If you love that, NASA has a whole 100 page PDF about fasteners:
https://ntrs.nasa.gov/api/citations/19900009424/downloads/19900009424.pdf
One particularly notable part is about split lock washers. They’re useless, often detrimental, and need to go away. NASA said so in 1990 and there’s no reason to think this has changed.
Don’t tighten it tight
Can I get this picture without the caption and red circle?
Don’t know where it’s from, found it on reddit.
Try searching for it through images.google.com or the text in the image.
Oh bro, it’s the Art of War.
Gotta say, arch wiki was great for learning this stuff
To screw or not to screw.
A little bit of both 🤷…
Noted.
Thanks for the red circle, I was really lost there for a moment
I can’t find where your comment is. Can you please add a red circle so I can read it?
Thanks for the red circle, I was really lost there for a moment
➕
⭕️