NetBSD/doc
bjh21 8724ced8ae inet(3): align signatures of inet_addr(), inet_network(),
inet_makeaddr(), inet_lnaof(), and inet_netof() with XNS and
                POSIX.  [bjh21 20030505]
2003-05-05 14:16:09 +00:00
..
3RDPARTY gcc-3.2.3 out. 2003-04-25 06:29:37 +00:00
BRANCHES Update to reflect merging of the nathanw_sa branch. 2003-01-19 20:06:22 +00:00
BUILDING.mdoc Fix example 3; the build.sh target is "install" not "installworld". 2003-02-08 10:00:33 +00:00
CHANGES inet(3): align signatures of inet_addr(), inet_network(), 2003-05-05 14:16:09 +00:00
CHANGES.prev DMA, not dma nor Dma. 2003-05-03 18:10:37 +00:00
HACKS Remove curses \E[m hack - fixed in setterm.c : 1.36. 2003-04-06 10:12:20 +00:00
LAST_MINUTE
README.files
RESPONSIBLE add the various evb* maintainers 2003-05-03 21:01:54 +00:00
TODO swept through the tree with find and grep looking for EDITOR. 2002-12-05 22:47:28 +00:00
TODO.kqueue pkgsrc/devel/py-kqueue added, remove from TODO list 2002-11-30 13:52:14 +00:00

#	$NetBSD: README.files,v 1.2 2002/09/23 08:02:34 lukem Exp $

What's in this directory:

CHANGES		Changes between the XXX.XXX-1 and XXX.XXX releases.

CHANGES.prev	Changes in previous NetBSD releases.

LAST_MINUTE	Last minute changes and notes about the release.

README.files	This file.

patches/	Post-release binary code patches.

shared/		Binary sets shared between multiple ports.

source/		Source code.

source/sets/	Source distribution sets; see below.

source/patches/	Post-release source code patches.



In addition to the files and directories listed above, there is one
directory per architecture, for each of the architectures for which
NetBSD XXX.XXX has a binary distribution.  The contents of each
architecture's directory are described in an "INSTALL" file found in
that directory.

The most recent list of mirror sites for NetBSD is viewable at the URL:

	http://www.NetBSD.org/Sites/net.html

If you are receiving this distribution on a CD set, some files and
subdirectories may be on a separate disc; read all README files for more
information.

See http://www.NetBSD.org/Misc/crypto-export.html for the formal status of
the exportability out of the United States of some pieces of the
distribution tree containing cryptographic software.  If you export these
bits and the above document says you should not do so, it's your fault,
not ours.