NetBSD/doc
simonb 1541f2efdc Describe the mips shared linker load address fix hack in
src/sys/kern/exec_elf32.c rev 1.107.
2005-10-07 08:42:24 +00:00
..
3RDPARTY acpica 20050930 is out. 2005-10-06 19:03:55 +00:00
BRANCHES fill in historical data for mrg-vm-swap and mrg-vm-swap2. 2005-07-07 19:20:20 +00:00
BUILDING.mdoc Change all .Xr config 8 to .Xr config 1, following the recent move of 2005-06-20 13:25:23 +00:00
CHANGES Note Xen network backend inprovements. 2005-10-02 21:55:41 +00:00
CHANGES.prev Move entry for ipsec-tools 0.6.1 update to "CHANGES.prev" after it has 2005-09-03 08:48:28 +00:00
HACKS Describe the mips shared linker load address fix hack in 2005-10-07 08:42:24 +00:00
LAST_MINUTE
README.files
RESPONSIBLE Forgot to note amd responsible on this file. 2005-09-27 10:12:46 +00:00
TODO * make clear what "window" is 2005-09-27 20:15:15 +00:00
TODO.i18n
TODO.kqueue
TODO.nits Fixing showmount was easier than I thought.. 2005-09-25 18:59:50 +00:00

README.files

#	$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.