From Fedora Project Wiki
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 84: | Line 84: | ||
| <references/> | | <references/> | ||
|- | |- | ||
| [[ | | [[royboy626|Ron Humble]] | ||
| {{result|pass}} <ref>Test pass, All Ker Param boots OK. Not yet verify Results 3,4,5,6. Hope to do more.</ref> | | {{result|pass}} <ref>Test pass, All Ker Param boots OK. Not yet verify Results 3,4,5,6. Hope to do more.</ref> | ||
| {{result|fail}} <ref>N/A</ref> | | {{result|fail}} <ref>N/A</ref> | ||
| <references/> | | <references/> | ||
|- | |- | ||
| [[ | | [[zbyszek|Zbyszek Jędrzejewski-Szmek]] | ||
| {{result|warn}} <ref>Output is messy: "Halting...Stopping auditd[ OK ]stemctl):", but the next lines are OK</ref> <ref>Asking for runlevel 1, single, s, S or -s booted into runlevel "unknown" (as reported by {{command|runlevel}}) {{bz|630914}}</ref> | | {{result|warn}} <ref>Output is messy: "Halting...Stopping auditd[ OK ]stemctl):", but the next lines are OK</ref> <ref>Asking for runlevel 1, single, s, S or -s booted into runlevel "unknown" (as reported by {{command|runlevel}}) {{bz|630914}}</ref> | ||
| {{result|warn}} <ref>AD 3: Asking for runlevel 4 or 2 runlevel runlevel is reported as 3</ref> <ref>AD 3: After {{command|init 1}} the old runlevel is still reported (3 or 5)</ref> <ref group="long">AD 12: {{command|service netconsole start}} prints 'Starting netconsole (via systemctl): [OK]', but {{command|systemctl status netconsole}} shows '...exited, status 6/NOTCONFIGURED' and netconsole is really not loaded</ref> <ref>AD 19: corrected a bug in Expected Results</ref> | | {{result|warn}} <ref>AD 3: Asking for runlevel 4 or 2 runlevel runlevel is reported as 3</ref> <ref>AD 3: After {{command|init 1}} the old runlevel is still reported (3 or 5)</ref> <ref group="long">AD 12: {{command|service netconsole start}} prints 'Starting netconsole (via systemctl): [OK]', but {{command|systemctl status netconsole}} shows '...exited, status 6/NOTCONFIGURED' and netconsole is really not loaded</ref> <ref>AD 19: corrected a bug in Expected Results</ref> | ||
| Line 95: | Line 95: | ||
|- | |- | ||
| [[ | | [[urban|Krzysztof Urbaniak]] | ||
| {{result|pass}} <ref>Booting to different runlevels works, (s|S|single) works, changing the default runlevel works.</ref> | | {{result|pass}} <ref>Booting to different runlevels works, (s|S|single) works, changing the default runlevel works.</ref> | ||
| {{result|warn}} <ref>Works almost all, i'll have small issues with telinit 1,2,3,4,5, but its not critical.</ref> | | {{result|warn}} <ref>Works almost all, i'll have small issues with telinit 1,2,3,4,5, but its not critical.</ref> | ||
| Line 106: | Line 106: | ||
|- | |- | ||
| [[ | | [[ac000|Andrew Clayton]] | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|warn}} <ref>telinit has problems as in {{bz|627014}}</ref> <ref> shutdown -k doesn;t work as it should. {{bz|624149#c20}}</ref> | | {{result|warn}} <ref>telinit has problems as in {{bz|627014}}</ref> <ref> shutdown -k doesn;t work as it should. {{bz|624149#c20}}</ref> | ||
| Line 117: | Line 117: | ||
|- | |- | ||
| [[User:Thub|Thub]] | | [[User:Thub|Thub]] | ||
| {{result|warn}} <ref>Runlevel 1 does not update the runlevel reported by "runlevel" command, either at boot or via telinit (reported above). {{bz|630914}}</ref> <ref>Booting to runlevel 3 when firstboot hasn't been run yet results in firstboot and getty trying to use the same tty. {{bz|631584}}</ref> | | {{result|warn}} <ref>Runlevel 1 does not update the runlevel reported by "runlevel" command, either at boot or via telinit (reported above). {{bz|630914}}</ref> | ||
| {{result|fail}} <ref group="long">telinit fails to change runlevels properly (e.g. telinit 5 does not start X unless the system booted to runlevel 5 initially). {{bz|627014}}</ref> <ref>"halt" command: No indication that it has halted. {{bz|631592}}</ref> <ref group="long">"halt -p", "poweroff", and "shutdown -h" commands and their rebooting equivalents, when invoked in runlevel 5, appear to cause gdm to be restarted, rather than stopped. {{bz|631160}}</ref> | <ref>Booting to runlevel 3 when firstboot hasn't been run yet results in firstboot and getty trying to use the same tty. {{bz|631584}}</ref> | ||
| {{result|fail}} <ref group="long">telinit fails to change runlevels properly (e.g. telinit 5 does not start X unless the system booted to runlevel 5 initially). {{bz|627014}}</ref> | |||
<ref>"halt" command: No indication that it has halted. {{bz|631592}}</ref> | |||
<ref group="long">"halt -p", "poweroff", and "shutdown -h" commands and their rebooting equivalents, when invoked in runlevel 5, appear to cause gdm to be restarted, rather than stopped. {{bz|631160}}</ref> | |||
| <references/> | | <references/> | ||
|- | |- | ||
| [[User:jcm|Jon Masters]] | | [[User:jcm|Jon Masters]] | ||
| {{result|warn}} <ref>When booted with "console=tty console=ttyS0" or "console=ttyS0", there is no getty on tty1.</ref> | | {{result|warn}} <ref>When booted with "console=tty console=ttyS0" or "console=ttyS0", there is no getty on tty1.</ref> | ||
| {{result|fail}} <ref group="long">"halt" used to also shut down the system, does not do so any longer (I know this has been discussed, I'm specifically calling it out). Additionally, on current <b>rawhide</b>: (systemd-9-3.fc15.x86_64) the root filesystem always has busy inodes on shutdown and forces a replay of the journal on next boot, lvm2-monitor does not shutdown cleanly on halt, various log entries contain "init[1]: Got invalid poll event on pipe." followed by e.g. "init[1]: Unit sys-kernel-security.automount entered failed state.", and there are several "mount" errors when systemd re-execs itself to apparently try to handle the busy inodes situation. | | {{result|fail}} <ref group="long">"halt" used to also shut down the system, does not do so any longer (I know this has been discussed, I'm specifically calling it out). Additionally, on current <b>rawhide</b>: (systemd-9-3.fc15.x86_64) the root filesystem always has busy inodes on shutdown and forces a replay of the journal on next boot, lvm2-monitor does not shutdown cleanly on halt, various log entries contain "init[1]: Got invalid poll event on pipe." followed by e.g. "init[1]: Unit sys-kernel-security.automount entered failed state.", and there are several "mount" errors when systemd re-execs itself to apparently try to handle the busy inodes situation. | ||
| Some testing on F-14, some on rawhide. Seems to work ok, but there are some behavioral changes. < | | Some testing on F-14, some on rawhide. Seems to work ok, but there are some behavioral changes.</ref> | ||
|- | |- | ||
| [[User:Dramsey|David Ramsey ]] | | [[User:Dramsey|David Ramsey ]] | ||
| Line 141: | Line 144: | ||
<references group="long" /> | <references group="long" /> | ||
[[Category:Fedora 14 Test Days]] | [[Category:Test Days]] [[Category:Fedora 14 Test Days]] | ||