Re: initdefault has no effect
> Mike Burger wrote: > >> Ubuntu (the distro in which I believe upstart to have been started) has >> done away with the inittab, altogether, in favor of another script in >> their /etc/events.d (their equivalent of Fedora's /etc/event.d) >> directory >> that determines default runlevel. Maybe Fedora needs to consider the >> same? > > this is interesting and brings a question, are you saying that ubuntu and > fedora use /etc/event.d/ instead of inittab or just ubuntu? >From what I've read, Ubuntu does not use the inittab, at all...doesn't even include one. > ria, i *replaced* 'id:5:initdefault:' with 'id:3:initdefault:' in inittab > and > made no changes in /etc/event.d/, and i boot level 3 with no problems. Not surprising...the underlying issue, for us using Fedora, is that the Upstart script that reads the inittab does not distinguish between lines with comment delimiters and lines without. Having just the single line would work, as expected. -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org To be notified of updates to the web site, visit: https://www.bubbanfriends.org/mailman/listinfo/site-update or send a blank email message to: site-update-subscr...@bubbanfriends.org -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
On Sun, 2009-04-12 at 15:30 -0700, Jonathan Ryshpan wrote: > (1) What am I trying to do? > Install the proprietary nvidia drivers for my video card. Nvidia > advises that the X Window System be stopped during installation. This > can be done in either runlevel 1 or 3. Level 3 is better, but since > networking is off, it doesn't matter that security is nonexistent. Generally speaking, it's better NOT to install the drivers supplied by NVidia themselves, but use ones packaged PROPERLY for Fedora, from one of the Fedora repos. None of this malarkey is required, and they don't mess up X like NVidia does. Unless you actually have a problem with the Fedora package, I'd strongly advise that you run away, as fast as you can, from using the run file that you can download from NVidia. Set up your computer to use the rpmfusion repo. http://rpmfusion.org/Configuration http://rpmfusion.org/Howto/nVidia -- [...@localhost ~]$ uname -r 2.6.27.21-78.2.41.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
On Sun, 2009-04-05 at 22:42 -0700, Jonathan Ryshpan wrote: > I have /etc/inittab set up as follows, but the system always starts with > the X Window System running. What am I missing? > ... > # Default runlevel. The runlevels used are: > # 0 - halt (Do NOT set initdefault to this) > # 1 - Single user mode > # 2 - Multiuser, without NFS (The same as 3, if you do not have networking) > # 3 - Full multiuser mode > # 4 - unused > # 5 - X11 > # 6 - reboot (Do NOT set initdefault to this) > # > # id:5:initdefault: > id:1:initdefault: Sorry to take so long to reply. I haven't looked at this thread for a while. Comments: (1) What am I trying to do? Install the proprietary nvidia drivers for my video card. Nvidia advises that the X Window System be stopped during installation. This can be done in either runlevel 1 or 3. Level 3 is better, but since networking is off, it doesn't matter that security is nonexistent. (2) What's going on here? Fedora uses the new upstart initialization system. It looks like the only use that upstart makes of /etc/inittab is to awk it for a line looking like id:5:initdefault: No attention paid to comments or whatever. See the files /etc/event.d/rcS* . (3) Is this a bug? I think it is, as long as /etc/inittab contains what look like comments advising how to edit it, and these comments say nothing about it being impossible to comment out an "initdefault" line. (4) What's the best cure? Get rid of /etc/inittab, except possibly for a comment saying to edit the appropriate file(s) in /etc/event.d . I'd put in a special file containing nothing but the initdefault level, and maybe a comment, since the level seems to be referred to in more than one place. Say something like: $ cat /etc/event.d/initdefault # Default runlevel. The runlevels used are: # 0 - halt (Do NOT set initdefault to this) # 1 - Single user mode # 2 - Multiuser, without NFS (The same as 3, if you do not have networking) # 3 - Full multiuser mode # 4 - unused # 5 - X11 # 6 - reboot (Do NOT set initdefault to this) # id:5:initdefault: Also edit the awk scripts accessing this file to pay attention to comments. And edit /etc/inittab to read something like: This file is obselete and will eventually be removed from the Fedora distribution. See /etc/event.d and other files in the upstart rpm for information about system initialization. In particular use /etc/event.d/initdefault to set the initial runlevel. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Kevin Kofler wrote: > Just Ubuntu. ok. just wanted to be clear and sure something was not wrong with my f10 install. :) -- peace out. tc,hago. g . in a free world without fences, who needs gates. ** help microsoft stamp out piracy - give linux to a friend today ** to mess up a linux box, you need to work at it; to mess up an ms windows box, you just need to *look at* it. ** learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html 'The Linux Documentation Project' http://www.tldp.org/ 'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html 'HowtoForge' http://howtoforge.com/ 'fedora faqs' http://www.fedorafaq.org/ signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Aaron Konstam wrote: > Well it exists in F9 at least. Are you saying it is not used? existence and usage are 2 different things. what i said is that in version of f10 that i have installed, i changed from level 5 to level 3 via inittab. -- peace out. tc,hago. g . in a free world without fences, who needs gates. ** help microsoft stamp out piracy - give linux to a friend today ** to mess up a linux box, you need to work at it; to mess up an ms windows box, you just need to *look at* it. ** learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html 'The Linux Documentation Project' http://www.tldp.org/ 'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html 'HowtoForge' http://howtoforge.com/ 'fedora faqs' http://www.fedorafaq.org/ signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Aaron Konstam wrote: > Well it exists in F9 at least. Are you saying it is not used? It's used for event scripts. But the default runlevel is set in /etc/inittab, not in a script in /etc/event.d, whereas Ubuntu does the latter. To be more precise, Fedora's /etc/event.d/rcS script reads the runlevel from /etc/inittab, whereas in Ubuntu you'd edit the script directly to set your runlevel. Kevin Kofler -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
On Fri, 2009-04-10 at 01:50 +0200, Kevin Kofler wrote: > g wrote: > > this is interesting and brings a question, are you saying that ubuntu and > > fedora use /etc/event.d/ instead of inittab or just ubuntu? > > Just Ubuntu. > > Kevin Kofler > Well it exists in F9 at least. Are you saying it is not used? -- === FACILITY REJECTED 10004420; === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
g wrote: > this is interesting and brings a question, are you saying that ubuntu and > fedora use /etc/event.d/ instead of inittab or just ubuntu? Just Ubuntu. Kevin Kofler -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Mike Burger wrote: > Ubuntu (the distro in which I believe upstart to have been started) has > done away with the inittab, altogether, in favor of another script in > their /etc/events.d (their equivalent of Fedora's /etc/event.d) directory > that determines default runlevel. Maybe Fedora needs to consider the > same? this is interesting and brings a question, are you saying that ubuntu and fedora use /etc/event.d/ instead of inittab or just ubuntu? ria, i *replaced* 'id:5:initdefault:' with 'id:3:initdefault:' in inittab and made no changes in /etc/event.d/, and i boot level 3 with no problems. -- peace out. tc,hago. g . in a free world without fences, who needs gates. ** help microsoft stamp out piracy - give linux to a friend today ** to mess up a linux box, you need to work at it; to mess up an ms windows box, you just need to *look at* it. ** learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html 'The Linux Documentation Project' http://www.tldp.org/ 'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html 'HowtoForge' http://howtoforge.com/ 'fedora faqs' http://www.fedorafaq.org/ signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
2009/4/7 D. Hugh Redelmeier :
> | From: "Sharpe, Sam J"
>
> | runlevel=$(/bin/awk -F ':' '($3 == "initdefault") && ($1 !~ /(#|;)/) {
> print $2 }' /etc/inittab)
>
> Probably you meant ($1 !~ /^(#|;)/)
Actually I didn't - hence my comment:
> I've assumed that # and ; are comments and aren't allowed in the runlevel
> descriptions.
# is definitely a comment
; this might be a comment
# I consider a comment - # is the first non-whitespace character
Because It's only matching on $1 and split on colons, then the only
conceivable bad match would be something like:
id#:5:initdefault:
hence the assumption that # is not allowed in the runlevel descriptions.
--
Sam
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Craig White wrote: On Tue, 2009-04-07 at 12:30 +0800, Ed Greshko wrote: Mike Burger wrote: Ed Greshko wrote: Hummm Bad news I had to test this and have in the intttab file # 5 - X11 # 6 - reboot (Do NOT set initdefault to this) # ; id:5:initdefault: id:3:initdefault: And the system still comes up in run level 5. Yet the fact remains, ; had no more effect than #. If you don't trust the test that I did, you can do it yourself in order to prove it. I've done nothing to study the code but it seems consistent with the way chkconfig also derives the runlevels from the initscripts. It leads to a guess that there is just a quick & dirty type grep for the first result and run with it. In the case of chkconfig, the file it's examining is a shell script, and the parameter lines have to be marked as shell comments. That's not the case with inittab. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Mike Burger wrote: > Fair enough, if that is to be the end product...but if you want to test > something, and don't want to litter the system with dozens of backup > inittab files and the like, commenting a line is quicker than fully > editing it in and out. I don't understand this at all. It's a single character to change. Just do the change. Kevin Kofler -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
| From: "Sharpe, Sam J"
| runlevel=$(/bin/awk -F ':' '($3 == "initdefault") && ($1 !~ /(#|;)/) { print
$2 }' /etc/inittab)
Probably you meant ($1 !~ /^(#|;)/)
Simpler, I think:
runlevel=`/bin/awk -F ':' '/^[^#;]/ && ($3 == "initdefault") { print $2 }'
/etc/inittab`
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
> Mike Burger wrote: >> >> Again...within inittab, the # character is not a comment delimiter...the >> ; >> character is. >> >> Because the # was used, the first default line was matched, therefore >> processing to determine the default runlevel stopped at the first >> match...the line with the 5 in it. >> >> Subsequent lines, which do not contain "initdefault" are processed, >> because they do not match the "initdefault" parameter that was matched >> above. > Strange - I have always been under the impression that both # and ; > work as comment delimiters in inittab. If # is not a comment > delimiter, then all the other comment lines that start with # should > generate syntax errors. As has been noted, it turns out it's nothing to do with the delimiter being used for commenting, after all, but a scripting logic error that ignores the fact that there's a commenting delimiter in place, at all. -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org To be notified of updates to the web site, visit: https://www.bubbanfriends.org/mailman/listinfo/site-update or send a blank email message to: site-update-subscr...@bubbanfriends.org -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Mike Burger wrote: > > Again...within inittab, the # character is not a comment delimiter...the ; > character is. > > Because the # was used, the first default line was matched, therefore > processing to determine the default runlevel stopped at the first > match...the line with the 5 in it. > > Subsequent lines, which do not contain "initdefault" are processed, > because they do not match the "initdefault" parameter that was matched > above. Strange - I have always been under the impression that both # and ; work as comment delimiters in inittab. If # is not a comment delimiter, then all the other comment lines that start with # should generate syntax errors. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Sharpe, Sam J wrote:
Mike Burger wrote:
Tom Horsley wrote:
On Tue, 7 Apr 2009 06:42:36 -0400 (EDT)
Mike Burger wrote:
I'm still doing some digging.
I thought there was a thread on this very topic in a previous
release, but I can't find it (maybe it was in fedora-list
rather than fedora-test-list), anyway it is a very old bug
I'm surprised is still around.
The script in the upstart code that searches /etc/inittab to
find the runlevel was not ignoring commented out lines, so
whatever line it found first, that's the one it grabbed the
runlevel from regardless of the comment prefix.
Bugger.
This *is* the Fedora list, BTW, rather than the fedora-test list.
However, I pop in and out of this list, given the level of traffic and
my availability to monitor and try to answer questions (when I *think*
that I'm actually capable of answering them), based on workload and
travel, so it may be possible that I completely missed that thread,
somewhere.
Since I never really noticed this in F9...the only F9 systems I had
were my laptop and workstation, so I didn't have much reason to
customize)...I had no reason to investigate, either.
If this is a filed bug, and you happen to have the bugzilla report ID,
please forward. I'll also try to dig into it and see if I can find
it, too...I'd like to see this one squashed...or, at the very least,
verify which script it is and see if I can figure out the logic to fix
it.
The script concerned is /etc/event.d/rcS (and /etc/event.d/rcS-sulogin -
both are owned by the initscripts RPM.
They do this:
runlevel=$(/bin/awk -F ':' '$3 == "initdefault" { print $2 }' /etc/inittab)
i.e. they don't ignore the line if $1 contains ; or #
They should probably do something more like:
runlevel=$(/bin/awk -F ':' '($3 == "initdefault") && ($1 !~ /(#|;)/) {
print $2 }' /etc/inittab)
I've assumed that # and ; are comments and aren't allowed in the
runlevel descriptions.
FWIW, Rawhide has initscripts-8.93 which either totally or partially
fixes this bug, depending on how you consider valid comments should be
tagged. If semicolons aren't valid comment indicators and hashes must be
at the beginning of the line, then this (which rawhide does)nis sufficient:
runlevel=$(/bin/awk -F ':' '$3 == "initdefault" && $1 !~ "^#" { print $2
}' /etc/inittab)
So, I guess the only question is whether this is sufficiently serious to
qualify for an updated packages for F10 and F9?
--
Sam
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
On Tue, 07 Apr 2009 08:21:54 -0400 Mike Burger wrote: > However, I pop in and out of this list, given the level of traffic and > my availability to monitor and try to answer questions (when I *think* > that I'm actually capable of answering them), based on workload and > travel, so it may be possible that I completely missed that thread, > somewhere. OK, I found the thread: http://www.redhat.com/archives/fedora-list/2008-June/msg00091.html I don't see anything in that thread that indicates a bugzilla was ever submitted though (just a comment that says one should be submitted :-). -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Mike Burger wrote:
Tom Horsley wrote:
On Tue, 7 Apr 2009 06:42:36 -0400 (EDT)
Mike Burger wrote:
I'm still doing some digging.
I thought there was a thread on this very topic in a previous
release, but I can't find it (maybe it was in fedora-list
rather than fedora-test-list), anyway it is a very old bug
I'm surprised is still around.
The script in the upstart code that searches /etc/inittab to
find the runlevel was not ignoring commented out lines, so
whatever line it found first, that's the one it grabbed the
runlevel from regardless of the comment prefix.
Bugger.
This *is* the Fedora list, BTW, rather than the fedora-test list.
However, I pop in and out of this list, given the level of traffic and
my availability to monitor and try to answer questions (when I *think*
that I'm actually capable of answering them), based on workload and
travel, so it may be possible that I completely missed that thread,
somewhere.
Since I never really noticed this in F9...the only F9 systems I had were
my laptop and workstation, so I didn't have much reason to
customize)...I had no reason to investigate, either.
If this is a filed bug, and you happen to have the bugzilla report ID,
please forward. I'll also try to dig into it and see if I can find it,
too...I'd like to see this one squashed...or, at the very least, verify
which script it is and see if I can figure out the logic to fix it.
The script concerned is /etc/event.d/rcS (and /etc/event.d/rcS-sulogin -
both are owned by the initscripts RPM.
They do this:
runlevel=$(/bin/awk -F ':' '$3 == "initdefault" { print $2 }' /etc/inittab)
i.e. they don't ignore the line if $1 contains ; or #
They should probably do something more like:
runlevel=$(/bin/awk -F ':' '($3 == "initdefault") && ($1 !~ /(#|;)/) {
print $2 }' /etc/inittab)
I've assumed that # and ; are comments and aren't allowed in the
runlevel descriptions.
--
Sam
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
On Tue, 2009-04-07 at 12:30 +0800, Ed Greshko wrote: > Mike Burger wrote: > >> Ed Greshko wrote: > >> > >>> Hummm Bad news > >>> > >>> I had to test this and have in the intttab file > >>> > >>> # 5 - X11 > >>> # 6 - reboot (Do NOT set initdefault to this) > >>> # > >>> ; id:5:initdefault: > >>> id:3:initdefault: > >>> > >>> And the system still comes up in run level 5. > Yet the fact remains, ; had no more effect than #. If you don't trust > the test that I did, you can do it yourself in order to prove it. I've done nothing to study the code but it seems consistent with the way chkconfig also derives the runlevels from the initscripts. It leads to a guess that there is just a quick & dirty type grep for the first result and run with it. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Tom Horsley wrote: On Tue, 7 Apr 2009 06:42:36 -0400 (EDT) Mike Burger wrote: I'm still doing some digging. I thought there was a thread on this very topic in a previous release, but I can't find it (maybe it was in fedora-list rather than fedora-test-list), anyway it is a very old bug I'm surprised is still around. The script in the upstart code that searches /etc/inittab to find the runlevel was not ignoring commented out lines, so whatever line it found first, that's the one it grabbed the runlevel from regardless of the comment prefix. Bugger. This *is* the Fedora list, BTW, rather than the fedora-test list. However, I pop in and out of this list, given the level of traffic and my availability to monitor and try to answer questions (when I *think* that I'm actually capable of answering them), based on workload and travel, so it may be possible that I completely missed that thread, somewhere. Since I never really noticed this in F9...the only F9 systems I had were my laptop and workstation, so I didn't have much reason to customize)...I had no reason to investigate, either. If this is a filed bug, and you happen to have the bugzilla report ID, please forward. I'll also try to dig into it and see if I can find it, too...I'd like to see this one squashed...or, at the very least, verify which script it is and see if I can figure out the logic to fix it. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
On Tue, 7 Apr 2009 06:42:36 -0400 (EDT) Mike Burger wrote: > I'm still doing some digging. I thought there was a thread on this very topic in a previous release, but I can't find it (maybe it was in fedora-list rather than fedora-test-list), anyway it is a very old bug I'm surprised is still around. The script in the upstart code that searches /etc/inittab to find the runlevel was not ignoring commented out lines, so whatever line it found first, that's the one it grabbed the runlevel from regardless of the comment prefix. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
>> Mike Burger wrote: Ed Greshko wrote: > Hummm Bad news > > I had to test this and have in the intttab file > > # 5 - X11 > # 6 - reboot (Do NOT set initdefault to this) > # > ; id:5:initdefault: > id:3:initdefault: > > And the system still comes up in run level 5. > There is probably no comment sign anymore. Upstart just rapidly scans /etc/inittab for the default runlevel and ignores everything else. The only reason the file is still /etc/inittab is for backwards compatibility. So it doesn't use a complete inittab parser, it probably just scans for the first occurrence of id:?:initdefault, completely ignoring any comment signs. >>> >>> While I've not read any upstart documentation to refute your assertion, >>> I >>> do believe that I've commented and uncommented enough since starting >>> with >>> F9 that I am fairly confident that there is, indeed, still the default >>> ; >>> as an inittab comment delimiter. >>> >>> Just don't leave commented lines around. >>> >>> Fair enough, if that is to be the end product...but if you want to test >>> something, and don't want to litter the system with dozens of backup >>> inittab files and the like, commenting a line is quicker than fully >>> editing it in and out. >>> >>> Probably a matter of preference, I would say. >>> >>> >> Kindly be careful with your attributions The comments concerning >> upstart were those of Kevin Kofler. > > Apologies...quite possibly a crop gone awry...your name *was* the one at > the top of the quote/requote/rerequote sequence, but I may have not have > "chopped" low down enough in the chain, or it's possible that my > Thunderbird installation is not properly set up to properly attribute the > most recent quote. > >> Yet the fact remains, ; had no more effect than #. If you don't trust >> the test that I did, you can do it yourself in order to prove it. > > My response, in the message above, was not in response to your test, but > to Kevin's note about not leaving commented lines around. > > While I'm looking at this, though, my earlier assertion that # wouldn't > work as a comment in inittab, at this level, would appear to be incorrect, > as well, given that *all* of the comments at the top of the file start > with a #. > > I'm still doing some digging. At this point, the only other thing I can confirm, after performing Ed's test, and then taking it a step further, is that no amount of commenting seems to matter...the first initdefault line in the inittab is still read to determine the default runlevel. First, I tried it using the method Ed used...comment out the line, and then reinput it with 3 instead of 5, below the commented line. Rebooted, and voila, still in runlevel 5. Next, I moved the commented runlevel 5 line *below* the uncommented runlevel 3 line. Rebooted, and voila, booted up at runlevel 3. All of this bears out both Ed's point that comments don't do anything and my point that upstart's read of the inittab stops on the first match of "initdefault". So, the (temporary?) fix for this situation appears to be that if you're going to comment out one runlevel in order to put in another, insert the new initdefault line *above* the commented "old" initdefault line. On the other hand, this issue may illustrate the need for a bugzilla entry on the issue. Ubuntu (the distro in which I believe upstart to have been started) has done away with the inittab, altogether, in favor of another script in their /etc/events.d (their equivalent of Fedora's /etc/event.d) directory that determines default runlevel. Maybe Fedora needs to consider the same? -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org To be notified of updates to the web site, visit: https://www.bubbanfriends.org/mailman/listinfo/site-update or send a blank email message to: site-update-subscr...@bubbanfriends.org -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
> Mike Burger wrote: >>> Ed Greshko wrote: >>> Hummm Bad news I had to test this and have in the intttab file # 5 - X11 # 6 - reboot (Do NOT set initdefault to this) # ; id:5:initdefault: id:3:initdefault: And the system still comes up in run level 5. >>> There is probably no comment sign anymore. >>> >>> Upstart just rapidly scans /etc/inittab for the default runlevel and >>> ignores >>> everything else. The only reason the file is still /etc/inittab is for >>> backwards compatibility. So it doesn't use a complete inittab parser, >>> it >>> probably just scans for the first occurrence of id:?:initdefault, >>> completely ignoring any comment signs. >>> >> >> While I've not read any upstart documentation to refute your assertion, >> I >> do believe that I've commented and uncommented enough since starting >> with >> F9 that I am fairly confident that there is, indeed, still the default ; >> as an inittab comment delimiter. >> >> >>> Just don't leave commented lines around. >>> >> >> Fair enough, if that is to be the end product...but if you want to test >> something, and don't want to litter the system with dozens of backup >> inittab files and the like, commenting a line is quicker than fully >> editing it in and out. >> >> Probably a matter of preference, I would say. >> >> > Kindly be careful with your attributions The comments concerning > upstart were those of Kevin Kofler. Apologies...quite possibly a crop gone awry...your name *was* the one at the top of the quote/requote/rerequote sequence, but I may have not have "chopped" low down enough in the chain, or it's possible that my Thunderbird installation is not properly set up to properly attribute the most recent quote. > Yet the fact remains, ; had no more effect than #. If you don't trust > the test that I did, you can do it yourself in order to prove it. My response, in the message above, was not in response to your test, but to Kevin's note about not leaving commented lines around. While I'm looking at this, though, my earlier assertion that # wouldn't work as a comment in inittab, at this level, would appear to be incorrect, as well, given that *all* of the comments at the top of the file start with a #. I'm still doing some digging. -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org To be notified of updates to the web site, visit: https://www.bubbanfriends.org/mailman/listinfo/site-update or send a blank email message to: site-update-subscr...@bubbanfriends.org -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Mike Burger wrote: >> Ed Greshko wrote: >> >>> Ed Greshko wrote: >>> >>> Mike Burger wrote: > Mike Burger wrote: > > > >> Tim wrote: >> >> >> >>> On Sun, 2009-04-05 at 22:42 -0700, Jonathan Ryshpan wrote: >>> >>> >>> >>> 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: id:1:initdefault: >>> I seem to recall seeing that before, delete the commented-out line. >>> >>> >>> >>> >> In order to comment out a line in inttab, you need to use a >> semicolon, rather than a pound sign. >> >> >> > To clarify...the reason that this didn't work, in the first place, is > 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. > > > > I don't quite understand what you are saying 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? Thanks >>> Never mind. I see what you are saying after all I forgot for >>> the moment that the original id line was left in the modified file >>> Duh... >>> >>> >>> >> Hummm Bad news >> >> I had to test this and have in the intttab file >> >> # 5 - X11 >> # 6 - reboot (Do NOT set initdefault to this) >> # >> ; id:5:initdefault: >> id:3:initdefault: >> >> And the system still comes up in run level 5. >> > > Interesting. > > Someone once told me to use two semicolons in inittab, but I've never > needed to try that. > And, I too didn't read this before replying to an earlier message... :-) > Might be worth a try. > Maybe...but in the scheme of things this is rather small But simple...so maybe it will be worth it... > On the other hand, since Upstart doesn't use many of the options that used > to be in the inittab, it may be possible that the default runlevel is > actually set in an upstart config file, somewhere, now? > ...yeah...maybe... Will have to wait till I have more time on my hands -- More are taken in by hope than by cunning. -- Vauvenargues mei-mei.gres...@greshko.com http://tw.youtube.com/watch?v=cCSz_koUhSg signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Mike Burger wrote: >> Ed Greshko wrote: >> >>> Hummm Bad news >>> >>> I had to test this and have in the intttab file >>> >>> # 5 - X11 >>> # 6 - reboot (Do NOT set initdefault to this) >>> # >>> ; id:5:initdefault: >>> id:3:initdefault: >>> >>> And the system still comes up in run level 5. >>> >> There is probably no comment sign anymore. >> >> Upstart just rapidly scans /etc/inittab for the default runlevel and >> ignores >> everything else. The only reason the file is still /etc/inittab is for >> backwards compatibility. So it doesn't use a complete inittab parser, it >> probably just scans for the first occurrence of id:?:initdefault, >> completely ignoring any comment signs. >> > > While I've not read any upstart documentation to refute your assertion, I > do believe that I've commented and uncommented enough since starting with > F9 that I am fairly confident that there is, indeed, still the default ; > as an inittab comment delimiter. > > >> Just don't leave commented lines around. >> > > Fair enough, if that is to be the end product...but if you want to test > something, and don't want to litter the system with dozens of backup > inittab files and the like, commenting a line is quicker than fully > editing it in and out. > > Probably a matter of preference, I would say. > > Kindly be careful with your attributions The comments concerning upstart were those of Kevin Kofler. Yet the fact remains, ; had no more effect than #. If you don't trust the test that I did, you can do it yourself in order to prove it. -- Life is a POPULARITY CONTEST! I'm REFRESHINGLY CANDID!! mei-mei.gres...@greshko.com http://tw.youtube.com/watch?v=cCSz_koUhSg signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
> Ed Greshko wrote: >> Ed Greshko wrote: >> >>> Mike Burger wrote: >>> >>> Mike Burger wrote: > Tim wrote: > > >> On Sun, 2009-04-05 at 22:42 -0700, Jonathan Ryshpan wrote: >> >> >> >>> 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: >>> id:1:initdefault: >>> >>> >>> >> I seem to recall seeing that before, delete the commented-out line. >> >> >> > In order to comment out a line in inttab, you need to use a > semicolon, rather than a pound sign. > > To clarify...the reason that this didn't work, in the first place, is 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. >>> I don't quite understand what you are saying >>> >>> 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? >>> >>> Thanks >>> >>> >>> >> Never mind. I see what you are saying after all I forgot for >> the moment that the original id line was left in the modified file >> Duh... >> >> > Hummm Bad news > > I had to test this and have in the intttab file > > # 5 - X11 > # 6 - reboot (Do NOT set initdefault to this) > # > ; id:5:initdefault: > id:3:initdefault: > > And the system still comes up in run level 5. Interesting. Someone once told me to use two semicolons in inittab, but I've never needed to try that. Might be worth a try. On the other hand, since Upstart doesn't use many of the options that used to be in the inittab, it may be possible that the default runlevel is actually set in an upstart config file, somewhere, now? -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org To be notified of updates to the web site, visit: https://www.bubbanfriends.org/mailman/listinfo/site-update or send a blank email message to: site-update-subscr...@bubbanfriends.org -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
> Ed Greshko wrote: > > Never mind. I see what you are saying after all I forgot for > the moment that the original id line was left in the modified file > Duh... And, of course, I replied before seeing this. Sorry. -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org To be notified of updates to the web site, visit: https://www.bubbanfriends.org/mailman/listinfo/site-update or send a blank email message to: site-update-subscr...@bubbanfriends.org -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
> Ed Greshko wrote: >> Hummm Bad news >> >> I had to test this and have in the intttab file >> >> # 5 - X11 >> # 6 - reboot (Do NOT set initdefault to this) >> # >> ; id:5:initdefault: >> id:3:initdefault: >> >> And the system still comes up in run level 5. > > There is probably no comment sign anymore. > > Upstart just rapidly scans /etc/inittab for the default runlevel and > ignores > everything else. The only reason the file is still /etc/inittab is for > backwards compatibility. So it doesn't use a complete inittab parser, it > probably just scans for the first occurrence of id:?:initdefault, > completely ignoring any comment signs. While I've not read any upstart documentation to refute your assertion, I do believe that I've commented and uncommented enough since starting with F9 that I am fairly confident that there is, indeed, still the default ; as an inittab comment delimiter. > Just don't leave commented lines around. Fair enough, if that is to be the end product...but if you want to test something, and don't want to litter the system with dozens of backup inittab files and the like, commenting a line is quicker than fully editing it in and out. Probably a matter of preference, I would say. -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org To be notified of updates to the web site, visit: https://www.bubbanfriends.org/mailman/listinfo/site-update or send a blank email message to: site-update-subscr...@bubbanfriends.org -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
> Mike Burger wrote: >> Mike Burger wrote: >>> Tim wrote: On Sun, 2009-04-05 at 22:42 -0700, Jonathan Ryshpan wrote: > 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: > id:1:initdefault: > I seem to recall seeing that before, delete the commented-out line. >>> In order to comment out a line in inttab, you need to use a >>> semicolon, rather than a pound sign. >> To clarify...the reason that this didn't work, in the first place, is >> 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. >> > I don't quite understand what you are saying > > 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? > > Thanks Again...within inittab, the # character is not a comment delimiter...the ; character is. Because the # was used, the first default line was matched, therefore processing to determine the default runlevel stopped at the first match...the line with the 5 in it. Subsequent lines, which do not contain "initdefault" are processed, because they do not match the "initdefault" parameter that was matched above. -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org To be notified of updates to the web site, visit: https://www.bubbanfriends.org/mailman/listinfo/site-update or send a blank email message to: site-update-subscr...@bubbanfriends.org -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Ed Greshko wrote: > Hummm Bad news > > I had to test this and have in the intttab file > > # 5 - X11 > # 6 - reboot (Do NOT set initdefault to this) > # > ; id:5:initdefault: > id:3:initdefault: > > And the system still comes up in run level 5. There is probably no comment sign anymore. Upstart just rapidly scans /etc/inittab for the default runlevel and ignores everything else. The only reason the file is still /etc/inittab is for backwards compatibility. So it doesn't use a complete inittab parser, it probably just scans for the first occurrence of id:?:initdefault, completely ignoring any comment signs. Just don't leave commented lines around. Kevin Kofler -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Ed Greshko wrote: > Ed Greshko wrote: > >> Mike Burger wrote: >> >> >>> Mike Burger wrote: >>> >>> Tim wrote: > On Sun, 2009-04-05 at 22:42 -0700, Jonathan Ryshpan wrote: > > > >> 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: >> id:1:initdefault: >> >> >> > I seem to recall seeing that before, delete the commented-out line. > > > In order to comment out a line in inttab, you need to use a semicolon, rather than a pound sign. >>> To clarify...the reason that this didn't work, in the first place, is >>> 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. >>> >>> >>> >> I don't quite understand what you are saying >> >> 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? >> >> Thanks >> >> >> > Never mind. I see what you are saying after all I forgot for > the moment that the original id line was left in the modified file > Duh... > > Hummm Bad news I had to test this and have in the intttab file # 5 - X11 # 6 - reboot (Do NOT set initdefault to this) # ; id:5:initdefault: id:3:initdefault: And the system still comes up in run level 5. -- hubub, hubub, HUBUB, hubub, hubub, hubub, HUBUB, hubub, hubub, hubub. mei-mei.gres...@greshko.com http://tw.youtube.com/watch?v=cCSz_koUhSg signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Ed Greshko wrote: > Mike Burger wrote: > >> Mike Burger wrote: >> >>> Tim wrote: >>> On Sun, 2009-04-05 at 22:42 -0700, Jonathan Ryshpan wrote: > 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: > id:1:initdefault: > > I seem to recall seeing that before, delete the commented-out line. >>> In order to comment out a line in inttab, you need to use a >>> semicolon, rather than a pound sign. >>> >> To clarify...the reason that this didn't work, in the first place, is >> 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. >> >> > I don't quite understand what you are saying > > 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? > > Thanks > > Never mind. I see what you are saying after all I forgot for the moment that the original id line was left in the modified file Duh... -- Is it a right to remain ignorant? -- Calvin mei-mei.gres...@greshko.com http://tw.youtube.com/watch?v=cCSz_koUhSg signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Mike Burger wrote: > Mike Burger wrote: >> Tim wrote: >>> On Sun, 2009-04-05 at 22:42 -0700, Jonathan Ryshpan wrote: >>> 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: id:1:initdefault: >>> >>> I seem to recall seeing that before, delete the commented-out line. >>> >> In order to comment out a line in inttab, you need to use a >> semicolon, rather than a pound sign. > To clarify...the reason that this didn't work, in the first place, is > 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. > I don't quite understand what you are saying 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? Thanks -- Are you sure the back door is locked? mei-mei.gres...@greshko.com http://tw.youtube.com/watch?v=cCSz_koUhSg signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Mike Burger wrote: Tim wrote: On Sun, 2009-04-05 at 22:42 -0700, Jonathan Ryshpan wrote: 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: id:1:initdefault: I seem to recall seeing that before, delete the commented-out line. In order to comment out a line in inttab, you need to use a semicolon, rather than a pound sign. To clarify...the reason that this didn't work, in the first place, is 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. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Tim wrote: On Sun, 2009-04-05 at 22:42 -0700, Jonathan Ryshpan wrote: 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: id:1:initdefault: I seem to recall seeing that before, delete the commented-out line. In order to comment out a line in inttab, you need to use a semicolon, rather than a pound sign. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
On Sun, 2009-04-05 at 23:15 -0700, Jonathan Ryshpan wrote: > On Mon, 2009-04-06 at 11:23 +0530, Shakthi Kannan wrote: > > --- On Mon, Apr 6, 2009 at 11:12 AM, Jonathan Ryshpan > > wrote: > > | I have /etc/inittab set up as follows, but the system always starts > > with > > | the X Window System running. What am I missing? > > | > > | id:1:initdefault: > > \-- > > > > Use id:3:default: > > http://www.fedorafaq.org/basics/#textonly > > I have (of course) tried that too. Runlevel 1 should have the same > effect as 3, only more so. Not true. rl1 has only one user root. No passwd checking. rl3 is a normal multi user mode without X. -- === A fool's brain digests philosophy into folly, science into superstition, and art into pedantry. Hence University education. -- G. B. Shaw === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Jonathan Ryshpan wrote: > > I have (of course) tried that too. Runlevel 1 should have the same > effect as 3, only more so. > > jon > > No really. You lose a lot of security. You also lose networking. What are you trying to do that you want to start in run level 1? Mikkel -- Remember, sometimes the dragon wins! [Polite Dragon Smile] signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Shakthi Kannan: >> Use id:3:default: >> http://www.fedorafaq.org/basics/#textonly Jonathan Ryshpan: > I have (of course) tried that too. Runlevel 1 should have the same > effect as 3, only more so. I'd agree with using 3 as a text-only default, rather than 1. Single mode has less security - you end up logging in as root without entering any password. Not sure how that affects any services you might be running which don't normally run as root. -- [...@localhost ~]$ uname -r 2.6.27.21-78.2.41.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
On Sun, 2009-04-05 at 23:13 -0700, Jonathan Ryshpan wrote: > On Mon, 2009-04-06 at 15:23 +0930, Tim wrote: > > On Sun, 2009-04-05 at 22:42 -0700, Jonathan Ryshpan wrote: > > > 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: > > > id:1:initdefault: > > > > I seem to recall seeing that before, delete the commented-out line. > > I'll give it a try. And it is as you say. Most deceptive thing I ever saw. If I were harder working, I'd report it as a bug. jon -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
On Mon, 2009-04-06 at 11:23 +0530, Shakthi Kannan wrote: > --- On Mon, Apr 6, 2009 at 11:12 AM, Jonathan Ryshpan > wrote: > | I have /etc/inittab set up as follows, but the system always starts > with > | the X Window System running. What am I missing? > | > | id:1:initdefault: > \-- > > Use id:3:default: > http://www.fedorafaq.org/basics/#textonly I have (of course) tried that too. Runlevel 1 should have the same effect as 3, only more so. jon -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
On Mon, 2009-04-06 at 15:23 +0930, Tim wrote: > On Sun, 2009-04-05 at 22:42 -0700, Jonathan Ryshpan wrote: > > 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: > > id:1:initdefault: > > I seem to recall seeing that before, delete the commented-out line. I'll give it a try. Thanks - jon -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
Hi, --- On Mon, Apr 6, 2009 at 11:12 AM, Jonathan Ryshpan wrote: | I have /etc/inittab set up as follows, but the system always starts with | the X Window System running. What am I missing? | | id:1:initdefault: \-- Use id:3:default: http://www.fedorafaq.org/basics/#textonly SK -- Shakthi Kannan http://www.shakthimaan.com -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: initdefault has no effect
On Sun, 2009-04-05 at 22:42 -0700, Jonathan Ryshpan wrote: > 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: > id:1:initdefault: I seem to recall seeing that before, delete the commented-out line. -- [...@localhost ~]$ uname -r 2.6.27.21-78.2.41.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
