Thanks for the red circle, I was really lost there for a moment
this post was submitted on 16 Oct 2024
860 points (98.0% liked)
linuxmemes
27922 readers
731 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
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.
founded 2 years ago
MODERATORS
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
β
βοΈ
π₯π₯π₯π₯π₯π₯π₯π₯π₯π₯π₯π₯π₯π₯π₯π₯
π₯Thanks for the red circle, π₯
π₯I was really lost there for a moment. π₯
π₯π₯π₯π₯π₯π₯π₯π₯π₯π₯π₯π₯π₯π₯π₯π₯
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.
load more comments
(1 replies)
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
load more comments
(3 replies)
"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"
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).
βWhy dont windows users switch to Linux????β
load more comments
(3 replies)
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?
load more comments
(1 replies)
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.
As someone who works in manufacturing this makes prefect sense and wish more instructions were this clear
How π€¨... tighten, but don't...
Tighten them but tighten them not too much but make sure not to tighten them too less, I guess
Tighten but don't overtighten them, probably.
load more comments
(8 replies)
If you did tighten, DO NOT LOOSEN.
Clear your mind. Simply "be" the screws. Do not aim for completion, for one is never complete. Also, it's upside-down.
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 why I'm still on Windows 7.
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.
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?
To screw or not to screw.
A little bit of both π€·...
Oh bro, it's the Art of War.
view more: next βΊ