NetBSD/doc
junyoung 3962094d84 binutils 2.15, db 4.2.52, gdb 6.1.1.
while here, drop trailing spaces.
2004-06-29 05:24:37 +00:00
..
3RDPARTY binutils 2.15, db 4.2.52, gdb 6.1.1. 2004-06-29 05:24:37 +00:00
BRANCHES Add 2.0 branch 2004-03-29 03:10:41 +00:00
BUILDING.mdoc Document -h. From Karsten Kruse in PR 25974. 2004-06-25 15:04:02 +00:00
CHANGES Note MPC601 and IBM RS/6000 40P support. 2004-06-26 21:56:12 +00:00
CHANGES.prev acorn32: Generate sparkive with new bootloader for install 2004-06-25 18:38:50 +00:00
HACKS Modify latest vax entry to instead point to the commit by mhitch, now 2004-06-06 17:11:33 +00:00
LAST_MINUTE
README.files
RESPONSIBLE Add myself to "usb" and "acpi". 2004-06-28 18:38:14 +00:00
TODO Take Unix98 ptys off the To Do list (thanks, Christos!) 2004-05-27 03:46:32 +00:00
TODO.i18n libintl implicit iconv has been implemented. 2004-01-20 12:08:13 +00:00
TODO.kqueue test-compiled evbsh5 CAYMAN and SIMULATOR, and pc532 GENERIC, remove from TODO 2003-12-08 06:43:55 +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.