From 5149d9c4f6bed05988fa019f081113aafb486f29 Mon Sep 17 00:00:00 2001 From: Deven Blake Date: Wed, 18 Aug 2021 22:56:25 -0400 Subject: [PATCH] fix one-liner --- homepage/knowledge/true.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/homepage/knowledge/true.html b/homepage/knowledge/true.html index 06c5611..5f50e2d 100644 --- a/homepage/knowledge/true.html +++ b/homepage/knowledge/true.html @@ -56,7 +56,7 @@ In some shells, true(1) is a shell built-in command, so running GNU true(1), from the GNU coreutils, deserves a special mention, as it's eighty lines long and directly includes four C header files. This is not a joke. -Their true.c is 2.3 kilobytes, parses the arguments --help and --version (only if either are the first argument to the program), and I don't know how big the executable ends up being because the first thing I do when I take control of a GNU system is printf "#/bin/sh\nexit 0\n"|dd of="$(which true)";chmod +x "$(which true)" (use at your own risk). +Their true.c is 2.3 kilobytes, parses the arguments --help and --version (only if either are the first argument to the program), and I don't know how big the executable ends up being because the first thing I do when I take control of a GNU system is dd if=/dev/null of="$(which true)";chmod +x "$(which true)" (use at your own risk). The GNU coreutils implementation of true(1) is not POSIX compliant.

Cited media and further reading