1.0.16.18: Fixes to get clisp through host-1

[sbcl.git] / README

diff --git a/README b/README
index f07d4cf..86deff3 100644 (file)
--- a/README
+++ b/README
@@ -11,27 +11,36 @@ If you'd like to install or build the system, see the "INSTALL" file.
 
 If you'd like more information about using the system, see the man
 page, "sbcl.1", or the user manual in the "doc/" subdirectory of the
-distribution. (The user manual is maintained as DocBook SGML in the
-source distribution; there is an HTML version in the binary
-distribution.)
+distribution. (The user manual is maintained as Texinfo in the source
+distribution; HTML version is available for download.)
 
 The system is a work in progress. See the "TODO" file in the source
 distribution for some highlights.
 
+The "BUGS" file lists current known bugs.
+
 If you'd like to make suggestions, report a bug, or help to improve the
 system, please send mail to one of the mailing lists:
   sbcl-help@lists.sourceforge.net
   sbcl-devel@lists.sourceforge.net
+Note that as a spam reduction measure you must subscribe to the lists
+before you can post.
 
 
 SYSTEM-SPECIFIC HINTS
 
+for NetBSD:
+  NetBSD 2.0 and above are required because of the lack of needed
+  signal APIs in NetBSD 1.6 and earlier.
+
 for OpenBSD:
-  It's reported for CMU CL (by Darren Bane on the comp.lang.lisp newsgroup,
-  2002-04-22) that OpenBSD 3.0 has stricter ulimit values, and/or enforces
-  them more strictly, than its predecessors, and so CMU CL's initial mmap()
-  won't work unless you increase the limit on the data segment, e.g. with
-    ulimit -S -d 524288
-  before you run CMU CL. The same is probably true of SBCL, but hasn't been
-  tested yet. (As of sbcl-0.7.3, SBCL has only been tested on OpenBSD 2.9
-  and earlier.)
+  OpenBSD 3.0 has stricter ulimit values, and/or enforces them more
+  strictly, than its predecessors. Therefore SBCL's initial mmap()
+  won't work unless you increase the limit on the data segment from
+  the OpenBSD defaults, e.g. with
+    ulimit -S -d 1000000
+  before you run SBCL. Otherwise SBCL fails with a message like
+  "ensure_space: failed to validate xxxxxxx bytes at yyyyy". (SBCL
+  is just allocating this huge address space, not actually using this
+  huge memory at this point. OpenBSD <3.0 had no problem with this,
+  but OpenBSD 3.0 is less hospitable.)