haad c9d0c62a0c Merge the haad-dm branch to -current. This branch adds LVM functionality to
the base NetBSD system. It uses Linux LVM2 tools and our BSD licensed
device-mapper driver.

The device-mapper driver can be used to create virtual block devices which
maps virtual blocks to real with target mapping called target. Currently
these targets are available a linear, zero, error and a snapshot (this is
work in progress and doesn't work yet).

The lvm2tools adds lvm and dmsetup binary to based system, where the lvm
tool is used to manage and administer whole LVM and the dmestup is used to
communicate iwith device-mapper kernel driver. With these tools also
a libdevmapper library is instaled to the base system.

Building of tools and driver is currently disable and can be enabled with
MKLVM=yes in mk.conf. I will add sets lists and rc.d script soon.

Oked by agc@ and cube@.
2008-12-19 15:24:03 +00:00
..

#	$NetBSD: README.files,v 1.4 2007/12/14 21:15:52 pavel 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/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.