Test Day:2010-09-07 Systemd

What to test?
Today's installment of Fedora Test Day will focus on systemd, the new initialization system being introduced in Fedora 14.

Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion...
 * Development - Lennart Poettering (mezcalero)
 * Quality Assurance - Adam Williamson (adamw)

What's needed to test

 * An updated pre-release, or the special live image (see below)
 * Not-yet-published updates for systemd, initscripts, dbus, ConsoleKit and acpid (see below for details)

Update your machine
If you're running Fedora 14, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:

Live image
Optionally, you may download a non-destructive live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

This custom live image contains all the necessary updated packages. You will not be able to conduct the full range of tests using the live CD, but you can perform the tests that are possible, and confirm that it boots correctly on your system. You can also use it to install a Fedora 14 system to perform the full range of tests.

Install additional updates
To provide the best test results, please install the following packages. They have not yet been accepted as official Fedora 14 updates, but they fix several known issues with systemd. If you test with or install from the custom live image linked to above, these updates will already be installed.

From koji:
 * systemd-9-3.fc14
 * initscripts-9.19-1.fc14
 * dbus-1.4.0-1.fc14
 * ConsoleKit-0.4.2-1.fc14
 * acpid-2.0.5-2.1.fc14 - i686, x86_64

Test
Follow each of these test cases:


 * QA:Testcase_initialization_basic
 * QA:Testcase_initialization_tools

Test Results
If you have problems with any of the tests, report a bug to Bugzilla usually for the component systemd. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, if your system worked correctly, simply enter the word PASS. If you had trouble, enter the word FAIL, with a footnote indicator, and put a link to the bug report in the References column (as in the example line). For tests you could not perform, enter a dash.