Bug 627474

Summary:	Document systemd "runlevel" change in /etc/inittab
Product:	[Fedora] Fedora	Reporter:	Rahul Sundaram <metherid>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	awilliam, horsley1953, iarlyy, initscripts-maint-list, jonathan, lnykryn, notting, plautrba, rvokal
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	initscripts-9.45-1.fc19	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-15 14:41:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Rahul Sundaram 2010-08-26 06:49:55 UTC

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

Comment 1 Matthias Clasen 2010-08-26 17:54:14 UTC

*** Bug 627429 has been marked as a duplicate of this bug. ***

Comment 2 Petr Lautrbach 2010-09-07 08:18:28 UTC

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

Comment 3 Bill Nottingham 2010-09-07 17:08:29 UTC

Right, that's intentional if we're supporting both in a single package.

Comment 4 Adam Williamson 2011-05-17 06:22:11 UTC

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

Comment 5 Adam Williamson 2011-05-17 06:23:45 UTC

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

Comment 6 Bill Nottingham 2011-05-17 18:01:56 UTC

This would be some pretty horrible macro-ization in the spec, but doable. (Which inittab you get depends on buildflags in the package.)

Comment 7 Lukáš Nykrýn 2013-03-14 12:15:24 UTC

Currently it is quite improbable that someone uses anything else that systemd in fedora, so I remove config flag from this file.