Paul Vixie <paul@vix.com> wrote that for BSDi 2.0the use of mmap for 
use with the history file is ok (add -DMMAP to DBZCFLAGS in config.data), 
but not for active, so set ACT_STYLE to READ. Others write that it is
not. Your mileage may vary and depend on how heavily-used your machine
is.

For NetBSD1.0 and 1.1 one shouldn't use mmap() unless you add the 
following:

*** icd.c.orig  Wed Jun  7 15:04:05 1995
--- icd.c       Sat Dec 30 16:22:50 1995
***************
*** 369,375 ****
  ICDwriteactive()
  {
  #if   defined(ACT_MMAP)
!     /* No-op. */
  
  #else
  
--- 369,375 ----
  ICDwriteactive()
  {
  #if   defined(ACT_MMAP)
!     msync(ICDactpointer, 0);
  
  #else
 
In NetBSD 1.1 the use of -DMMAP is also ok.(after Curt Sampson <curt@portal.ca>)

FreeBSD users should use mmap() with caution. There are serious problems 
with some realeases of the FreeBSD operating system concerning mmap()
and the performance without is quite good. With current releases,
namely 2.2.1, this seems fixed.

Users of 4.4 BSD derived systems should set LSEEKVAL in config.data to
``off_t'' in order to reflect the 64bit long off_t's in those systems.

If you have problems with makehistory on BSDi then replace the BSDi sort 
command with an other one e.g. from the gnu textutils package. It seems 
that the BSDi one has some problems with 64kB boundaries.

BSDi has a default some datasize limits which will let some operations
fail. Add the following at the beginning of rc.news (and also of news.daily):

limit datasize unlimited
limit openfiles 256
limit memoryuse unlimited
limit maxproc unlimited

If this still fails look at #5.24 (the same applies to FreeBSD).

In 2.1, BSDi introduced a bug with wrong spelling of ``february''
somewhere which lets inn fail somehow .. But they also have a patch:

ftp://ftp.bsdi.com/bsdi/patches/patches-2.1/U210-002

Here's the Summary from the fix:

    This patch fixes a bug in the BSD/OS 2.1 release of the inn
    programs.  A fix that we made between the 2.0 and 2.1
    releases introduced a bug that caused innd to incorrectly
    parse dates.  The symptom is that inn programs fail with
    "437 Bad "Date" header" in the /var/log/news/news file, or
    that Pnews will fail with "441 Can't parse "Date" header"
    messages.

For FreeBSD 2.1.6 and INN1.5 Vincent Archer <archer@frmug.org> has written
a autoconf package, that you can get from 
<ftp://ftp.frmug.org/pub/news/autoconf-inn.1.5.tar.gz>
James will try to incorporate this into the main INN tree.

To get it to work:

Go to your inn 1.5 source directory, untar, you'll get configure and
config/config.data.in.
    
Type ./configure; make; make install :)
(well, you might want to check the pathnames and parameters first, or type
 ./configure --help)

Some parts © 2009 Advameg, Inc.