Quote:
Originally Posted by
snchaudhari2
init S:
will take you in the system maintenance mode, where you can use fsck on mounted file systems or to repair file systems...
use fsck on mounted filesystems ???, I hope not unless you remount them in read/only mode.
Quote:
init s
will take you in the single user mode, where you can unmount your whole file system and mount it on /a or /mnt and can make changes to filesystems...you can also use fsck here.
You are partially describing here the failsafe boot mode, not a run level.
Quote:
In short,
if you just need to do file system check, you can use "init S". and if you want to modify files, blocks, cylinders, you can use "init s"
Hmm, how do you modify blocks and cylinders in a file system context ?
Quote:
Correct me if I am not....
I'm afraid you are confusing the failsafe boot mode, the administrative run level and the single user mode. Switching from multi-user to the "s" and "S" states is
exactly the same operation* and put the OS in single user mode while "init 1" put the it in system administrator mode. Booting to failsafe mode cannot be achieved with the init command alone.
* this can be confirmed by looking at init source code: http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/init/init.c#lvlname_to_state
