cvs commit: hints bsd-init.txt

tushar at linuxfromscratch.org tushar at linuxfromscratch.org
Sun Jun 20 20:53:33 PDT 2004


tushar      04/06/20 21:53:33

  Modified:    .        bsd-init.txt
  Log:
  Updated Hint: bsd-init
  
  Revision  Changes    Path
  1.6       +15 -9     hints/bsd-init.txt
  
  Index: bsd-init.txt
  ===================================================================
  RCS file: /home/cvsroot/hints/bsd-init.txt,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -u -r1.5 -r1.6
  --- bsd-init.txt	1 Feb 2004 03:44:36 -0000	1.5
  +++ bsd-init.txt	21 Jun 2004 03:53:33 -0000	1.6
  @@ -54,7 +54,7 @@
   2.1 Runlevel planning
   ---------------------
   
  -   Runlevels are a convenient way of chaning a system's current purpose
  +   Runlevels are a convenient way of changing a system's current purpose
    on the fly by terminating and starting a bulk of running programs at once.
    If you are not confident with runlevels and init, I suggest you get yourself
    some information on it now. Search for primers on the web and read init(8). 
  @@ -344,11 +344,12 @@
   ----------------------------end of /etc/rc.d/rc.2----------------------------
   
   
  -   Now copy /etc/rc.d/rc.2 to /etc/rc.d/rc.3:
  - 	cp /etc/rc.d/rc.2
  -   
  +   Now copy /etc/rc.d/rc.2 to /etc/rc.d/rc.3 and /etc/rc.d/rc.5:
  + 	cp /etc/rc.d/rc.2 /etc/rc.d/rc.3
  +	cp /etc/rc.d/rc.2 /etc/rc.d/rc.5
  +
       and add the following to the
  - bottom of the file:
  + bottom of the file /etc/rc.d/rc.5:
   
   
   ------------------------------------snip-------------------------------------
  @@ -374,7 +375,7 @@
   	sleep 10
   	/sbin/telinit 2 
   fi
  -----------------------------end of /etc/rc.d/rc.3----------------------------
  +----------------------------end of /etc/rc.d/rc.5----------------------------
   
   
      The script is pretty self-explaining. It looks for the most commonly used
  @@ -445,6 +446,7 @@
   
      Some notes on this file: the hwclock should be configured like the one in
    /etc/rc.d/rc.sysinit (no --utc if your hardware clock uses local time). The
  + construction
   
     case "$0" in
   	*6)
  @@ -456,8 +458,8 @@
   	;;
     esac
   
  - construction writes some status information to /etc/wtmp. It's a good idea to
  - do this, but you can safely remove it. At about two-third of the file, I call
  + writes some status information to /etc/wtmp. It's a good idea to do this,
  + but you can safely remove it. At about two-third of the file, I call
    /bin/sync. This program flushes the filesystem buffers so you won't lose any
    data. Like the construct above this is optional but I recommend it.
   
  @@ -480,7 +482,7 @@
   
      As you probably know, it is common to have a /etc/rc.d/rc.local file where
    you put commands in that will be executed at the very end of the boot process.
  - You  can use it to create up-to-date issue files or to pick a random
  + You can use it to create up-to-date issue files or to pick a random
    message of the day. But since you created all bootscripts yourself,
    you can change them as much as you like, and you probably won't need this
    script. So what's it going to be?
  @@ -529,6 +531,10 @@
   
   
   CHANGELOG:
  +[2004-06-05]
  + * corrected a typo
  + * corrected a mistake where runlevel 3 would be 5
  +
   [2003-10-02]
    * New maintainer 
    * Conversion to new hint format
  
  
  



More information about the hints mailing list