NetBSD/doc
rillig b1cae80086 doc/CHANGES: fix typos 2023-07-01 09:21:47 +00:00
..
roadmaps desktop: update some details 2022-01-15 19:38:05 +00:00
3RDPARTY new OpenPAM. 2023-06-30 21:48:15 +00:00
BRANCHES fix various typos in documentation, comments and sysctl device description. 2023-03-26 19:10:32 +00:00
BUILDING.mdoc BUILDING: remove duplication from mk.conf(5) 2023-06-11 20:34:14 +00:00
CHANGES doc/CHANGES: fix typos 2023-07-01 09:21:47 +00:00
CHANGES.prev Fix typo. 2023-06-24 05:26:01 +00:00
HACKS Not hacks to use old binutils (2.34 instead of 2.39) on mips64* 2023-05-07 12:43:32 +00:00
LAST_MINUTE
Makefile doc: MAKEVERBOSE support 2023-05-16 07:48:50 +00:00
README.files
RESPONSIBLE
TODO
TODO.clang
TODO.compat-module
TODO.ext2fs
TODO.i18n
TODO.kaslr
TODO.modules
TODO.nits
TODO.npf
TODO.nvmm
TODO.smpnet Add bge(4) to the list of drivers that take advantage of NET_MPSAFE 2022-08-14 10:13:06 +00:00

README.files

#	$NetBSD: README.files,v 1.5 2012/09/06 22:20:38 riz 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.

images/		Bootable images, including ISOs and USB disk images.

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/mirrors/

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/about/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.