[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: LSB Spec 1.0 Criticism

>From: Ethan Benson <erbenson@alaska.net>

>> 	# Required-Start: $multiuser
>> would put it in runlevel 2,3,4,5 on both Red Hat and Debian.
>> Changing the wording to something like:
>> 	``For the purposes of the Default-Start: and Default-Stop: comment
>> 	  headers, the valid runlevels are:
>> 		1 -- single user
>> 		2 -- multiuser, no networking
>> 		3 -- multiuser, networking
>> 		4 -- X, multiuser, no networking
>> 		5 -- X, multiuser, networking
>> 	  The actual runlevels used by the distributor or the local user
>> 	  may not match these values, but the distributor is required to
>> 	  translate them to the appropriate local runlevels.''

>this makes sooo much more sense. and doesn't require debian to adopt
>deficient practices. (telling the admin how he should configure runlevels)

>From a UNIX man page for init:

          S or s
                 init goes to  the  single-user  state.  In  this
                 state,  the system console device (/dev/console)
                 is opened for reading and writing and  the  com-
                 mand  /sbin/su,  (see  su(1M)),  is invoked. Use
                 either init or telinit to  change the run  level
                 of  the  system.  Note that if the shell is ter-
                 minated (using an end-of-file),  init  only  re-
                 initializes   to   the   single-user   state  if
                 /etc/inittab does not exist.

          0-6   init enters the  corresponding  run  level.  Run
                 levels 0, 5, and 6 are reserved states for shut-
                 ting the system down. Run levels 2, 3, and 4 are
                 available as multi-user operating states.


     0     Go into firmware.

     1     Put the system in system administrator mode. All local
           file  systems  are mounted. Only a small set of essen-
           tial kernel processes are left running. This  mode  is
           for  administrative  tasks such as installing optional
           utility packages. All  files  are  accessible  and  no
           users are logged in on the system.

     2     Put the system  in  multi-user  mode.  All  multi-user
           environment   terminal   processes   and  daemons  are
           spawned. This state is commonly  referred  to  as  the
           multi-user state.

     3     Extend  multi-user  mode  by  making  local  resources
           available over the network.

     4     Is available to be defined as  an  alternative  multi-
           user  environment  configuration.  It is not necessary
           for system operation and is usually not used.

     5     Shut the machine down so that it is safe to remove the
           power. Have the machine remove power, if possible.

     6     Stop the operating system  and  reboot  to  the  state
           defined by the initdefault entry in /etc/inittab.


 EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
       js@cs.tu-berlin.de		(uni)  If you don't have iso-8859-1
       schilling@fokus.gmd.de		(work) chars I am J"org Schilling
 URL:  http://www.fokus.gmd.de/usr/schilling   ftp://ftp.fokus.gmd.de/pub/unix

Reply to: