Features/Dracut

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Current status)
(Current status)
 
(12 intermediate revisions by 2 users not shown)
Line 11: Line 11:
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/12 | 12 ]]  
+
* Targeted release: [[Releases/12 | Fedora 12 ]]  
* Last updated: 2009-06-19
+
* Last updated: 2009-08-19
* Percentage of completion: 85%
+
* Percentage of completion: 100%
  
Package currently under review:
+
Working:
https://bugzilla.redhat.com/show_bug.cgi?id=506939
+
 
 +
* 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 26: Line 37:
 
== Scope ==
 
== Scope ==
 
All functionality of nash/mkinitrd has to be implemented and tested in dracut.
 
All functionality of nash/mkinitrd has to be implemented and tested in dracut.
Still missing is netboot (also from iscsi) and proper raid support.
 
  
 
== 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.
 
 
A good "how to test" should answer these four questions:
 
  
0. What special hardware / data / etc. is needed (if any)?
+
* See also: [[Dracut]]
1. How do I prepare my system to test this feature? What packages
+
* See also: [[Dracut/Testing]]
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 ==

Latest revision as of 16:36, 3 September 2009

Contents

[edit] Dracut

[edit] Summary

Dracut is a replacement for nash/mkinitrd.

[edit] Owner

  • email: harald@redhat.com

[edit] 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)

[edit] Detailed Description

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

See also: Dracut

[edit] Benefit to Fedora

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

[edit] Scope

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

[edit] How To Test

[edit] User Experience

Switching root partitions should be more flexible.

[edit] Dependencies

none

[edit] Contingency Plan

Fallback to mkinitrd.

[edit] Documentation

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

[edit] Release Notes

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

[edit] Comments and Discussion