All the platform-specific hints were obsolete or unhelpful at this point.

diff --git a/doc/README.aix b/doc/README.aix
deleted file mode 100644 (file)
index c28d9c6..0000000
--- a/doc/README.aix
+++ /dev/null
@@ -1,11 +0,0 @@
-Here are some tips&tricks for IBM users,
-from Chris Moller (moller@vnet.ibm.com, moller@futserv.austin.ibm.com):
-
-"Under IBM weirdness, after you modify /etc/services or /etc/inetd.conf,
-you have to update the ODM by running, from root, the following:
-
-        inetimp
-        chrctcp -S -c inetd -f debug='no' -f file='/etc/inetd.conf'
-
-or the changes don't take effect.  Other than that, everything worked
-fine out of the box."

diff --git a/doc/README.irix4 b/doc/README.irix4
deleted file mode 100644 (file)
index c64bf08..0000000
--- a/doc/README.irix4
+++ /dev/null
@@ -1,20 +0,0 @@
-Machine Type:          Silicon Graphics IRIX 4.*
-
-Make using:            make irix4
-Make optimised:                make "CFLAGS=-O" "LDFLAGS=-s" irix4
-
-Person(s) porting:     Simon Leinen <simon@lia.di.epfl.ch>
-Port date:             A long time ago...
-Verified working:      OS version(s)   Pident vers     Person
-                       4               2.1beta.10      <simon@lia.di.epfl.ch>
-
-Build comments:                Nothing unusual
-
-Install comments:      Generally install into /usr/etc
-
-Usage comments:                Works as daemon or from inetd with wait/nowait
-
-Known bugs:            It returns the <uid> of the process owning the
-                       socket in question instead of the <ruid>. Ie,
-                       it returns "root" instead of the actual user
-                       when the user runs a setuid-root program like rsh..

diff --git a/doc/README.irix5 b/doc/README.irix5
deleted file mode 100644 (file)
index 4cb7f18..0000000
--- a/doc/README.irix5
+++ /dev/null
@@ -1,11 +0,0 @@
-Frank Maas says:
-
-I have had this question a couple of times, so I wondered if you could
-add the following comment just before the #include <sys/vnode.h> state-
-ment in src/kernel/irix5.c... (we are talking pident2.5.1 here ;-):
-
-/** Well... here some problems begin: when upgrading IRIX to 5.3 the **/
-/** `inst' program shows one of its peculiar bugs: the file vnode.h  **/
-/** has changed location in between versions and now the file is up- **/
-/** grade first (new package) and then deleted (old package). So if  **/
-/** you have problems finding this file: reinstall eoe1.sw.unix.     **/

diff --git a/doc/README.sunos5 b/doc/README.sunos5
deleted file mode 100644 (file)
index 358ba79..0000000
--- a/doc/README.sunos5
+++ /dev/null
@@ -1,32 +0,0 @@
-Please note that the Solaris 2 port of Pidentd is very dependant
-on the version of Solaris. So when you upgrade to a new version of Solaris
-you most probably also must upgrade the Pidentd server. You can always
-find the latest version of Pidentd on ftp.lysator.liu.se in pub/ident/servers.
-
-Some common problems that may occur when compiling under Solaris 2:
-
-       * You use /usr/ucb/cc - NEVER ever EVER use that compiler
-
-       * You use GCC, but didn't run "fixincludes" correctly when
-         installing it
-
-       * You use GCC and have just upgraded from Solaris 2.3 to 2.4
-         (for example) and have forgotten to RERUN the "fixincludes".
-         This just *MUST* do or things will fail in mysterious ways.
-
-You may have to enable the "SOLARIS24_WORKAROUND" feature in the
-file "src/kernel/sunos5.c" if you have problems getting "-b" and/or "-w"
-to work correctly under Solaris 2.4. Please tell me if you do and it helps
-you (send an email to pen@lysator.liu.se).
-
-Casper Dik <casper@fwi.uva.nl> says:
-
-  I found a bug in Solaris 2.x inetd which may affect identd
-  installations:  if you change a tcp service from "nowait" to "wait" mode,
-  inetd will still pass the connected socket (as happens in nowait
-  mode) instead of the socket to do accept() on.  The workaround
-  is to first comment out the service and -HUP inetd, then reinstall
-  the service as wait service and resend -HUP.  Inetd apparently needs
-  to forget all about this service.  The symptom is accept returing
-  errno 22.
-