I believe the left hand is a shell fork-bomb, on the assumption that anything that zany is probably malicious.
And the right hand is a way to tell Make to use up all available system resources:
"-j [jobs]’ ¶
‘--jobs[=jobs]’
Specifies the number of recipes (jobs) to run simultaneously. With no argument, make runs as many recipes simultaneously as possible. If there is more than one ‘-j’ option, the last one is effective. See Parallel Execution, for more information on how recipes are run. Note that this option is ignored on MS-DOS."
Edit: I think the make command is technically only a problem when run for a Makefile that tries to do too many things, and has at least one mistake in dependency controls. So... for every Makefile I ever encountered (or that I ever wrote!)
I think it can also get weird when you call other makefiles, like if you go make -j64 at the top level and that thing goes on to call make on subprojects, that can be a looooot of threads of that -j gets passed down. So even on that 64 core machine, now you have possibly 4096 jobs going, and it surfaces bugs that might not have been a problem when we had 2-4 cores (oh no, make is running 16 jobs at once, the horror).
You are correct, left hand is a fork bomb. Specifically, it creates and then runs a function named ":". What this function does is pipe its output into itself while running in a background process, which instantly spawns infinite copies of itself. Technically I believe the : character could be any character as its just a name. The creator just picked a colon for aesthetics.
I'm pretty sure it's "run as many threads as there are cores" mode, though if you're running it in a terminal I always find it best to use nproc-1 or -2 so the machine actually stays usable.
i use pink 32bit net-book with openbsd as a mostly command line computer, for when i feel like i wanna take a break of all the bloat of all my other computers. (all my other primary computer run arch tho...)
Not an expert nor a historian, but my understanding is that 'find' goes back a long way (*nix has been around a while).
Earlier commands such as find were created back before a lot of command/option syntax forms we know today were agreed to and standardized.
Since 'find' has been around so long, we've just suffered its non-standard syntax rather than risk the chaos that would be unleashed by trying to fix it.
If it makes you feel better, you can console yourself that you're using one of the more arcane incantations of the elder *nix wizards.
It works now. It definitely didn't before when using Sync for Lemmy. That kind of mistake wouldn't have worked on the reddit website either. I had seen it a million times. Not sure if the Lemmy web site would handl it right.
Both versions work on my end.
I'm surprised to hear that.
Markdown libraries normally see the closing parenthesis in the URL as the end of the link markdown syntax of [text](link). You had [text](link(stuff)) which is parsed as [text](link(stuff) A smarter markdown parser could handle it, so whatever app you were using might do that.
I don’t mind the order of path, arguments and options, but what the hell is the deal with long arguments with a single dash? i.e. -name instead of —-name
linuxmemes
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.