Fix CI badges in README.md and fix dracut description
While fixing the CI badges, I removed some old crufty README text.master
parent
eb770a4a20
commit
871d63c3be
11
README.md
11
README.md
|
@ -4,15 +4,15 @@ dracut
|
||||||
dracut is an event driven initramfs infrastructure.
|
dracut is an event driven initramfs infrastructure.
|
||||||
|
|
||||||
[](https://travis-ci.org/dracutdevs/dracut)
|
[](https://travis-ci.org/dracutdevs/dracut)
|
||||||
[](https://github.com/dracutdevs/dracut/actions?query=workflow%3AFedora-30)
|
|
||||||
[](https://github.com/dracutdevs/dracut/actions?query=workflow%3AFedora-31)
|
[](https://github.com/dracutdevs/dracut/actions?query=workflow%3AFedora-31)
|
||||||
|
[](https://github.com/dracutdevs/dracut/actions?query=workflow%3AFedora-32)
|
||||||
|
|
||||||
dracut (the tool) is used to create an initramfs image by copying tools
|
dracut (the tool) is used to create an initramfs image by copying tools
|
||||||
and files from an installed system and combining it with the
|
and files from an installed system and combining it with the
|
||||||
dracut framework, usually found in /usr/lib/dracut/modules.d.
|
dracut framework, usually found in /usr/lib/dracut/modules.d.
|
||||||
|
|
||||||
Unlike existing initramfs's, this is an attempt at having as little as
|
Unlike other implementations, dracut hard-codes as little
|
||||||
possible hard-coded into the initramfs as possible. The initramfs has
|
as possible into the initramfs. The initramfs has
|
||||||
(basically) one purpose in life -- getting the rootfs mounted so that
|
(basically) one purpose in life -- getting the rootfs mounted so that
|
||||||
we can transition to the real rootfs. This is all driven off of
|
we can transition to the real rootfs. This is all driven off of
|
||||||
device availability. Therefore, instead of scripts hard-coded to do
|
device availability. Therefore, instead of scripts hard-coded to do
|
||||||
|
@ -20,10 +20,7 @@ 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.
|
then when we have the rootfs's device node, we mount and carry on.
|
||||||
This helps to keep the time required in the initramfs as little as
|
This helps to keep the time required in the initramfs as little as
|
||||||
possible so that things like a 5 second boot aren't made impossible as
|
possible so that things like a 5 second boot aren't made impossible as
|
||||||
a result of the very existence of an initramfs. It's likely that
|
a result of the very existence of an initramfs.
|
||||||
we'll grow some hooks for running arbitrary commands in the flow of
|
|
||||||
the script, but it's worth trying to resist the urge as much as we can
|
|
||||||
as hooks are guaranteed to be the path to slow-down.
|
|
||||||
|
|
||||||
Most of the initramfs generation functionality in dracut is provided by a bunch
|
Most of the initramfs generation functionality in dracut is provided by a bunch
|
||||||
of generator modules that are sourced by the main dracut script to install
|
of generator modules that are sourced by the main dracut script to install
|
||||||
|
|
|
@ -99,7 +99,7 @@ Requires: libkcapi-hmaccalc
|
||||||
|
|
||||||
%description
|
%description
|
||||||
dracut contains tools to create bootable initramfses for the Linux
|
dracut contains tools to create bootable initramfses for the Linux
|
||||||
kernel. Unlike previous implementations, dracut hard-codes as little
|
kernel. Unlike other implementations, dracut hard-codes as little
|
||||||
as possible into the initramfs. dracut contains various modules which
|
as possible into the initramfs. dracut contains various modules which
|
||||||
are driven by the event-based udev. Having root on MD, DM, LVM2, LUKS
|
are driven by the event-based udev. Having root on MD, DM, LVM2, LUKS
|
||||||
is supported as well as NFS, iSCSI, NBD, FCoE with the dracut-network
|
is supported as well as NFS, iSCSI, NBD, FCoE with the dracut-network
|
||||||
|
|
Loading…
Reference in New Issue