Re: initdefault has no effect
- From: Ed Greshko <Ed.Greshko@xxxxxxxxxxx>
- Date: Tue, 07 Apr 2009 09:37:12 +0800
Ed Greshko wrote:
Mike Burger wrote:Never mind..... I see what you are saying after all.... I forgot for
Mike Burger wrote:I don't quite understand what you are saying....
Tim wrote:To clarify...the reason that this didn't work, in the first place, is
On Sun, 2009-04-05 at 22:42 -0700, Jonathan Ryshpan wrote:In order to comment out a line in inttab, you need to use a
I have /etc/inittab set up as follows, but the system always starts
with the X Window System running. What am I missing?
# id:5:initdefault:I seem to recall seeing that before, delete the commented-out line.
semicolon, rather than a pound sign.
that the initial initdefault line wasn't truly commented out, due to
the pound sign instead of the semicolon.
After that, the init processing for an entry stops on the first
match...since the "not properly commented" entry was first, it got
matched, and runlevel 5 was how the system came up.
You said "the init processing for an entry stops on the first match".
What is being matched to what? Also, if the # isn't a comment character
then how are the other 25 lines in the inittab being parsed?
the moment that the original id line was left in the modified file....
Is it a right to remain ignorant? -- Calvin Mei-Mei.Greshko@xxxxxxxxxxx
Description: OpenPGP digital signature
fedora-list mailing list
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
- Prev by Date: Re: initdefault has no effect
- Next by Date: Re: System time 1 hr ahead of real time
- Previous by thread: Re: initdefault has no effect
- Next by thread: Re: initdefault has no effect