From Fedora Project Wiki
(New page: = Feature Name = Dracut == Summary == Dracut is a replacement for nash/mkinitrd. == Owner == * Name: Harald Hoyer <!-- Include you email address that you can be reached...)
 
 
(24 intermediate revisions by 5 users not shown)
Line 1: Line 1:
= Feature Name =
= Dracut =
Dracut


== Summary ==
== Summary ==
Line 12: Line 11:


== Current status ==
== Current status ==
* Targeted release: [[Releases/12 | 12 ]]  
* Targeted release: [[Releases/12 | Fedora 12 ]]  
* Last updated: (DATE)
* Last updated: 2009-08-19
* Percentage of completion: XX%
* Percentage of completion: 100%


<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
Working:
 
* normal disk with md/dm raid, LVM, crypto
* NFS
* iSCSI
* NBD
* FCoE
 
TODO:
* IPv6 (postponed to post F12)
* multipath (postponed to post F12)


== Detailed Description ==
== Detailed Description ==
Dracut is a generic, modular initramfs generation tool that can be used across various distributions.
Dracut is a generic, modular initramfs generation tool that can be used across various distributions.
See also: [[Dracut]]


== Benefit to Fedora ==
== Benefit to Fedora ==
Line 28: Line 39:


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.


Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
* See also: [[Dracut]]
 
* See also: [[Dracut/Testing]]
A good "how to test" should answer these four questions:
 
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this feature? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the feature is
working like it's supposed to?
3. What are the expected results of those actions?
-->
Use the created initrd on any machine to boot from any root partitions.


== User Experience ==
== User Experience ==
Line 58: Line 58:
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
* Sourceforge Project http://sourceforge.net/projects/dracut/
* Sourceforge Project http://sourceforge.net/projects/dracut/
* git git://dracut.git.sourceforge.net/gitroot/dracut
* git [http://dracut.git.sourceforge.net/ git://dracut.git.sourceforge.net/gitroot/dracut]
* Trac Instance: http://apps.sourceforge.net/trac/dracut/  
* Trac Instance: http://apps.sourceforge.net/trac/dracut/  
* Mailing List: initramfs@vger.kernel.org  
* Mailing List: initramfs@vger.kernel.org  
LWN article: http://lwn.net/Articles/317793/


== Release Notes ==
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
*  
* mkinitrd/nash has been replaced by dracut, which uses standard tools and scripts to boot from the root partition.


== Comments and Discussion ==
== Comments and Discussion ==
* See [[Talk:Features/YourFeatureName]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
* See [[Talk:Features/Dracut]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->




[[Category:FeaturePageIncomplete]]
[[Category:FeatureAcceptedF12]]
<!-- When your feature page is completed and ready for review -->
<!-- When your feature page is completed and ready for review -->
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
Line 77: Line 79:
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->


[[Category:Features needing QA approval]]
 
<!-- Note that the current Feature guidelines require useful Scope and Test Plans at certain milestones; QA is responsible for checking these, and will change this category as needed. -->
<!-- Note that the current Feature guidelines require useful Scope and Test Plans at certain milestones; QA is responsible for checking these, and will change this category as needed. -->

Latest revision as of 16:36, 3 September 2009

Dracut

Summary

Dracut is a replacement for nash/mkinitrd.

Owner

  • email: harald@redhat.com

Current status

  • Targeted release: Fedora 12
  • Last updated: 2009-08-19
  • Percentage of completion: 100%

Working:

  • normal disk with md/dm raid, LVM, crypto
  • NFS
  • iSCSI
  • NBD
  • FCoE

TODO:

  • IPv6 (postponed to post F12)
  • multipath (postponed to post F12)

Detailed Description

Dracut is a generic, modular initramfs generation tool that can be used across various distributions.

See also: Dracut

Benefit to Fedora

Replace nash/mkinitrd with a tool, that is maintained by a cross distribution community.

Scope

All functionality of nash/mkinitrd has to be implemented and tested in dracut.

How To Test

User Experience

Switching root partitions should be more flexible.

Dependencies

none

Contingency Plan

Fallback to mkinitrd.

Documentation

LWN article: http://lwn.net/Articles/317793/

Release Notes

  • mkinitrd/nash has been replaced by dracut, which uses standard tools and scripts to boot from the root partition.

Comments and Discussion


Retrieved from "https://fedoraproject.org/w/index.php?title=Features/Dracut&oldid=122390"