cvs commit: BLFS/BOOK/postlfs/config netfs.xml random.xml

tushar at linuxfromscratch.org tushar at linuxfromscratch.org
Sun Mar 21 23:42:23 PST 2004


tushar      04/03/22 00:42:22

  Modified:    BOOK     index.xml
               BOOK/general/genlib/libfam libfam-config.xml
               BOOK/general/graphlib/libmng libmng-exp.xml
               BOOK/general/sysutils/fcron fcron-config.xml
               BOOK/general/sysutils/gpm gpm-config.xml
               BOOK/introduction/important bootscripts.xml
               BOOK/introduction/welcome changelog.xml
               BOOK/postlfs/config netfs.xml random.xml
  Log:
  First batch of lfs-bootscripts
  
  Revision  Changes    Path
  1.412     +2 -2      BLFS/BOOK/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/index.xml,v
  retrieving revision 1.411
  retrieving revision 1.412
  diff -u -u -r1.411 -r1.412
  --- index.xml	22 Mar 2004 01:32:50 -0000	1.411
  +++ index.xml	22 Mar 2004 07:42:21 -0000	1.412
  @@ -2,8 +2,8 @@
   <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" 
   			"/usr/share/docbook/docbookx.dtd" [
   
  -<!ENTITY version "CVS-20040321">
  -<!ENTITY releasedate "March 21st, 2004">
  +<!ENTITY version "CVS-20040322">
  +<!ENTITY releasedate "March 22nd, 2004">
   <!ENTITY blfs-version "cvs">
   
   <!ENTITY % book SYSTEM "book/book.ent">
  
  
  
  1.13      +10 -0     BLFS/BOOK/general/genlib/libfam/libfam-config.xml
  
  Index: libfam-config.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/general/genlib/libfam/libfam-config.xml,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -u -r1.12 -r1.13
  --- libfam-config.xml	22 Sep 2003 16:23:23 -0000	1.12
  +++ libfam-config.xml	22 Mar 2004 07:42:21 -0000	1.13
  @@ -42,6 +42,16 @@
       }
   <command>EOF</command></userinput></screen>
   
  +<!--
  +<para>If you do not have any inetd daemon installed and have no
  +wish to install one, you can also start fam during system startup
  +by installing <filename>/etc/rc.d/init.d/fam</filename>
  +init script included in the
  +<xref linkend="intro-important-bootscripts"/> package.</para>
  +                                                                                                                
  +<screen><userinput><command>make install-fam</command></userinput></screen>
  +-->
  +
   </sect3>
   
   </sect2>
  
  
  
  1.9       +3 -2      BLFS/BOOK/general/graphlib/libmng/libmng-exp.xml
  
  Index: libmng-exp.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/general/graphlib/libmng/libmng-exp.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -u -r1.8 -r1.9
  --- libmng-exp.xml	1 Feb 2004 08:25:47 -0000	1.8
  +++ libmng-exp.xml	22 Mar 2004 07:42:21 -0000	1.9
  @@ -1,8 +1,9 @@
   <sect2>
   <title>Command explanations</title>
   
  -<para><command>./autogen.sh</command>: First we have to create proper
  -configuration scripts for the Linux platform.</para>
  +<para><command>./autogen.sh</command>: This package does not ship
  +with the configure script. The autotool files need to be generated
  +before configuring the package.</para>
   
   <para><screen><command>./configure --prefix=/usr</command></screen>
   This command sets the install directory.</para>
  
  
  
  1.10      +4 -54     BLFS/BOOK/general/sysutils/fcron/fcron-config.xml
  
  Index: fcron-config.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/general/sysutils/fcron/fcron-config.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -u -r1.9 -r1.10
  --- fcron-config.xml	8 Feb 2004 00:50:22 -0000	1.9
  +++ fcron-config.xml	22 Mar 2004 07:42:21 -0000	1.10
  @@ -19,60 +19,10 @@
   Refer to the man page for fcrontab for proper parameters for your 
   situation.</para>
   
  -<para>Create the boot script with the following:</para>
  -
  -<screen><userinput><command>cat > /etc/rc.d/init.d/fcron << "EOF"
  -#!/bin/sh
  -# Begin $rc_base/init.d/fcron
  -
  -# Based on sysklogd script from LFS-3.1 and earlier.
  -# Rewritten by Gerard Beekmans  - gerard at linuxfromscratch.org
  -
  -. /etc/sysconfig/rc
  -. $rc_functions
  -
  -case "$1" in
  -        start)
  -                echo "Starting fcron..."
  -                loadproc fcron
  -                ;;
  -
  -        stop)
  -                echo "Stopping fcron..."
  -                killproc fcron
  -                ;;
  -
  -        restart)
  -                $0 stop
  -                sleep 1
  -                $0 start
  -                ;;
  -
  -        status)
  -                statusproc fcron
  -                ;;
  -
  -        *)
  -                echo "Usage: $0 {start|stop|restart|status}"
  -                exit 1
  -                ;;
  -esac
  -
  -# End $rc_base/init.d/fcron
  -EOF
  -chmod 755 /etc/rc.d/init.d/fcron</command></userinput></screen>
  -
  -<para>Create the symbolic links to this file in the relevant
  -<filename class="directory">rc.d</filename> directory
  -with the following commands:</para>
  -
  -<screen><userinput><command>cd /etc/rc.d/init.d &&
  -ln -sf ../init.d/fcron ../rc0.d/K08fcron &&
  -ln -sf ../init.d/fcron ../rc2.d/S40fcron &&
  -ln -sf ../init.d/fcron ../rc3.d/S40fcron &&
  -ln -sf ../init.d/fcron ../rc4.d/S40fcron &&
  -ln -sf ../init.d/fcron ../rc5.d/S40fcron &&
  -ln -sf ../init.d/fcron ../rc6.d/K08fcron</command></userinput></screen>
  +<para>Install <filename>/etc/rc.d/init.d/fcron</filename>
  +init script from the <xref linkend="intro-important-bootscripts"/> package.</para>
  +                                                                                                                
  +<screen><userinput><command>make install-fcron</command></userinput></screen>
   
   </sect3>
   
  
  
  
  1.11      +4 -66     BLFS/BOOK/general/sysutils/gpm/gpm-config.xml
  
  Index: gpm-config.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/general/sysutils/gpm/gpm-config.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -u -r1.10 -r1.11
  --- gpm-config.xml	16 Feb 2004 00:52:10 -0000	1.10
  +++ gpm-config.xml	22 Mar 2004 07:42:21 -0000	1.11
  @@ -2,74 +2,12 @@
   <title>Configuring <application><acronym>GPM</acronym></application></title>
   
   <sect3><title>gpm init.d script</title>
  -<para>The <command>gpm</command> init.d script can be created using 
  -the following commands:  <!-- (This assumes that you have followed the
  -<acronym>LFS</acronym> default of having your $rc_base set to <filename
  -class="directory">/etc/rc.d</filename>) --></para>
  -<screen><userinput><command>cat > /etc/rc.d/init.d/gpm << "EOF"</command>
  -#!/bin/sh
  -# Begin $rc_base/init.d/gpm
  +<para>Install the <filename>/etc/rc.d/init.d/gpm</filename>
  +init script included in the
  +<xref linkend="intro-important-bootscripts"/> package.</para>
   
  -# Based on sysklogd script from LFS-3.1 and earlier.
  -# Rewritten by Gerard Beekmans  - gerard at linuxfromscratch.org
  -# GPM specific parts by Mark Hymers - markh at linuxfromscratch.org
  +<screen><userinput><command>make install-gpm</command></userinput></screen>
   
  -. /etc/sysconfig/rc
  -. $rc_functions
  -
  -if [ -f /etc/sysconfig/mouse ]
  -	then
  -        source /etc/sysconfig/mouse
  -fi
  -
  -if [ -z "$MDEVICE" ] || [ -z "$PROTOCOL" ]
  -	then
  -	echo "Please create an /etc/sysconfig/mouse file containing"
  -	echo "MDEVICE and PROTOCOL values"
  -	exit 1;
  -fi
  -
  -case "$1" in
  -        start)
  -                echo "Starting gpm..."
  -                loadproc gpm -m $MDEVICE -t $PROTOCOL
  -                ;;
  -
  -        stop)
  -                echo "Stopping gpm..."
  -                killproc gpm
  -                ;;
  -
  -        restart)
  -                $0 stop
  -                sleep 1
  -                $0 start
  -                ;;
  -
  -        status)
  -                statusproc gpm
  -                ;;
  -
  -        *)
  -                echo "Usage: $0 {start|stop|restart|status}"
  -                exit 1
  -                ;;
  -esac
  -
  -# End $rc_base/init.d/gpm
  -<command>EOF
  -chmod 755 /etc/rc.d/init.d/gpm</command></userinput></screen>
  -
  -<para>You then need to create symbolic links to this file in the
  -relevant <filename>rc.d</filename> directories.  For example:</para>
  -<screen><userinput><command>cd /etc/rc.d/init.d &&
  -ln -sf ../init.d/gpm ../rc0.d/K10gpm &&
  -ln -sf ../init.d/gpm ../rc1.d/K10gpm &&
  -ln -sf ../init.d/gpm ../rc2.d/K10gpm &&
  -ln -sf ../init.d/gpm ../rc3.d/S70gpm &&
  -ln -sf ../init.d/gpm ../rc4.d/S70gpm &&
  -ln -sf ../init.d/gpm ../rc5.d/S70gpm &&
  -ln -sf ../init.d/gpm ../rc6.d/K10gpm</command></userinput></screen>
   </sect3>
   
   <sect3><title>Config files</title>
  
  
  
  1.7       +8 -1      BLFS/BOOK/introduction/important/bootscripts.xml
  
  Index: bootscripts.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/introduction/important/bootscripts.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -u -r1.6 -r1.7
  --- bootscripts.xml	21 Mar 2004 19:27:22 -0000	1.6
  +++ bootscripts.xml	22 Mar 2004 07:42:21 -0000	1.7
  @@ -9,7 +9,10 @@
   source directory around until completion of your
   <acronym>BLFS</acronym> system.  When a script is requested from
   lfs-bootscritps, simply change to the directory and execute the given
  -'make install-<init-script>' command.</para>
  +<command>make install-<init-script></command> command. This command installs the
  +init script to its proper location (along with any auxillary configuration
  +scripts) and also creates the appropriate symlinks to start and stop the
  +service at the appropriate run-level.</para>
   
   <para>If you are installing <acronym>BLFS</acronym>
   from an older version of LFS, see the INSTALL included in the package for
  @@ -17,5 +20,9 @@
   
   <para>Refer to <ulink url="&lfs-root;/chapter07/bootscripts.html"/> for more
   information on the lfs-bootscripts package.</para>
  +
  +<note><para>It is advisable to peruse each bootscript before installation to
  +ascertain that it satisfies your need. Also verify that the start and stop
  +symlinks it creates match your preferences.</para></note>
   
   </sect1>
  
  
  
  1.1009    +4 -0      BLFS/BOOK/introduction/welcome/changelog.xml
  
  Index: changelog.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/introduction/welcome/changelog.xml,v
  retrieving revision 1.1008
  retrieving revision 1.1009
  diff -u -u -r1.1008 -r1.1009
  --- changelog.xml	22 Mar 2004 01:32:50 -0000	1.1008
  +++ changelog.xml	22 Mar 2004 07:42:21 -0000	1.1009
  @@ -11,6 +11,10 @@
   
   <itemizedlist>
   
  +<listitem><para>March 22nd, 2004 [tushar]: Added fam, fcron, gpm, netfs,
  +and random lfs-bootscripts. Added note that users should refer to the
  +check the bootscript before installing.</para></listitem>
  +
   <listitem><para>March 21st, 2004 [tushar]: Updated network related
   bootscripts (Patch from DJ Lucas). Reworked the book to start using
   lfs-bootscripts instead of including the scripts in the book.</para></listitem>
  
  
  
  1.3       +12 -121   BLFS/BOOK/postlfs/config/netfs.xml
  
  Index: netfs.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/postlfs/config/netfs.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -u -r1.2 -r1.3
  --- netfs.xml	26 Jan 2004 22:40:37 -0000	1.2
  +++ netfs.xml	22 Mar 2004 07:42:22 -0000	1.3
  @@ -2,126 +2,17 @@
   <?dbhtml filename="netfs.html" dir="postlfs"?>
   <title>Configuring for Network Filesystems</title>
   
  -<para>While <acronym>LFS</acronym> is capable of mounting NFS volumes from
  -the get go, the lfs-bootscripts are not quite ready for this configuration.
  -Network filesystems should be unmounted before the network goes down.  The
  -<filename>netfs</filename> script below will prepare your LFS for mounting
  -network filesystems at boot time, and unmounting them when the network 
  -is stopped.</para>
  -
  -<para>  The following commands will create the <filename>netfs</filename>
  -script:</para>
  -
  -<screen><command>cat > /etc/rc.d/init.d/netfs << "EOF"</command>
  -#!/bin/sh
  -# Begin $rc_base/init.d/netfs
  -                                                                                
  -# Based on sysklogd script from LFS-3.1 and earlier.
  -# Rewritten by Gerard Beekmans  - gerard at linuxfromscratch.org
  -# netfs script written by Nathan Coulson - conathan at conet.dyndns.org
  -# and by DJ Lucas - dj at lucasit.com
  -                                                                                
  -. /etc/sysconfig/rc
  -. $rc_functions
  -                                                                                
  -case "$1" in
  -                                                                                
  -        start)
  -                # The following line mounts all entries in fstab that
  -                # have the _netdev option.  This is required for network
  -                # filesystems to be mounted at boot time.
  -                echo "Mounting network volumes..."
  -                mount -a -O _netdev
  -                evaluate_retval
  -                ;;
  -                                                                                
  -        stop)
  -                echo -n "Unmounting network volumes..."
  -                                                                                
  -                # The following line obtains a list from the output of
  -                # mount for all netfs types and anything that was
  -                # mounted with the _netdev option.
  -                NETMOUNTS=`mount | grep '_netdev\|smbfs\|ncpfs|\coda\|nfs' \
  -                        | cut -d " " -f 3 | sed 's/$/ /g'`
  -                                                                                
  -                # Check to see if anything was listed from above
  -                # (see if anything is actually needs to be unmounted)
  -                if [ x"$NETMOUNTS" != x ]
  -                then
  -                        # There is something mounted
  -                        # terminate the echo -n above
  -                        echo " "
  -                                                                                
  -                        # Try and stop processes the nice way
  -                        # (probably won't work in most cases)
  -                        fuser -m -SIGTERM $NETMOUNTS > /dev/null
  -                                                                                
  -                        # Check and see if it found anything.  If it
  -                        # did, then give 3 seconds for things to exit
  -                        # the nice way before killing them off.  
  -                        # This one will work all of the time!
  -                        if [ $? == 0 ]
  -                        then
  -                                sleep 3
  -                                fuser -km $NETMOUNTS > /dev/null
  -                        fi
  -                                                                                
  -                        # We now need to unmount all network filesystems.
  -			# We will do this with two umount commands to allow
  -			# for broken behavior of smbmount, and also to make
  -			# certain that netmounts without the _netdev option
  -			# will still get unmounted.
  -                        umount -a -O _netdev
  -                        # save the retval
  -			if [ $? != 0 ]
  -			then
  -				NERRVAL=1
  -			fi
  -
  -			# Now catch the rest of the network filesystems
  -			# by fstype.  This list can be extended later as
  -			# more network filesystems are supported by mount.
  -			umount -a -t coda,ncpfs,nfs,smbfs
  -			if [ $? == 0]
  -			then
  -				[ -z $NERRVAL ]
  -				evaluate_retval
  -			else
  -				# make certain that we return an error
  -				/bin/false		
  -				evaluate_retval
  -			fi
  -                else
  -                        # There is nothing mounted
  -                        echo "No network volumes mounted!"
  -                        # print a nice '[  OK  ]' message
  -                        evaluate_retval
  -                fi
  -                ;;
  -                                                                                
  -*)
  -                echo "Usage: $0 {start|stop}"
  -                exit 1
  -                ;;
  -esac
  -                                                                                
  -# End $rc_base/init.d/netfs
  -EOF
  -<command>chmod 0755 /etc/rc.d/init.d/netfs</command></screen>
  -
  -<para>While the excessive comments in the script might make people cringe, the
  -important part to note is that network filesystems that should be mounted at
  -boot time, must have the <emphasis role="strong">_netdev</emphasis>
  -option passed to them in <filename>/etc/fstab</filename>.</para>
  -
  -<para>Now put the necessary symlinks in place.</para>
  -
  -<screen><command>ln -sf ../init.d/netfs /etc/rc.d/rc0.d/K47netfs &&
  -ln -sf ../init.d/netfs /etc/rc.d/rc1.d/K47netfs &&
  -ln -sf ../init.d/netfs /etc/rc.d/rc2.d/K47netfs &&
  -ln -sf ../init.d/netfs /etc/rc.d/rc3.d/S28netfs &&
  -ln -sf ../init.d/netfs /etc/rc.d/rc4.d/S28netfs &&
  -ln -sf ../init.d/netfs /etc/rc.d/rc5.d/S28netfs &&
  -ln -sf ../init.d/netfs /etc/rc.d/rc6.d/K47netfs</command></screen>
  +<para>While <acronym>LFS</acronym> is capable of mounting network file
  +systems such as <acronym>NFS</acronym> these are not mounted by
  +<filename>mountfs</filename> init script since the tools needed to mount
  +these systems may not be available on the root partition and also since
  +network file systems need to be mounted after the networking is on and
  +need to be unmounted before the network goes down.</para>
  +
  +<para>Install the <filename>/etc/rc.d/init.d/netfs</filename>
  +network mount script included with the
  +<xref linkend="intro-important-bootscripts"/> package.</para>
  +                                                                                                                
  +<screen><userinput><command>make install-netfs</command></userinput></screen>
   
   </sect1>
  
  
  
  1.7       +6 -51     BLFS/BOOK/postlfs/config/random.xml
  
  Index: random.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/postlfs/config/random.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -u -r1.6 -r1.7
  --- random.xml	8 Feb 2004 00:50:22 -0000	1.6
  +++ random.xml	22 Mar 2004 07:42:22 -0000	1.7
  @@ -13,58 +13,13 @@
   predictable state.  This creates the real possibility that the number generated
   at startup may always be the same.  In order to counteract this effect,
   you should carry the entropy pool information across your shut-downs and
  -start-ups. The following init.d script and links will perform this function
  -for you automatically.</para>
  -
  -<screen><userinput><command>cat > /etc/rc.d/init.d/random << "EOF"
  -</command>
  -#!/bin/sh
  -# Begin $rc_base/init.d/random
  -
  -# Based on sysklogd script from LFS-3.1 and earlier.
  -# Rewritten by Gerard Beekmans  - gerard at linuxfromscratch.org
  -# Random script elements by Larry Lawrence
  -
  -. /etc/sysconfig/rc
  -. $rc_functions
  -
  -case "$1" in
  -        start)
  -                echo "Initializing kernel random number generator..."
  -                if [ -f /var/tmp/random-seed ]; then
  -	                cat /var/tmp/random-seed >/dev/urandom
  -		fi
  -		dd if=/dev/urandom of=/var/tmp/random-seed count=1 &>/dev/null
  -		evaluate_retval
  -		;;
  -		
  -	stop)
  -		echo "Saving random seed..."
  -		dd if=/dev/urandom of=/var/tmp/random-seed count=1 &>/dev/null
  -		evaluate_retval
  -		;;
  -
  -        *)
  -                echo "Usage: $0 {start|stop}"
  -                exit 1
  -                ;;
  -esac
  -
  -# End $rc_base/init.d/random
  -<command>EOF
  -chmod 755 /etc/rc.d/init.d/random</command></userinput></screen>
  -
  -<para>Create the symbolic links to this file in the relevant
  -<filename class="directory">rc.d</filename> directories 
  -with the following commands:</para>
  -<screen><userinput><command>cd /etc/rc.d/init.d &&
  -ln -sf ../init.d/random ../rc0.d/K45random &&
  -ln -sf ../init.d/random ../rc2.d/S25random &&
  -ln -sf ../init.d/random ../rc3.d/S25random &&
  -ln -sf ../init.d/random ../rc4.d/S25random &&
  -ln -sf ../init.d/random ../rc5.d/S25random &&
  -ln -sf ../init.d/random ../rc6.d/K45random</command></userinput></screen>
  +start-ups.</para>
   
  +<para>Install the <filename>/etc/rc.d/init.d/random</filename>
  +init script included with the
  +<xref linkend="intro-important-bootscripts"/> package.</para>
  +                                                                                                                
  +<screen><userinput><command>make install-random</command></userinput></screen>
   
   </sect1>
   
  
  
  



More information about the blfs-book mailing list