systemd-detect-fash
detects execution in a fascist environment. It identifies the fascist technology and can distinguish full machine fascism from installed fashware.systemd-detect-fash
exits with a return value of 0 (success) if a fascism technology is detected, and non-zero (error) otherwise.
Useless, you don’t need a tool to tell whether or not you’re running Windows.
I love both that it’s even well written as well as the professional answer it got despite its nature.
I present you with another, better utility: am-i-an-imbecile. It just returns 1. Run it to make sure that you’re good.
returns 1
That just means the user is not an imbecille, there’s still a great number of scenarios to rule out
That just means the user is not an imbecille
It doesn’t. 0 – false, !0 – true.
no, exit codes work the other way round: 0 = success, !0 = error
No, you use common sense if you’re returning actual data in exit codes. Return 0 as ok works only for the “well, program finished its work without obvious errors” situation. This isn’t the case.
Every time an exit code is a boolean, 0 is true. Shell scripting would be very annoying if this were inconsistent
A program that provides data is providing data. If the program’s actual work result is 42 then it is quite logical to return 42.
But to stop this pointless bickering, I can suggest you another (even more better) utility: am-i-an-formalistically-irritating-imbecile that will return 0 as exit code and “yes” in stdout.
created with a russian military email to create division