1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
Source: yaird
Section: utils
Priority: optional
Build-Depends: cdbs (>= 0.4.23-1.1), debhelper (>= 4.2.0), quilt, patchutils (>= 0.2.25), cdbs (>= 0.4.27-1), dh-buildinfo, xmlto
Maintainer: Yaird Team <yaird-devel@lists.alioth.debian.org>
Uploaders: Jonas Smedegaard <dr@jones.dk>
Standards-Version: 3.7.2
Package: yaird
Architecture: any
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.
.
Compared with earlier implementations like mkinitrd, it does a
better job of deciding which modules are needed for your system,
so it produces smaller images and there is less risk of making
an image that will not boot. This comes at a price:
only Linux 2.6 is supported (because 2.6 has sysfs, which makes
it a lot easier to do a hardware inventory).
.
See mkinitrd.yaird(8) for how to activate the program.
.
See http://wiki.debian.org/InitrdReplacementOptions for status and
comparison with other ramdisk tools.
.
Homepage: http://yaird.alioth.debian.org/
|
