Allow me to retort with an all-in-one self build script, along with pass-through args and exitcode.

#!/bin/sh
out=$(mktemp)
sed -e '0,/^#SELFBUILD$/d' "$0" | rustc --o "$out" - && "$out" "$@"
status=$?
rm -f "$out"
exit "$status"
#SELFBUILD

fn main() {
    dbg!(std::env::args());
    println!("hello rust");
    std::process::exit(2);
}

P.S. I have no idea why you’d want that, as it’s a terribly inefficient way to ship code, but it’s a fascinating glimpse at how we used to do self-extract archives decades ago.

Interestingly, we’ve got the same glitch in the Gregorian calendar, where the year 0 doesn’t exist. So the 21st century started in 2001…

The opinion of Linux desktop users (or any users really) do not count in the enterprise world. Somehow, if management bought in on the Crowdstrike rootkit bandwagon, you’ll see it on corporate hardware. It doesn’t matter if it’s a bad plan; it doesn’t matter if it gives an American company a backdoor to all you infrastructure; if the CISO decides everyone gets it, everyone get it.

The only thing you can really do as a lowly employee is keep any such device away from any personal info or network as if it’s infected by malware (which I would argue is exactly what it is).

just tag yourself as “early-access” and suddenly everyone will forgive your flaws.

Hacker: That’s ok, we don’t want you to paste stuff in there, we just want you to send us your cookies. It’s not like you’re eating them anyway…