mirror of
https://github.com/dracutdevs/dracut.git
synced 2024-10-27 00:55:34 +03:00
0ac9584ded
Provided that you are configuring them via DHCP. RARP, BOOTP, and static configuration are not written yet. Also, adding nic drivers really bloats the initrd. I am looking for feedback on these patches from people who actually implement booting over the network. This patch series does not include support for that yet -- you will not find nfsroot= handling, or booting to a fs supplied by dhcp yet. I do want to make it as easy as possible to add support for booting over the network, as well as making it easy for people to customize things to meet their site requirements. This patch series is also available as the network-configurability branch at http://git.fnordovax.org/dracut. It may be rebased without warning to keep it in sync with the rest of dracut.
63 lines
3.3 KiB
Plaintext
63 lines
3.3 KiB
Plaintext
Dracut
|
|
------
|
|
|
|
This is the simple skeleton of a new initramfs infrastructure.
|
|
Information about our goals and aims can be found at
|
|
https://fedoraproject.org/wiki/Initrdrewrite
|
|
|
|
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.
|
|
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
|
|
a result of the very existence of an initramfs. It's likely that
|
|
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 initrd generation functionality in dracut is provided by a bunch
|
|
of generator modules that are sourced by the main dracut script to install
|
|
specific functionality into the initrd. They live in the modules subdirectory,
|
|
and use functionality provided by dracut-functions to do their work.
|
|
Some general rules for writing modules:
|
|
* Use one of the inst family of functions to actually install files
|
|
on to the initrd. They handle mangling the pathnames and (for binaries,
|
|
scripts, and kernel modules) installing dependencies as appropriate so
|
|
you do not have to.
|
|
* Scripts that end up on the initrd should be POSIX compliant. dracut
|
|
will try to use /bin/dash as /bin/sh for the initrd if it is available,
|
|
so you should install it on your system -- dash aims for strict POSIX
|
|
compliance to the extent possible.
|
|
* Hooks MUST be POSIX compliant -- they are sourced by the init script,
|
|
and having a bashism break your user's ability to boot really sucks.
|
|
* Generator modules should have a two digit numeric prefix -- they run in
|
|
ascending sort order. Anything in the 90-99 range is stuff that dracut
|
|
relies on, so try not to break those hooks.
|
|
* Generator modules and hooks must have a .sh extension.
|
|
* We have some breakpoints for debugging your hooks. If you pass 'break'
|
|
as a kernel parameter, the initramfs will drop to a shell just before
|
|
switching to a new root. You can pass 'break=hookpoint', and the initramfs
|
|
will break just before hooks in that hookpoint run.
|
|
|
|
Also, there is an attempt to keep things as distribution-agnostic as
|
|
possible. Every distribution has their own tool here and it's not
|
|
something which is really interesting to have separate across them.
|
|
So contributions to help decrease the distro-dependencies are welcome.
|
|
|
|
The git tree can be found at
|
|
git://fedorapeople.org/~katzj/dracut.git for now. See the TODO
|
|
file for things which still need to be done and HACKING for some
|
|
instructions on how to get started. There is also a mailing list that
|
|
is being used for the discussion -- initramfs@vger.kernel.org. It is
|
|
a typical vger list, send mail to majordomo@vger.kernel.org with body
|
|
of 'subscribe initramfs email@host.com'
|
|
|
|
|
|
Licensed under the GPLv2
|
|
|
|
Copyright 2008, Red Hat, Inc. -- Jeremy Katz <katzj@redhat.com>
|