Re: Dracut -- Cross distribution initramfs infrastructure

[Bernhard Walle <bwalle@suse.de>]

* Seewer Philippe [2008-12-19 08:41]:
>
> Hannes Reinecke wrote:
> [snip]
> > If anyone is interested I can give a short overview of it.
> Please do so, would be appreciated.

A good start is the manual page in section 5:
http://git.opensuse.org/?p=projects/mkinitrd.git;a=blob_plain;f=man/mkinitrd.5.txt;hb=7583c3cc047edc3e8f1a06e8b7925bd27ac0228c

(The git.kernel.org and the opensuse.org repos are basically the same,
we just switched to opensuse.org after the internal maintainership has
been transferred from Hannes to myself because it was easier to add
new users there. The opensuse.org git repo site didn't exist when the
kernel.org mkinitrd repo was created.)

Anyway:

The basic idea is to have most stuff not in the main 'mkinitrd' script
but in modules. Each module has (normally) a setup script part that is
executed when the initrd is created, and a boot part that is executed
when the initrd is running. For example, NFS root is in the 'nfs-util'
package, not in 'mkinitrd'. Same for iSCSI. Or the kdump part is
not in the main mkinitrd but in our 'kdump' package [1]. So the main
initrd  package is quite small but still very flexible.

It's also flexible enough to use Busybox as module that resides in the
'busybox' package and can then be enabled with -F busybox (feature)
when building the initrd.

Only documentation is at the current time a bit weak, one has to fiddle
some stuff from the sources when writing new modules. But that's easy
to fix. :-)

Hannes may explain more ...



    Bernhard

[1] hg clone http://freehg.org/u/bwalle/kdump/