Ubuntu
dracut package

dracut 005-1 source package in Ubuntu

Changelog

dracut (005-1) unstable; urgency=low

  * Version 005
  * First dracut release to unstable. Closes: #558274

dracut (004-1) unreleased; urgency=low

  * Version 004

dracut (003-1) unreleased; urgency=low

  * Version 003

dracut (002-1) unreleased; urgency=low

  * Version 002
 -- Ubuntu Archive Auto-Sync <email address hidden>   Tue,  25 May 2010 15:15:25 +0100

Upload details

Uploaded by:
Ubuntu Archive Auto-Sync
Uploaded to:
Maverick
Original maintainer:
Philippe Seewer
Architectures:
all
Section:
utils
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Maverick: [FULLYBUILT] i386

Downloads

File Size SHA-256 Checksum
dracut_005.orig.tar.bz2 85.5 KiB 36fe872e412de1587dc2f881f86ce4e64b77d1c3250a51c954346767372ce61a
dracut_005-1.debian.tar.gz 2.5 KiB ef9b838e1ae963b0dbfff23daf96ad1bad64317f3c400ca2cb6a20323b1bd772
dracut_005-1.dsc 1.1 KiB 53e22798c9d5ecf5bc665247068857badf2b2ae8e60ec3252d03f5ef9ce2f7d0

View changes file

Binary packages built by this source

dracut: A new initramfs infrastructure

 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: A new initramfs infrastucture

 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.