Source: yaird
Section: utils
Priority: optional
Build-Depends: debhelper (>= 5.0.44), quilt, patchutils (>= 0.2.25), dh-buildinfo, devscripts (>= 2.10.7), cdbs (>= 0.4.39), xmlto
Maintainer: Yaird Team <yaird-devel@lists.alioth.debian.org>
Uploaders: Jonas Smedegaard <dr@jones.dk>
Vcs-Git: git://git.debian.org/git/collab-maint/yaird.git
Vcs-Browser: http://git.debian.org/?p=collab-maint/yaird.git;a=summary
Standards-Version: 3.7.3
Homepage: http://yaird.alioth.debian.org/

Package: yaird
Architecture: i386 powerpc amd64 arm armel alpha sparc
Depends: ${shlibs:Depends}, ${perl:Depends}, libhtml-template-perl, dash, libparse-recdescent-perl, cpio
Suggests: doc-base
Provides: linux-initramfs-tool
Description: Yet Another mkInitRD
 Yaird generates initial boot images in initramfs format.
 .
 The boot image is an intermediate step between the boot loader (eg.
 Grub, Lilo) and the init scripts on the root file system; it loads
 modules and enables devices to a level where the kernel can access the
 real root file system, and then hands over control to the init scripts.
 .
 Main features:
  - Strict build logic: Less risk of producing non-booting ramdisks
  - Small ramdisks: Optimized for the currently running system
 .
 Main shortcomings:
  - No automatic firmware loading (some SCSI drivers needs manual work)
  - Limited support for encrypted disks (enable manually in config)
  - Produced ramdisks cannot boot into a different system setup!
 .
 Yaird is good for stable systems, like servers (especially if managed
 remotely) and embedded systems.
 .
 If you need a flexible ramdisk tool, then use initramfs-tools instead.
 .
 See http://wiki.debian.org/InitrdReplacementOptions for status and
 comparison with other ramdisk tools.