Package: clvm-openais Source: lvm2 Version: 2.02.44-4~bpo50+1 Architecture: i386 Maintainer: Debian LVM Team Installed-Size: 472 Depends: libc6 (>= 2.7-1), libdevmapper1.02.1 (>= 2:1.02.30), libopenais-legacy-2 (>= 0.80.5+svn20090522), lvm2 (= 2.02.44-4~bpo50+1), lsb-base Conflicts: clvm Replaces: clvm (<= 2.02.44-3) Filename: ./clvm-openais_2.02.44-4~bpo50+1_i386.deb Size: 220228 MD5sum: 0577a3df3943b12762059769cb0ab073 Section: admin Priority: extra Description: Cluster LVM Daemon for lvm2 This package provides the clustering interface for lvm2, when used with the OpenAIS cluster infrastructure. It allows logical volumes to be created on shared storage devices (eg Fibre Channel, or iSCSI). Package: dmsetup Source: lvm2 (2.02.44-4~bpo50+1) Version: 2:1.02.30-4~bpo50+1 Architecture: i386 Maintainer: Debian LVM Team Installed-Size: 92 Depends: libc6 (>= 2.7-1), libdevmapper1.02.1 (>= 2:1.02.27) Filename: ./dmsetup_1.02.30-4~bpo50+1_i386.deb Size: 42206 MD5sum: d9a49f890eb3d694d919e18b9a9fce6f Section: admin Priority: optional Description: The Linux Kernel Device Mapper userspace library The Linux Kernel Device Mapper is the LVM (Linux Logical Volume Management) Team's implementation of a minimalistic kernel-space driver that handles volume management, while keeping knowledge of the underlying device layout in user-space. This makes it useful for not only LVM, but EVMS, software raid, and other drivers that create "virtual" block devices. . This package contains a utility for modifying device mappings. Package: libdevmapper-dev Source: lvm2 (2.02.44-4~bpo50+1) Version: 2:1.02.30-4~bpo50+1 Architecture: i386 Maintainer: Debian LVM Team Installed-Size: 192 Depends: libdevmapper1.02.1 (= 2:1.02.30-4~bpo50+1) Filename: ./libdevmapper-dev_1.02.30-4~bpo50+1_i386.deb Size: 74562 MD5sum: 4ce4381f055e35094d63810c72c29c00 Section: libdevel Priority: optional Description: The Linux Kernel Device Mapper header files The Linux Kernel Device Mapper is the LVM (Linux Logical Volume Management) Team's implementation of a minimalistic kernel-space driver that handles volume management, while keeping knowledge of the underlying device layout in user-space. This makes it useful for not only LVM, but EVMS, software raid, and other drivers that create "virtual" block devices. . This package contains the (user-space) header files for accessing the device-mapper; it allow usage of the device-mapper through a clean, consistent interface (as opposed to through kernel ioctls). Package: libdevmapper1.02.1 Source: lvm2 (2.02.44-4~bpo50+1) Version: 2:1.02.30-4~bpo50+1 Architecture: i386 Maintainer: Debian LVM Team Installed-Size: 140 Depends: libc6 (>= 2.7-1), libselinux1 (>= 2.0.59) Provides: libdevmapper Filename: ./libdevmapper1.02.1_1.02.30-4~bpo50+1_i386.deb Size: 58654 MD5sum: f6aea20e5a6638d40461a50d6192ebc0 Section: libs Priority: required Description: The Linux Kernel Device Mapper userspace library The Linux Kernel Device Mapper is the LVM (Linux Logical Volume Management) Team's implementation of a minimalistic kernel-space driver that handles volume management, while keeping knowledge of the underlying device layout in user-space. This makes it useful for not only LVM, but EVMS, software raid, and other drivers that create "virtual" block devices. . This package contains the (user-space) shared library for accessing the device-mapper; it allows usage of the device-mapper through a clean, consistent interface (as opposed to through kernel ioctls). Package: lvm2 Version: 2.02.44-4~bpo50+1 Architecture: i386 Maintainer: Debian LVM Team Installed-Size: 900 Depends: libc6 (>= 2.7-1), libdevmapper1.02.1 (>= 2:1.02.30), libreadline5 (>= 5.2), lsb-base Recommends: dmsetup Conflicts: lvm-common Replaces: lvm-common Filename: ./lvm2_2.02.44-4~bpo50+1_i386.deb Size: 364688 MD5sum: 188624b53b845045c27dc5f7a5e884c5 Section: admin Priority: optional Description: The Linux Logical Volume Manager This is LVM2, the rewrite of The Linux Logical Volume Manager. LVM supports enterprise level volume management of disk and disk subsystems by grouping arbitrary disks into volume groups. The total capacity of volume groups can be allocated to logical volumes, which are accessed as regular block devices.