Ubuntu
dracut package

dracut 044+3-2 source package in Ubuntu

Changelog

dracut (044+3-2) unstable; urgency=medium

  [ Ben Hutchings ]
  * Split dracut binary package into core and automation hooks,
    Closes: #808787

 -- Thomas Lange <email address hidden>  Wed, 23 Dec 2015 23:13:50 +0100

Upload details

Uploaded by:
Thomas Lange
Uploaded to:
Sid
Original maintainer:
Thomas Lange
Architectures:
any all
Section:
utils
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
dracut_044+3-2.dsc 2.1 KiB def33d6cbbadbc180c4e291af45f5e485e5fc5ca2af015be0b22d8692bbcdf61
dracut_044+3.orig.tar.xz 247.0 KiB af895ae860cf8aa1c0a77dde54f9271991ceb5f7e7664a1adc479be9c4565c9b
dracut_044+3-2.debian.tar.xz 9.5 KiB c80c0874e0b8214459f23b006f7737ec3ce0675986f178e568e1360f54633b04

Available diffs

No changes file available.

Binary packages built by this source

dracut: Low-level tool for generating an initramfs image (automation)

 This package builds a bootable initramfs for Linux kernel packages. The
 initramfs is loaded along with the kernel and is responsible for
 mounting the root filesystem and starting the main init system.

dracut-config-generic: Low-level tool for generating an initramfs image

 This is the dracut configuration to turn off hostonly image generation

dracut-config-rescue: Low-level tool for generating an initramfs image

 This is the dracut configuration to turn on rescue image generation

dracut-core: Low-level tool for generating an initramfs image (core tools)

 Unlike existing initramfs's, this is an attempt at having as little as
 possible hard-coded into the initramfs as possible. The initramfs has
 (basically) one purpose in life -- getting the rootfs mounted so that
 we can transition to the real rootfs. This is all driven off of
 device availability. Therefore, instead of scripts hard-coded to do
 various things, we depend on udev to create device nodes for us and
 then when we have the rootfs's device node, we mount and carry on.
 Having the root on MD, LVM2, LUKS is supported as well as NFS, iSCSI,
 NBD and FCOE with dracut-network.

dracut-core-dbgsym: debug symbols for package dracut-core

 Unlike existing initramfs's, this is an attempt at having as little as
 possible hard-coded into the initramfs as possible. The initramfs has
 (basically) one purpose in life -- getting the rootfs mounted so that
 we can transition to the real rootfs. This is all driven off of
 device availability. Therefore, instead of scripts hard-coded to do
 various things, we depend on udev to create device nodes for us and
 then when we have the rootfs's device node, we mount and carry on.
 Having the root on MD, LVM2, LUKS is supported as well as NFS, iSCSI,
 NBD and FCOE with dracut-network.

dracut-network: Low-level tool for generating an initramfs image

 Unlike existing initramfs's, this is an attempt at having as little as
 possible hard-coded into the initramfs as possible. The initramfs has
 (basically) one purpose in life -- getting the rootfs mounted so that
 we can transition to the real rootfs. This is all driven off of
 device availability. Therefore, instead of scripts hard-coded to do
 various things, we depend on udev to create device nodes for us and
 then when we have the rootfs's device node, we mount and carry on.
 Having the root on MD, LVM2, LUKS is supported as well as NFS, iSCSI,
 NBD and FCOE with dracut-network.