git mv *.hint -> README.md

There is one exception:

    $ find . -name '*.hint' -execdir git mv '{}' README.md \;
    git statufatal: destination exists, source=1992/albert/albert.hint, destination=1992/albert/README.md

Looking at the two files they differ quite a bit so I've not changed it.
I'll bring this up on GitHub.
This commit is contained in:
Cody Boone Ferguson committed 2023-02-08 05:47:28 -08:00
1 parent 046692c03e
commit 17ea7fbd9e
155 files changed

No files matched your search

+169
View File
@@ -0,0 +1,169 @@
Best Abuse of the Guidelines:
Anthony Howe
Snert
42 av. Isola Bella
06400 Cannes
France
http://www.snert.com/
Judges' Comments:
To build (simple: Cygwin, FreeBSD, Linux, Mac OS X):
tar -zxf hibachi.tgz
cd hibachi
./configure
make
Try:
cd hibachi
./hibachi-start.sh
Then use your web browser to visit http://localhost:8008/
This entry violates the guidelines in so many ways! We are not
exactly sure how many org's will be upset with this entry, but we
are considering starting an IOCCC standards body just to reign in
the likes Mr Howe.
This entry also has the dubious honour of being the only one to have
been submitted with its own ./configure script.
Selected Author's Comments:
README.TXT Feb 2004
==========
Hibachi is a simple, small, and (probably) very secure web server.
There is a `hibachi.tgz' file that unpacks several support
files and a sub-directory tree containing the documentation and
examples. It can be viewed by:
tar -zxf hibachi.tgz
lynx hibachi/localhost/index.html
Or once Hibachi is running, use a web browser, preferably one that
supports images and JavaScript, to view the documentation and try
some of the CGI examples:
http://localhost:8008/
Building
--------
To build just the executable:
# Cygwin, FreeBSD, Linux (newer), Mac OS X
gcc -o hibachi hibachi.c
# Linux (older)
gcc -DSHUT_WR=1 -o hibachi hibachi.c
# SunOS
gcc -o hibachi hibachi.c -lnsl -lsocket
Since some systems place socket and network functions into other
libraries, a GNU autoconf ./configure script has been provided to
figure out the necessary link libraries, to verify all the
necessary headers and functions are present, and setup the #!
paths for the CGI examples. In which case the preferred build
commands are:
./configure [--enable-port=number]
make
To start the server on the default port (8008):
./hibachi-start.sh &
To test the server:
lynx http://localhost:8008/
To stop the server:
kill %1
Features
--------
o Supports virtual hosts.
o Supports all MIME types.
o Supports Common Gateway Interface (CGI) scripts and programs.
o Supports multiple index.* file types:
index.htm, index.html, index.php, index.pl,
index.sh, index.rb, index.py
o Supports subset of RFC 2616 HTTP/1.1 methods:
GET, HEAD, and POST
o Simple & straight forward configuration using environment variables.
o Portability across Unix-like environments, such as:
Cygwin, FreeBSD, Linux, SunOS.
o Known to work with Lynx, Mozilla, Opera, and Internet Explorer
web browsers.
o Is a dedicated process-forking server that does not use inetd.
o Is secure against relative path file snooping.
o Is secure against directory searches.
o CGI script execution managed through Unix file permissions.
o ~155 lines of source,
1940 bytes long by IOCCC 2004 rules,
~6KB compiled & stripped for FreeBSD.
o Superior & smaller than micro_httpd from http://www.acme.com/
o And has a really cool tongue-in-cheek animated logo too.
Comments
--------
o This code is properly indented using the One True Brace style.
o HTTP/1.0 200 OK == HTTP/1.1 200 OK CRLF Connection: close ?
o getenv() == putenv() ?
o Hibachi can serve www.ioccc.org.
o Commented spoiler available.
Known Issues
------------
o The "links" text browser does not support RFC 2616 section 7.2.1
paragraph 3 sentence 2, and so fails to display responses from
hibachi.
Suggested IOCCC Categories
--------------------------
Best Utility
Best Support
Most Portable Package
Most Likely to Cook Apache
Best Interpretation of RFC 2616
Winner of The Far Too Much Free Time Award