At 02:29 PM 27/11/2000, you wrote:
>I am just putting the finishing touches on a linux kiosk system. I'm trying
>to figure out why it is that even if I enter "linux single" at the boot
>prompt, "runlevel" after the boot will report runlevel 5.
>
>I have the initial runlevel set at 5, and the whole system (save for /var
>which is re-created at each boot) is read-only.
>
>What is causing this force into runlevel 5 when it should go to runleve 1 at
>"linux single"?
If you are rebuilding /var at each boot, maybe that is why..
Man runlevel says;
-----------------------------------------
RUNLEVEL(8) Linux System Administrator's Manual RUNLEVEL(8)
NAME
runlevel -- find the current and previous system runlevel.
SYNOPSIS
runlevel [utmp]
DESCRIPTION
Runlevel reads the system utmp file (typically /var/run/utmp) to
locate the runlevel record, and then prints the previous and current system
runlevel on its standard output, separated by a single space.
If there is no previous system runlevel, the letter N will be printed
instead.
If no utmp file exists, or if no runlevel record can be found,
runlevel prints the word unknown and exits with an error.
Runlevel can be used in rc scripts as a substitute for the System-V
who -r command. However, in newer versions of init(8) this information is
also available in the environment variables RUNLEVEL and PREVLEVEL.
-----------------------------------------
So if you are writing the file /var/run/utmp when you re-create /var, you
have your answer.
Rgds,
Darryl
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
