dracut 044+3-3 source package in Ubuntu

Changelog

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

  * add dracut.maintscript, so the duplicate logrotate entry is removed

 -- Thomas Lange <email address hidden>  Fri, 15 Jan 2016 02:37:08 +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
Xenial release universe utils

Downloads

File Size SHA-256 Checksum
dracut_044+3-3.dsc 2.1 KiB 1ad0b82f49cee03cebe55278722a5410c256b44055ed2b2f692bbf14f0331237
dracut_044+3.orig.tar.xz 247.0 KiB af895ae860cf8aa1c0a77dde54f9271991ceb5f7e7664a1adc479be9c4565c9b
dracut_044+3-3.debian.tar.xz 9.6 KiB 4f40101e47eafb0c074b08a86d9a23351166df88462e2ac214109f75b8fcc528

Available diffs

No changes file available.

Binary packages built by this source

dracut: No summary available for dracut in ubuntu yakkety.

No description available for dracut in ubuntu yakkety.

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.