diff --git a/1994/shapiro/README.md b/1994/shapiro/README.md index 749b64281..1ccacba13 100644 --- a/1994/shapiro/README.md +++ b/1994/shapiro/README.md @@ -51,7 +51,7 @@ source file is self documenting. :-) From time to time, run `ps(1)` and look at the new processes. See [shapiro.html](shapiro.html) for more information in the internals of this program. -The file [shapiro.alt.c](%%REPO_URL%%/1994/shapiro/shapiro.alt.c) contains a non-obfuscated version of +The file `shapiro.alt.c` contains a non-obfuscated version of this program. Note that this alt file is currently missing. See [1994 shapiro bugs](../../bugs.html#1994_shapiro) for details. @@ -71,14 +71,14 @@ My entry, [shapiro.c](%%REPO_URL%%/1994/shapiro/shapiro.c), is mostly comments, clock. If you strip out the comments and look at the code you will quickly realize that the comments were the important part and that the code does very little (see pun above). It writes (to `stdout`) -another C program ([shapiro_t2.c](%%REPO_URL%%/1994/shapiro/shapiro_t2.c). This is the first level of +another C program (`shapiro_t2.c`). This is the first level of obfuscation. -The second program ([shapiro_t2.c](%%REPO_URL%%/1994/shapiro/shapiro_t2.c) (use `make everything` first) -prints a clock in the upper right hand corner of your VTxxx/ANSI display. +The second program (`shapiro_t2.c`) prints a clock in the upper right hand +corner of your VTxxx/ANSI display. Most of the surface obfuscation in the second program, -[shapiro_t2.c](%%REPO_URL%%/1994/shapiro/shapiro_t2.c), was an attempt to make it as small as possible. +`shapiro_t2.c`, was an attempt to make it as small as possible. You should be able to see around this with `cb(1)` and some more intelligent variable names. Once you get past this you will realize that the third level of obfuscation is a six member client/server hierarchy. (See the diff --git a/1994/shapiro/index.html b/1994/shapiro/index.html index 918832e88..91b3159e1 100644 --- a/1994/shapiro/index.html +++ b/1994/shapiro/index.html @@ -421,7 +421,7 @@ bring it back to the foreground.

source file is self documenting. :-)

From time to time, run ps(1) and look at the new processes.

See shapiro.html for more information in the internals of this program. -The file shapiro.alt.c contains a non-obfuscated version of +The file shapiro.alt.c contains a non-obfuscated version of this program. Note that this alt file is currently missing. See 1994 shapiro bugs for details.

Author’s remarks:

@@ -432,12 +432,12 @@ this program. Note that this alt file is currently missing. See clock. If you strip out the comments and look at the code you will quickly realize that the comments were the important part and that the code does very little (see pun above). It writes (to stdout) -another C program (shapiro_t2.c. This is the first level of +another C program (shapiro_t2.c). This is the first level of obfuscation.

-

The second program (shapiro_t2.c (use make everything first) -prints a clock in the upper right hand corner of your VTxxx/ANSI display.

+

The second program (shapiro_t2.c) prints a clock in the upper right hand +corner of your VTxxx/ANSI display.

Most of the surface obfuscation in the second program, -shapiro_t2.c, was an attempt to make it as small as possible. +shapiro_t2.c, was an attempt to make it as small as possible. You should be able to see around this with cb(1) and some more intelligent variable names. Once you get past this you will realize that the third level of obfuscation is a six member client/server hierarchy. (See the