fix many internal links
Fixed a number of internal links that need to go to the GitHub site. Ran `make www` to perform the above.
This commit is contained in:
1 parent
b84f8cbe28
commit
e7d69bc232
175 files changed
+645
-631
No files matched your search
@@ -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](shapiro.alt.c) contains a non-obfuscated version of
|
||||
The file [shapiro.alt.c](%%REPO_URL%%/1994/shapiro/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.
|
||||
|
||||
@@ -67,18 +67,18 @@ The basic theme (pun) of this program is:
|
||||
```
|
||||
|
||||
|
||||
My entry ([shapiro.c](shapiro.c)) is mostly comments, formatted in the shape of a
|
||||
My entry ([shapiro.c](%%REPO_URL%%/1994/shapiro/shapiro.c)) is mostly comments, formatted in the shape of a
|
||||
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](shapiro_t2.c)). This is the first level of
|
||||
another C program ([shapiro_t2.c](%%REPO_URL%%/1994/shapiro/shapiro_t2.c)). This is the first level of
|
||||
obfuscation.
|
||||
|
||||
The second program ([shapiro_t2.c](shapiro_t2.c) (use `make everything` first)
|
||||
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.
|
||||
|
||||
Most of the surface obfuscation in the second program
|
||||
([shapiro_t2.c](shapiro_t2.c)) was an attempt to make it as small as possible.
|
||||
([shapiro_t2.c](%%REPO_URL%%/1994/shapiro/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
|
||||
|
||||
Reference in new issue
Block a user