From e8ad2bf89e1053ee8b42a7a9342543503072879c Mon Sep 17 00:00:00 2001 From: Deven Blake Date: Mon, 21 Jun 2021 08:24:21 -0400 Subject: [PATCH] more markup --- homepage/knowledge/cat.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/homepage/knowledge/cat.html b/homepage/knowledge/cat.html index 3527be5..d972954 100644 --- a/homepage/knowledge/cat.html +++ b/homepage/knowledge/cat.html @@ -69,14 +69,14 @@ window.load_highlighting = function(language){

cat was introduced in UNIX v1 to supercede the program pr which printed the contents of a single file to the screen (McIlroy); its first-edition manual page described cat as “about the easiest way to print a file” (“cat(1)”). -cat’s modern, typical use is more or less the same; it’s often introduced to UNIX beginners as a method to print the contents of a file to the screen, which is why many implementations of cat include options that are technically redundant - see the often-included cat -e, -t, and -v that replace the ends of lines, tabs, and invisible characters respectively with printing portrayals (“cat(1p)”). +cat’s modern, typical use is more or less the same; it’s often introduced to UNIX beginners as a method to print the contents of a file to the screen, which is why many implementations of cat include options that are technically redundant - see the often-included cat -e, -t, and -v that replace the ends of lines, tabs, and invisible characters respectively with printing portrayals (“cat(1p)”).

The POSIX standard as of 2003 requires only the option -u to be implemented, which prevents cat from buffering its output - on some systems, cat buffers its output in 512-byte blocks (McIlroy), similarly to dd’s default as defined by POSIX (“dd(1p)”), though most currently popular cat implementations do this by default and ignore the -u flag altogether (busybox, GNU coreutils). POSIX doesn’t mandate buffering by default - specifically, -u has to guarantee that the output is unbuffered, but cat doesn't have to buffer it in the first place and can ignore -u in that case.

-This is a POSIX-compliant implementation of UNIX cat with no additional features nor buffered output in C: +This is a POSIX-compliant implementation of UNIX cat with no additional features nor buffered output in C: 


@@ -172,7 +172,7 @@ main(int argc, char *argv[]){
 }
-

It’s worth noting that this concept of cat as a utility that sequentially prints given files to standard output means cat can be replaced by a simple shell script that does the same using dd and printf; cat as defined by POSIX is actually totally redundant to other POSIX utilities. Here’s the shell script:

+

It’s worth noting that this concept of cat as a utility that sequentially prints given files to standard output means cat can be replaced by a simple shell script that does the same using dd and printf; cat as defined by POSIX is actually totally redundant to other POSIX utilities. Here’s the shell script:


 #!/bin/sh
@@ -243,7 +243,7 @@ done
 exit 0
-

cat still has a purpose though. This shell script is relatively slow for short files and very slow for very large files (though dd itself should probably be used to copy large files from one medium to another anyway). This is provided for educational purposes (though I personally use this shell script in my system PATH; the C implementation provided compiles to a much larger binary using gcc 11.1.0, so this saves a couple kilobytes).

+

cat still has a purpose though. This shell script is relatively slow for short files and very slow for very large files (though dd itself should probably be used to copy large files from one medium to another anyway). This is provided for educational purposes (though I personally use this shell script in my system PATH; the C implementation provided compiles to a much larger binary using gcc 11.1.0, so this saves a couple kilobytes).

Cited media and further reading