Move INABIAF to bugs.md in 1980s entries

Having to click on the links in each README.md file will have to be done
to verify the links work but it appears to be in the form of:

    /bugs.md#YYYYauthor-readmemd

1984/laman/README.md

@@ -8,12 +8,6 @@ Mike Laman
 make all
 ```
 
-## To run:
-
-```sh
-./laman <positive number>
-```
-
 ### Bugs and (Mis)features
 
 This entry a listed in [bugs.md](/bugs.md) as:
@@ -24,6 +18,14 @@ STATUS: INABIAF - please **DO NOT** fix
 
 For more detailed information see [bugs.md](/bugs.md#1984laman-readmemd).
 
+
+## To run:
+
+```sh
+./laman <positive number>
+```
+
+
 ## Try:
 
 The program accepts ONE POSITIVE number.  Seeing is believing, so try things

1988/dale/README.md

@@ -9,6 +9,19 @@ Australia
 make all
 ```
 
+### INABIAF - it's not a bug it's a feature! :-)
+
+### Bugs and (Mis)features
+
+This entry a listed in [bugs.md](/bugs.md) as:
+
+```
+STATUS: INABIAF - please **DO NOT** fix
+```
+
+For more detailed information see [bugs.md](/bugs.md#1988dale-readmemd).
+
+
 ## Try:
 
 ```sh
@@ -26,11 +39,6 @@ behaviour?
 ./dale "$(printf "the following files exist in this directory:\n%s\n" *)"
 ```
 
-### INABIAF - it's not a bug it's a feature! :-)
-
-In linux it might happen that core dumps are created when running this entry
-even though it works fine and you don't see any message about dumping core.
-
 ### Alternate code
 
 If you have an old enough compiler you can try the original version in

1989/fubar/README.md

@@ -1,10 +1,6 @@
 # Best self-modifying program
 
 Jay Vosburgh\
-Sequent Computer Systems, Inc\
-15450 SW Koll Parkway\
-Beaverton, OR\
-97006\
 US
 
 ## To build:
@@ -13,6 +9,18 @@ US
 make all
 ```
 
+
+### Bugs and (Mis)features
+
+This entry a listed in [bugs.md](/bugs.md) as:
+
+```
+STATUS: INABIAF - please **DO NOT** fix
+```
+
+For more detailed information see [bugs.md](/bugs.md#1989fubar-readmemd).
+
+
 ## To run:
 
 ```sh
@@ -25,11 +33,6 @@ make all
 ./fubar 2
 ```
 
-### INABIAF - it's not a bug it's a feature! :-)
-
-If you use either `fubar` or `ouroboros.c` (it's executable, see below) with a
-number < 0 or larger than, say 20, it's very likely that the program will turn
-into an infinite loop trying to compile code with syntax errors.
 
 ## Judges' remarks:
 

1989/robison/README.md

@@ -1,10 +1,6 @@
 # Best minimal use of C
 
 Arch D. Robison\
-University of Illinois\
-1304 W. Springfield Ave.\
-Urbana, IL\
-61801\
 US
 
 ## To build:
@@ -13,6 +9,16 @@ US
 make all
 ```
 
+### Bugs and (Mis)features
+
+This entry a listed in [bugs.md](/bugs.md) as:
+
+```
+STATUS: INABIAF - please **DO NOT** fix
+```
+
+For more detailed information see [bugs.md](/bugs.md#1989robison-readmemd).
+
 
 ## To run:
 

bugs.md

@@ -542,7 +542,8 @@ or any others.
 ## STATUS: INABIAF - please **DO NOT** fix
 
 In linux it might happen that despite no error message or message about doing
-so, the program drops a core file into the directory.
+so, the program drops a core file into the directory even though the entry works
+and does not crash.
 
 # 1989
 
@@ -550,10 +551,12 @@ so, the program drops a core file into the directory.
 ## [1989/fubar](1989/fubar/fubar.c) ([README.md](1989/fubar/README.md))
 ## STATUS: INABIAF - please **DO NOT** fix
 
-Specifying too large a number (or < 0) to either `fubar` or the source code file
-(it's executable) that it generates will cause the program to enter an infinite
-loop, trying to compile code with syntax errors. At least in one system any
-number larger than 20 did this.
+If you use either `fubar` or `ouroboros.c` (it's executable, see README.md for
+details) with a number < 0 or larger than, say 20, it's very likely that the
+program will turn into an infinite loop trying to compile code with syntax
+errors.
+
+
 
 ## [1989/robison](1989/robison/robison.c) ([README.md](1989/robison/README.md))
 ## STATUS: INABIAF - please **DO NOT** fix