From Fedora Project Wiki
(Created page with '{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To rea...')
 
No edit summary
Line 5: Line 5:
{{admon/note | All sections of this template are required for review by FESCo.  If any sections are empty it will not be reviewed }}
{{admon/note | All sections of this template are required for review by FESCo.  If any sections are empty it will not be reviewed }}


= SysV to Systemd =


<!-- All fields on this form are required to be accepted by FESCo.
== Summary ==
We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
 
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
 
= Feature Name <!-- The name of your feature --> =


== Summary ==
Porting from sysVinit init scripts to systemd unit file.
<!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. -->


== Owner ==
== Owner ==
<!--This should link to your home wiki page so we know who you are-->
* Name: [[User:FASAcountName| Your Name]]


<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
* Name: [[User:Johannbg| Jóhann B. Guðmundsson]] ; [[User:Lennart | Lennart Poettering]]
* Email: <your email address so we can contact you, invite you to meetings, etc.>
* Email: johannbg AT gmail DOT com ; lpoetter AT redhat DOT com


== Current status ==
== Current status ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
* Targeted release: [[Releases/Fedora <number> | Fedora <number> ]]  
* Last updated: (DATE)
* Last updated:  
* Percentage of completion: XX%
* Percentage of completion: 0


<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
== Detailed Description ==


== Detailed Description ==
coordination to ensure the best user experience. The best case is that all services which have shipped with system v init scripts in the past are upgraded to have systemd unit files in one Fedora release. The next best thing would be for individual services to transition to unit files only in the lead up to a new release. Today the FPC passed a clarification to have a warning about the latter put into the guidelines. This ticket is to find out what can be done about the former. Could we have a FES ticket to get people to work on this for F16? Is there another way to coordinate this?
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. -->


== Benefit to Fedora ==
== Benefit to Fedora ==

Revision as of 19:10, 18 May 2011

Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.
Important.png
Set a Page Watch
Make sure you click watch on your new page so that you are notified of changes to it by others, including the Feature Wrangler
Note.png
All sections of this template are required for review by FESCo. If any sections are empty it will not be reviewed

SysV to Systemd

Summary

Porting from sysVinit init scripts to systemd unit file.

Owner

Current status

  • Targeted release: [[Releases/Fedora <number> | Fedora <number> ]]
  • Last updated:
  • Percentage of completion: 0

Detailed Description

coordination to ensure the best user experience. The best case is that all services which have shipped with system v init scripts in the past are upgraded to have systemd unit files in one Fedora release. The next best thing would be for individual services to transition to unit files only in the lead up to a new release. Today the FPC passed a clarification to have a warning about the latter put into the guidelines. This ticket is to find out what can be done about the former. Could we have a FES ticket to get people to work on this for F16? Is there another way to coordinate this?

Benefit to Fedora

Scope

How To Test

User Experience

Dependencies

Contingency Plan

Documentation

Release Notes

Comments and Discussion