diff --git a/faq.html b/faq.html
index 920b595ae..315616abb 100644
--- a/faq.html
+++ b/faq.html
@@ -413,7 +413,7 @@
@@ -1184,7 +1185,7 @@ compilers might do different things, have different defects or other issues.
Note that the Makefiles check the CC variable by substrings so that if you
were to do something like make CC=gcc=mp-12 it would register as gcc.
-
FAQ 3.1: Why doesn’t this IOCCC entry compile?
+FAQ 3.1: Why doesn’t an IOCCC entry compile?
Some entries that won the IOCCC, particularly entries from long ago, no longer compile on more
modern systems because the C language has evolved (i.e. the modern C compilers
@@ -1204,6 +1205,9 @@ request for more information about pull requests.
that works for modern systems but one can view the original code in the
.orig.c files (sometimes the original code is also in the directory as a
dirname.alt.c or prog.alt.c).
+It might also be worth noting that almost all entries, have been
+fixed so that they can compile in modern systems though just because an entry
+compiles does not mean it will run on your specific system.
FAQ 3.2: Why does a IOCCC entry fail on my 64-bit system?
@@ -1213,7 +1217,7 @@ version macOS no longer supports 32-bit binaries. If the entry acts on a certain
type of binary, say ELF, then that will also be a problem depending on the
entry. For example 2001/anonymous requires 32-bit
ELF binaries.
-There are numerous example entries that require 32-bit binaries. We have tried
+
There are a few example entries that require 32-bit binaries. We have tried
to note these in both the respective Makefiles and index.html files but it is
possible that some were missed. These entries are very likely in the
bugs.html file and we welcome any help in making an alternate version
@@ -1629,7 +1633,7 @@ reason it’s not you might have to do something else including just piping it t
just grep intr or whatever.
-
FAQ 3.13: Why does an IOCCC entry fail to compile or or fail run?
+FAQ 3.13: Why does an IOCCC entry fail to compile and/or fail to run?
What may have worked years ago may not work well or work at all today.
@@ -1852,6 +1856,84 @@ to the top level directory of the winner repo you can do:
it like:
gmake MAKE=gmake
though of course for both you may specify a rule or rules to run.
+
+
+
3.20 - How do I download individual entries or entries of a given year?
+
+
Although one can clone the entire winner
+repo to get the entire web site and all
+entries, we also provide, as a convenience, a way to download individual entries
+as well as a way to download a year’s winning entries.
+Please note that some of the links in the html files will not work! This is
+because you are not downloading the full website. If you want to view the entry
+with links intact you should clone the repo or view it on the official IOCCC
+web site instead.
+Individual winning entry tarballs
+The individual entry tarballs are named in the form of
+YYYY/winner/YYYY_winner.tar.bz2 (e.g. 1984/mullender/1984_mullender.tar.bz2)
+and will have the following files:
+
+ioccc.css - stylesheet for the html filesvar.mk - the top level Makefile included by all the other Makefiles that holds variables used by the MakefilesYYYY/winner/.path - directory path from top level directoryYYYY/winner/.entry.json - entry summary and manifest in JSONYYYY/winner/.gitignore - list of files that should not be committed under git
+plus the winning entry files like source code, the Makefile, supplementary data
+provided by the author and any other file found in the winning entry, found in
+YYYY/winner.
+If you downloaded 1984/mullender/1984_mullender.tar.bz2, for instance, you might
+then do:
+ cd 1984/mullender
+ make everything
+ ./mullender.alt
to compile all versions and then run the alternate version (if you have
+a PDP-11 or VAX-11 you would be able to run the original version). For more help
+on compiling entries, see also 3.0 - What Makefile rules are available to
+build or clean up IOCCC entries?.
+If you want to view the index.html file you can point your browser to the
+index.html file of the winning entry (e.g. 1984/mullender/index.html) with the
+caveats noted above.
+Year based tarballs
+The year based tarballs, which are under each year’s directory and are named in the form
+of YYYY/YYYY.tar.bz2, have, along with each entry’s directory and their
+respective files (as if you downloaded each entry tarball of the year
+individually as described above), the following files:
+
+.filelist - list of files in the year that are not part of a winning entry of the year, including the YYYY.tar.bz2 tarballindex.html - the YYYY/index.html file rendered from the YYYY/README.md fileMakefile - Makefile for the year to compile etc. all entries of the yearREADME.md - the source of the YYYY/index.html filerules.txt - rules of the year’s contest.year - text file that has a list of the winning entries’ directories of the year
+Additionally, some will have extra files like:
+
+.gitignore - list of files that should not be committed under gitguidelines.txt - the guidelines of the yeariocccsize.c - iocccsize tool of the yeariocccsize.mk - Makefile to compile the iocccsize tool of the yeariocccsize-test.sh - test suite for the iocccsize tool
+.. and perhaps some others we have missed as well.
+If you extract a year’s tarball you can cd YYYY (e.g. cd 1984) and then run
+make everything to compile the entries and alt code of every entry), as if you
+switched to each entry’s directory and ran make everything in each one.
+If you download the 1984 tarball, i.e. 1984/1984.tar.bz2, then you might
+extract it and then switch to the directory and compile everything of each
+entry:
+ cd 1984
+ make everything
For more help on compiling entries, see also 3.0 - What Makefile rules are
+available to build or clean up IOCCC entries?.
+Of course in this case you can also switch to individual entries and look at the
+index.html file (or any other file in the entry) and try out the entries that
+interest you, as if you downloaded that entry’s individual tarball.
+If you want to view the index.html files of that tarball, for instance the
+year’s index.html file and then 1984/mullender/index.html you could point your
+browser to 1984/index.html, scroll down to Winning Entries of 1984 - The 1st IOCCC and click on the link 1984/mullender which will take you to the
+index.html file. Of course the caveats listed above still will apply.
Section 4: Changes made to IOCCC entries
diff --git a/faq.md b/faq.md
index 22f5988c2..8460d6671 100644
--- a/faq.md
+++ b/faq.md
@@ -30,7 +30,7 @@
## Section 3 - [Compiling and running IOCCC entries](#faq3)
- [3.0 - What Makefile rules are available to build or clean up IOCCC entries?](#faq3_0)
-- [3.1 - Why doesn't this IOCCC entry compile?](#faq3_1)
+- [3.1 - Why doesn't an IOCCC entry compile?](#faq3_1)
- [3.2 - Why does a IOCCC entry fail on my 64-bit system?](#faq3_2)
- [3.3 - Why do some IOCCC entries fail to compile under macOS?](#faq3_3)
- [3.4 - Why does clang or gcc fail to compile an IOCCC entry?](#faq3_4)
@@ -42,13 +42,14 @@
- [3.10 - How do I compile and use an IOCCC entry that requires sound?](#faq3_10)
- [3.11 - Why do Makefiles use -Weverything with clang?](#faq3_11)
- [3.12 - How do I find out how to send interrupt/EOF etc. for entries that require it?](#faq3_12)
-- [3.13 - Why does an IOCCC entry fail to compile or or fail run?](#faq3_13)
+- [3.13 - Why does an IOCCC entry fail to compile and/or fail to run?](#faq3_13)
- [3.14 - How do I compile and install tcpserver for entries that require it?](#faq3_14)
- [3.15 - How do I compile and install netpbm for entries that require it?](#faq3_15)
- [3.16 - How do I compile and install libjpeg-turbo for entries that require it?](#faq3_16)
- [3.17 - How do I compile and install ImageMagick for entries that require it?](#faq3_17)
- [3.18 - How do I compile and install OpenGL for entries that require it?](#faq3_18)
- [3.19 - What kind of make(1) compatibility does the IOCCC support and will it support other kinds?](#faq3_19)
+- [3.20 - How do I download individual entries or entries of a given year?](#faq3_20)
## Section 4 - [Changes made to IOCCC entries](#faq4)
@@ -1051,7 +1052,7 @@ were to do something like `make CC=gcc=mp-12` it would register as `gcc`.
-### FAQ 3.1: Why doesn't this IOCCC entry compile?
+### FAQ 3.1: Why doesn't an IOCCC entry compile?
Some entries that won the IOCCC, particularly entries from long ago, no longer compile on more
@@ -1077,6 +1078,10 @@ that works for modern systems but one can view the original code in the
`.orig.c` files (sometimes the original code is also in the directory as a
`dirname.alt.c` or `prog.alt.c`).
+It might also be worth noting that almost all entries, have been
+fixed so that they can compile in modern systems though just because an entry
+compiles does not mean it will run on your specific system.
+
### FAQ 3.2: Why does a IOCCC entry fail on my 64-bit system?
@@ -1089,7 +1094,7 @@ type of binary, say ELF, then that will also be a problem depending on the
entry. For example [2001/anonymous](2001/anonymous/index.html) requires 32-bit
ELF binaries.
-There are numerous example entries that require 32-bit binaries. We have tried
+There are a few example entries that require 32-bit binaries. We have tried
to note these in both the respective Makefiles and index.html files but it is
possible that some were missed. These entries are very likely in the
[bugs.html](bugs.html) file and we welcome any help in making an alternate version
@@ -1768,7 +1773,7 @@ just `grep intr` or whatever.
-### FAQ 3.13: Why does an IOCCC entry fail to compile or or fail run?
+### FAQ 3.13: Why does an IOCCC entry fail to compile and/or fail to run?
@@ -2187,6 +2192,111 @@ it like:
though of course for both you may specify a rule or rules to run.
+
+
+### 3.20 - How do I download individual entries or entries of a given year?
+
+
+
+Although one can clone the entire [winner
+repo](https://github.com/ioccc-src/winner) to get the entire web site and all
+entries, we also provide, as a convenience, a way to download individual entries
+as well as a way to download a year's winning entries.
+
+Please note that some of the links in the html files will not work! This is
+because you are not downloading the full website. If you want to view the entry
+with links intact you should clone the repo or view it on the [official IOCCC
+web site](https://www.ioccc.org) instead.
+
+
+#### Individual winning entry tarballs
+
+The individual entry tarballs are named in the form of
+`YYYY/winner/YYYY_winner.tar.bz2` (e.g. `1984/mullender/1984_mullender.tar.bz2`)
+and will have the following files:
+
+- `ioccc.css` - stylesheet for the html files
+- `var.mk` - the top level Makefile included by all the other Makefiles that holds variables used by the Makefiles
+- `YYYY/winner/.path` - directory path from top level directory
+- `YYYY/winner/.entry.json` - entry summary and manifest in JSON
+- `YYYY/winner/.gitignore` - list of files that should not be committed under git
+
+plus the winning entry files like source code, the Makefile, supplementary data
+provided by the author and any other file found in the winning entry, found in
+`YYYY/winner`.
+
+If you downloaded `1984/mullender/1984_mullender.tar.bz2`, for instance, you might
+then do:
+
+```sh
+ cd 1984/mullender
+ make everything
+ ./mullender.alt
+```
+
+to compile all versions and then run the alternate version (if you have
+a PDP-11 or VAX-11 you would be able to run the original version). For more help
+on compiling entries, see also [3.0 - What Makefile rules are available to
+build or clean up IOCCC entries?](#faq3_0).
+
+If you want to view the `index.html` file you can point your browser to the
+`index.html` file of the winning entry (e.g. `1984/mullender/index.html`) with the
+caveats noted above.
+
+
+#### Year based tarballs
+
+The year based tarballs, which are under each year's directory and are named in the form
+of `YYYY/YYYY.tar.bz2`, have, along with each entry's directory and their
+respective files (as if you downloaded each entry tarball of the year
+individually as described above), the following files:
+
+- `.filelist` - list of files in the year that are not part of a winning entry of the year, including the `YYYY.tar.bz2` tarball
+- `index.html` - the `YYYY/index.html` file rendered from the `YYYY/README.md` file
+- `Makefile` - Makefile for the year to compile etc. all entries of the year
+- `README.md` - the source of the `YYYY/index.html` file
+- `rules.txt` - rules of the year's contest
+- `.year` - text file that has a list of the winning entries' directories of the year
+
+
+Additionally, some will have extra files like:
+
+- `.gitignore` - list of files that should not be committed under git
+- `guidelines.txt` - the guidelines of the year
+- `iocccsize.c` - `iocccsize` tool of the year
+- `iocccsize.mk` - Makefile to compile the `iocccsize` tool of the year
+- `iocccsize-test.sh` - test suite for the `iocccsize` tool
+
+.. and perhaps some others we have missed as well.
+
+If you extract a year's tarball you can `cd YYYY` (e.g. `cd 1984`) and then run
+`make everything` to compile the entries and alt code of every entry), as if you
+switched to each entry's directory and ran `make everything` in each one.
+
+If you download the 1984 tarball, i.e. `1984/1984.tar.bz2`, then you might
+extract it and then switch to the directory and compile everything of each
+entry:
+
+```sh
+ cd 1984
+ make everything
+```
+
+For more help on compiling entries, see also [3.0 - What Makefile rules are
+available to build or clean up IOCCC entries?](#faq3_0).
+
+Of course in this case you can also switch to individual entries and look at the
+`index.html` file (or any other file in the entry) and try out the entries that
+interest you, as if you downloaded that entry's individual tarball.
+
+
+If you want to view the `index.html` files of that tarball, for instance the
+year's `index.html` file and then `1984/mullender/index.html` you could point your
+browser to `1984/index.html`, scroll down to `Winning Entries of 1984 - The 1st
+IOCCC` and click on the link `1984/mullender` which will take you to the
+`index.html` file. Of course the caveats listed above still will apply.
+
+
## Section 4: Changes made to IOCCC entries