From Fedora Project Wiki

Reporting Problems

Before filing a bug, please read up on BugReporting, which will tell you how to fill out useful bug reports that will help us quickly solve your problem. Also try searching bugzilla for other reports about your problem, as some bugs are often filed by several people.

Developers

  1. FIXME

Dracut is primarily written in ....

Developers' Guide

  1. FIXME

If you want to work on Dracut, you should start with ...

Getting the Source

The primary methods of distributing the Dracut source are source RPMs in the Fedora development tree and git. To access the current source code in in non-rpm format, you'll need to install git.

yum install git

Note that several related packages will be installed as well. After the git source code management tool has been installed, then you use anonymous git access to the Dracut repository.

git clone git://dracut.git.sourceforge.net/gitroot/dracut

If you have committer access to Dracut, then you will want to use the git+ssh access url. #FIXME

git clone git+ssh://dracut.git.sourceforge.net/gitroot/dracut #FIXME
git clone git://dracut.git.sourceforge.net/gitroot/dracut #FIXME

Once you've committed changes locally, you can push them with

git push

If you would just like to browse the Dracut git repository via the web, then please use one of the following Dracut git URLs .

Summary Shortlog Log Commit CommitDiff

Dracut Team

In alphabetical order, the following people are the anaconda team and are responsible for the majority of commits. Of course, we get help from other people both from Red Hat and from the volunteer community as well.

Debugging

Template:Admon/not

rdinitdebug
Note.png
set -x for the dracut shell
rdbreak=[pre-udev|pre-mount|mount|pre-pivot|]
Note.png
drop the shell on defined breakpoint
rdudevinfo
Note.png
set udev to loglevel info
dudevdebug
Note.png
set udev to loglevel debug
rdnetdebug
Note.png
debug network scripts in dracut