Ubuntu
dracut package

dracut 044+3-1 source package in Ubuntu

Changelog

dracut (044+3-1) unstable; urgency=low

  * new upstream, Closes: #802823
  * new patch libdir, multipath Closes: #796329
  * fix plymouth path and remove items, Closes: #796110
  * dracut.install: add dracut-init.sh
  * aufs-mount.sh: use getargbool

 -- Thomas Lange <email address hidden>  Sun, 29 Nov 2015 13:49:04 +0100

Upload details

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

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
dracut_044+3-1.dsc 2.0 KiB 9f5fcf04f9c93e15b9e04faa06d983743be0f5f016636384c4c53960afc58391
dracut_044+3.orig.tar.xz 247.0 KiB af895ae860cf8aa1c0a77dde54f9271991ceb5f7e7664a1adc479be9c4565c9b
dracut_044+3-1.debian.tar.xz 9.3 KiB afdb4ed546f0dfa8209f6f1ce9989d0ea4bae99f2fadef3ac4d6697e191a5b0f

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-dbgsym: No summary available for dracut-dbgsym in ubuntu xenial.

No description available for dracut-dbgsym in ubuntu xenial.

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.