Description of problem: If we decide to go ahead with systemd for Fedora 14 and obsolete upstart, please ensure that /etc/inittab documents how to switch between targets http://www.freedesktop.org/wiki/Software/systemd/FrequentlyAskedQuestions
*** Bug 627429 has been marked as a duplicate of this bug. ***
Should be fixed by http://git.fedorahosted.org/git/?p=initscripts.git;a=commit;h=ea632a2bedadb6114aa15b3479eecfa84b4fd26e /etc/inittab is created from /etc/inittab.systemd but then it's overwritten by /etc/inittab.upstart because of: %define _with_upstart 1 %define _with_systemd 1
Right, that's intentional if we're supporting both in a single package.
Re-opening this because I noticed an issue. The updated /etc/inittab, which explains that the file is no longer any use, gets installed as /etc/inittab.rpmnew when you upgrade from F14 to F15. This doesn't make a great deal of sense; .rpmnew files make sense when you want to ensure that customizations to the file don't lost, but since the file is now a no-op anyway, there's no point keeping the old version whatever anyone's put in it. It should be marked such that it overwrites the old file even if the user has changed it, so that people will be sure to see the instructions it now contains. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
in fact it may as well simply be marked as a regular file, not a config file, any more. you can't put any configuration in it. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This would be some pretty horrible macro-ization in the spec, but doable. (Which inittab you get depends on buildflags in the package.)
Currently it is quite improbable that someone uses anything else that systemd in fedora, so I remove config flag from this file.