NetBSD/doc
chs a4ef51503f as a stop-gap measure to allow boot-from-disk to work on hppa,
add some padding to the end of struct scsipi_xfer on that platform.
2005-05-18 13:58:10 +00:00
..
3RDPARTY libevent-1.0e out. 2005-05-04 17:46:16 +00:00
BRANCHES Note that kent-audio2 is not compilable yet. 2005-04-15 13:39:00 +00:00
BUILDING.mdoc Document the environment variables for if you need to override or 2005-02-15 18:41:18 +00:00
CHANGES Import Intel ACPI-CA 20050408. 2005-05-02 15:09:59 +00:00
CHANGES.prev Move entry for 20050417 postinstall(8) move to list of changes in 2005-04-20 11:47:01 +00:00
HACKS as a stop-gap measure to allow boot-from-disk to work on hppa, 2005-05-18 13:58:10 +00:00
LAST_MINUTE
README.files
RESPONSIBLE Take responsibility for esa(4) and esl(4) 2005-04-08 00:30:14 +00:00
TODO Add some suggested projects (from Christos Zoulas). 2004-11-29 09:48:03 +00:00
TODO.i18n libintl implicit iconv has been implemented. 2004-01-20 12:08:13 +00:00
TODO.kqueue

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