diff --git a/LDP/howto/linuxdoc/CVS-RCS-HOWTO.sgml b/LDP/howto/linuxdoc/CVS-RCS-HOWTO.sgml
index 057bc525..1c8c6978 100644
--- a/LDP/howto/linuxdoc/CVS-RCS-HOWTO.sgml
+++ b/LDP/howto/linuxdoc/CVS-RCS-HOWTO.sgml
@@ -44,7 +44,7 @@ Revision Control System
 <author>Al Dev (Alavoor Vasudevan) 
        <htmlurl url="mailto:alavoor[AT]yahoo.com"
              name="alavoor[AT]yahoo.com">
-<date>v22.8, 2003-03-12 	<!-- YYYY-MM-DD correct date as per linuxdoc ISO 8601 -->
+<date>v22.9, 28 March 2003
 <abstract>
 This document is a "practical guide" to very quickly setup CVS/RCS source code
 control system. This document has custom shell scripts that are wrappers 
@@ -1202,6 +1202,35 @@ cvs co projdir
 
 
 
+<sect1> An Example - Access Remote CVS Server <label id="remoteeg">
+<p>
+To access a remote cvs server, here is an example:
+<code>
+
+# Set env variable
+export EDITOR=/bin/vi
+export CVSROOT=:pserver:yourname@cvs.tldp.org:/cvsroot
+
+# Login to remote cvs server
+cvs -d $CVSROOT login
+
+# Goto some local directory
+cd $HOME/<somedirectory>
+
+# You MUST create a new directory, as below... 
+mkdir cvsroot   # Create the local cvs directory which has the same name as in CVSROOT 
+
+# Now get the files from remote CVS repository
+cd cvsroot 
+cvs get LDP/howto   # Or you can do 'cvs get . ' which will get everything
+
+# After you make changes some file and later check-in that do
+cd $HOME/<somedirectory>/cvsroot
+cvs ci -m "your update comments here" LDP/howto/somefilename.java
+</code>
+
+
+
 
 <sect> RCS Shell Scripts <label id="rcs_scripts">
 <p>
diff --git a/LDP/howto/linuxdoc/Kernel-HOWTO.sgml b/LDP/howto/linuxdoc/Kernel-HOWTO.sgml
index 957d8bb2..b7f8d445 100644
--- a/LDP/howto/linuxdoc/Kernel-HOWTO.sgml
+++ b/LDP/howto/linuxdoc/Kernel-HOWTO.sgml
@@ -46,19 +46,19 @@ Al Dev (Alavoor Vasudevan)
 			" name="
 			alavoor[AT]yahoo.com
 		">
-<date>v5.2, 27 March 2003
+<date>v5.3, 31 March 2003
 
 <abstract>
 This is a detailed guide to kernel configuration, compilation, upgrades,
 and troubleshooting for ix86-based systems. Can be useful for other architectures
-as well. This document is kept small & simple so that even non-technical home computer
-users will be able to compile the Linux Kernel and run Linux.
+as well. This document is kept small & simple, so that even non-technical 
+"home computer users" will be able to compile and run the Linux Kernel.
 </abstract>
 
 <toc>
 
-<sect> Introduction <p>
-
+<sect> Introduction 
+<p>
 You compile Linux kernel for one of following reasons:
 <itemize>
 <item> You are doing kernel development
@@ -104,13 +104,10 @@ computer and hence there is Linux, Linux & Linux everywhere in United States!
 <item> And for many hundreds of reasons - too numerous to list!
 </itemize>
 
-If your time is precious then go straight to chapter 2 "Quick Steps".
-And, if you are successful in compiling the Linux kernel then you
-can skip the remaining chapters.
 <p>
 
-Note: This document is kept small & simple so that even non-technical home computer
-users will be able to compile the Linux Kernel and run Linux!
+Note: This document is kept small & simple, so that even non-technical 
+"home computer users" will be able to compile and run the Linux Kernel!
 
 
 
@@ -148,21 +145,30 @@ building the Linux kernel.
 <sect1> Minor Upgrading of Kernel <label id="upgrading">
 <p>
 If you had already built the kernel and you want to upgrade to next patch release,
-then you can simply copy the existing config and reuse it.
+then you can simply copy the existing config file and reuse it.
 (For example you have built kernel 2.4.19 and want to upgrade to 2.4.20).
 <p>
 <bf>For minor upgrades : </bf> 
-You can copy the .config file from your old linux kernel source tree 
-to new kernel tree (may save time, if you want to reuse the old settings).
+This step may save you time, if you want to reuse the old settings.
+Whenever you install the kernel, generally you put the config file in /boot.
+So, you can use the existing version of config file: 
+<code>
+bash# mv /usr/src/linux/.config  /usr/src/linux/.config.save
+bash# cp /boot/config-2.4.18-19.8.0  /usr/src/linux/.config
+</code>
+Or another method is - you can copy the .config file from your old 
+linux kernel source tree 
+to new kernel tree. 
 <code>
 	bash# ls -l /usr/src/lin*  # You can see that /usr/src/linux is a soft link
 	bash# cd /usr/src/linux 
 	bash# cp ../linux-old-tree/.config .  # Example cp ../linux-2.4.19/.config .
 </code>
-or alternatively, you can use "make oldconfig"
-which default all questions based on the contents of your existing ./.config file.
 
+or one other method is - you can use "make oldconfig"
+which default all questions based on the contents of your existing ./.config file.
 <p>
+
 NOTE: If you do not have lot of disk space in /usr/src then you can unpack the 
 kernel source package on any partition where you have free disk space (like /home).
 Because kernel compile needs lot of disk space for object files like *.o.
@@ -176,20 +182,27 @@ After this, look in the next section to do make and install.
 <p>
 <enum>
 <item> Unpack the sources
-<item> Optional - You can copy the .config file from your old linux kernel source tree 
+<item> Optional - Copy config file : You can copy the config file from your 
+old linux kernel source tree 
 to new kernel tree (may save time, if you want to reuse the old settings).
 <item> make clean; make mrproper
 <item> make xconfig
 <item> make dep
-<item> nohup make bzImage # And you can go to lunch or go to bed (have nice Linux dreams in sleep) and when you come back the system is ready! And see the log with 'less nohup.out'.
-<item> make modules
-<item> make modules_install
+<item> Give a unique name to your new Kernel - Edit /usr/src/linux/Makefile 
+and change EXTRAVERSION
+<item> nohup make bzImage 
+<item> 'make modules' and 'make modules_install'
+<item> And you can go to lunch or go to bed (have nice Linux dreams in sleep) 
+and when you come back the system is ready! And see the log with 'less nohup.out'.
 <item> make install # But NOT recommended - use cp /usr/src/linux/arch/i386/boot/bzImage /boot/bzImage.myker
-<item> make rpm   # To build rpm packages 
-<item> configure LILO or GRUB.
+<item> Configure GRUB or LILO.
+<item> Reboot and check new kernel is booting
+<item> Create emergency boot disk -  bzdisk  or mkbootdisk
+<item> Optional - make rpm   # To build rpm packages
 <item> Optional - make clean (If you want to free up disk space)
 </enum>
 
+<!--  no need - use make rpm
 On Redhat, instead of using 'make' commands you can use rpm command to build kernel. 
 If you want to build binary RPMs (kernel*.i386.rpm), do this:
 <enum>
@@ -198,6 +211,7 @@ If you want to build binary RPMs (kernel*.i386.rpm), do this:
 <item> rpmbuild -ba kernel*.spec  # or rpm -ba kernel*.spec  # for old systems
 <item> cd /usr/src/redhat/i386; rpm -i kernel*.rpm
 </enum>
+-->
 
 See details of above steps in the following sections....
 
@@ -260,15 +274,25 @@ For this reason the /usr/src/linux MUST be a soft link pointing to your source d
 <p>
 
 <item> 
-<bf>Optional : </bf> 
-You can copy the .config file from your old linux kernel source tree 
-to new kernel tree (may save time, if you want to reuse the old settings).
+<bf>Optional - Copy config file : </bf> 
+This step may save you time, if you want to reuse the old settings.
+
+Whenever you install the kernel, generally you put the config file in /boot.
+So, you can use the existing version of config file: 
+<code>
+bash# mv /usr/src/linux/.config  /usr/src/linux/.config.save
+bash# cp /boot/config-2.4.18-19.8.0  /usr/src/linux/.config
+</code>
+Or another method is - you can copy the .config file from your old 
+linux kernel source tree 
+to new kernel tree 
 <code>
 	bash# ls -l /usr/src/lin*  # You can see that /usr/src/linux is a soft link
 	bash# cd /usr/src/linux 
 	bash# cp ../linux-old-tree/.config .  # Example cp ../linux-2.4.19/.config .
 </code>
-or alternatively, you can use "make oldconfig"
+
+or one other method is - you can use "make oldconfig"
 which default all questions based on the contents of your existing ./.config file.
 <p>
 <!-- intentional blank line with a period --> 
@@ -279,6 +303,7 @@ which default all questions based on the contents of your existing ./.config fil
 Before doing mrproper below, you may want to backup the .config file.
 <code>
 	bash# cd /usr/src/linux 
+	bash# cp .config .config.save
 	bash# make clean
 	bash# make mrproper  # Must do this if want to start clean slate or if you face lot of problems
 </code>
@@ -328,22 +353,16 @@ Within 'make xconfig' you must do these (to avoid problems) -
 <itemize>
 <item> <bf>VERY IMPORTANT !!! : </bf> Select proper CPU type - Pentium 3, AMD K6, 
 Cyrix, Pentium 4, Intel 386, DEC Alpha, PowerPC otherwise kernel compile will fail
-and even if it compiles will not boot!!
+and even if it compiles, it will not boot!!
 <item> Select SMP support - whether single CPU or multiple CPUs
 <item> Filesystems - Select Windows95 Vfat, MSDOS, NTFS as part of kernel and 
-not as loadable modules. (My personal preference but you are free to pick your own option).
+not as loadable modules. (My personal preference, but you are free to pick your own option).
 <item> Enable the Loadable kernel modules support! 
 With this option you can load/unload the device drivers 
 dynamically on running linux system on the fly.
-See these man pages 
-<code>
-bash# rpm -i /mnt/cdrom/Redhat/RPMS/modutils*.rpm
-bash# man lsmod
-bash# man insmod
-bash# man rmmod
-bash# man depmod
-bash# man modprobe
-</code>
+
+See the Modules chapter at <ref id="loadablemodules" name="Loadable Modules">.
+
 </itemize>
 <p>
 
@@ -375,33 +394,6 @@ Here look for EXTRAVERSION = -19.8.0Blah_Blah_Blah
 and change to something like EXTRAVERSION = -19.8.0MyKernel.26Jan2003
 
 <p>
-<item> 
-<bf>LOADABLE MODULES: </bf>
-This step is required <bf>ONLY if</bf> you had enabled Loadable module support in 
-step 3 above.
-Loadable module are located in /lib/modules. You MUST do this step if you enabled or
-disabled any modules, otherwise you will get 'unresolved symbols' errors during
-or after kernel boot.
-Check for insmod command which is extensively used for loading the modules.
-<code>
-bash# cd /usr/src/linux
-bash# make modules
-bash# make modules_install
-</code>
-This will copy the modules to /lib/modules directory.
-
-For example to load the module <tt>/lib/modules/2.4.2-2/kernel/drivers/block/loop.o</tt>, you would
-do :
-<code>
-bash# man insmod
-bash# modprobe loop
-bash# insmod loop
-bash# lsmod 
-</code>
-You can set PATH the insmod searches in /etc/modules.conf
-
-<p>
-
 
 
 <item> 
@@ -428,19 +420,63 @@ Now, give the make command -
 This will put the kernel in /usr/src/linux/arch/i386/boot/bzImage 
 </code>
 
-And now, you can go to lunch or go to bed (have nice Linux dreams in sleep) and 
-when you come back the system is ready! You can check with command 'less nohup.out' to see
-the log of output.
 
 <p>
+<item> 
+<bf>LOADABLE MODULES: </bf>
+Now, while the 'make' is cranking along in the previous step "Do make", you
+should bring up another new xterm shell window and follow these steps:
+
+This step is required <bf>ONLY if</bf> you had enabled Loadable module support in 
+step "Configure Step" above.
+
+Loadable module are located in /lib/modules. You MUST do this step if you enabled or
+disabled any modules, otherwise you will get 'unresolved symbols' errors during
+or after kernel boot.
+<code>
+# Bring up a new Xterm shell window and ...
+bash# cd /usr/src/linux
+
+# Redirect outputs such that you do not overwrite the nohup.out which is still running...
+bash# nohup make modules 1> modules.out 2> modules.err  &
+
+bash# make modules_install   # Do this, only after the above make command is successful
+</code>
+This will copy the modules to /lib/modules directory.
+
+See the Modules chapter at <ref id="loadablemodules" name="Loadable Modules">.
+<p>
+
+<item>
+<bf>Now go to Lunch or Bed :</bf>
+Since both the make windows are cranking along, 
+and now, you can go to lunch (chitchat, have nap) or go to 
+bed (have nice Linux dreams in sleep) and when you wake up and 
+come back the system is ready! You can check with 
+command 'less nohup.out' to see the log of output.
+<code>
+bash# cd /usr/src/linux
+bash# less nohup.out
+bash# less modules.err
+bash# less modules.out
+
+If no errors then do:
+bash# make modules_install  
+</code>
+
 
 <item> 
 <bf>bzImage: </bf>
 After bzImage is successful, copy the kernel image to /boot directory.
 You must copy the new kernel image to /boot directory, otherwise the 
-new kernel <bf>MAY NOT</bf> boot. 
+new kernel <bf>MAY NOT</bf> boot. You must also copy the config file to /boot area
+to reflect the kernel image, for documentation purpose.
 <code>
 bash# cp /usr/src/linux/arch/i386/boot/bzImage     /boot/bzImage.myker.26mar2001
+
+# You MUST copy the config file to reflect the corresponding kernel image, for documentation purpose.
+bash# cp /usr/src/linux/.config /boot/config-<your_kernelversion_date>
+# Example: cp /usr/src/linux/.config /boot/config-2.4.18-19.8.0-26mar2001
 </code>
 
 <bf>NOTE : </bf> 
@@ -493,6 +529,15 @@ bash# rpm -i mkbootdisk*.rpm
 bash# man mkbootdisk
 </code>
   
+<p>
+<item> Build RPMs 
+<p>
+Optional - You can also build RPM packages of kernel, in case you want to install the
+new image on several machines.
+<code>
+make rpm   # To build rpm packages
+</code>
+
 
 <p>
 <item> 
@@ -514,410 +559,154 @@ See the <ref id="postkernel" name="Appendix D - Post Kernel Building">.
 
 
 
-<sect> Troubleshoot Common Mistakes <label id="troubleshoot">
+
+<sect> Loadable Modules <label id="loadablemodules">
+<p>
+Loadable kernel modules can save memory and ease configuration. The scope
+of modules has grown to include filesystems, ethernet card drivers, tape
+drivers, printer drivers, and more.
+
+Loadable modules are pieces of kernel code which are not
+linked (included) directly in the kernel. One compiles them separately,
+and can insert and remove them into the running kernel at almost any
+time. Due to its flexibility, this is now the preferred way to code certain
+kernel features. Many popular device drivers, such as the PCMCIA
+drivers and the QIC-80/40 tape driver, are loadable modules.
 <p>
 
-<sect1> Compiles OK but does not boot
-<p>
-If the kernel compiles ok but booting never works 
-and it always complains with a kernel panic about /sbin/modprobe.
+See the Module-HOWTO at <url url="http://www.tldp.org/HOWTO/Module-HOWTO">.
 
-Solution: You did not create initrd image file. 
-See the Appendix A at <ref id="createinitrd" name="Creating initrd.img file">.
-Also, you must do 'make modules' and 'make  modules_install' in addition to
-creating the initrd image file.
-
-<sect1> The System Hangs at LILO
-<p>
-<bf>Sympton: </bf> After you build the kernel and reboot, the system hangs just before LILO.
-
-<bf>Reason: </bf> Probably you did not set the BIOS to pick up the proper Primary Master IDE and
-Secondary Slave IDE hard disk partition.
-
-<bf>Solution: </bf>Power on the machine and press DEL key to do setup of the BIOS (Basic Input Output system). Select the IDE settings and set proper primary hard disk partition and slave drives.
-When the system boots it looks for the primary IDE hard disk and the Master Boot Record partition.
-It reads the MBR and starts loading the Linux Kernel from the hard disk partition.
-
-
-<sect1> No init found
-<p>
-The following mistake is commited very frequently by new users.
-
-If your new kernel does not boot and you get -
+And see these man pages 
 <code>
-Warning: unable to open an initial console
-Kernel panic: no init found. Try passing init= option to kernel
-</code>
-The problem is that you <bf>did not</bf> set the "root=" parameter properly
-in the /etc/lilo.conf. In my case, I used root=/dev/hda1 which is
-having the root partition "/". You must properly point the root device in your
-lilo.conf, it can be like /dev/hdb2 or /dev/hda7.
-
-The kernel looks for the init command which is located in /sbin/init.
-And /sbin directory lives on the root partition.
-For details see -
-<code>
-bash# man init
-</code>
-
-
-<sect1> Lot of Compile Errors
-<p>
-The 'make', 'make bzImage',  'make modules' or 'make modules_install' 
-gives compile problems.
-You should give 'make mrproper' before doing make.
-<code>
-bash# make mrproper
-</code>
-If this problem persists, then try menuconfig instead of xconfig.
-Sometimes GUI version xconfig causes some problems:
-<code>
-bash# export TERM=VT100
-bash# make menuconfig
-</code>
-
-
-
-
-<sect1> The 'depmod' gives "Unresolved symbol error messages"
-<p>
-When you run <tt>depmod</tt> it gives "Unresolved symbols". A sample error message 
-is given here to demonstrate the case: 
-<code>
-bash$ su - root
+bash# rpm -i /mnt/cdrom/Redhat/RPMS/modutils*.rpm
+bash# man lsmod
+bash# man insmod
+bash# man rmmod
 bash# man depmod
-bash# depmod
-depmod: *** Unresolved symbols in /lib/modules/version/kernel/drivers/md/linear.o
-depmod: *** Unresolved symbols in /lib/modules/version/kernel/drivers/md/multipath.o
-depmod: *** Unresolved symbols in /lib/modules/version/kernel/drivers/md/raid0.o
-depmod: *** Unresolved symbols in /lib/modules/version/kernel/drivers/md/raid1.o
-depmod: *** Unresolved symbols in /lib/modules/version/kernel/drivers/md/raid5.o
+bash# man modprobe
 </code>
-
-<bf>Reason: </bf> You did not make modules and install the modules after building 
-the new kernel with <tt>"make bzImage"</tt>.
-
-<bf>Solution: </bf> After you build the new kernel, you must do:
+For example to load the module <tt>/lib/modules/2.4.2-2/kernel/drivers/block/loop.o</tt>, 
+you would do :
 <code>
-bash$ su - root
-bash# cd /usr/src/linux
-bash# make modules
-bash# make modules_install
+bash# man insmod
+bash# modprobe loop
+bash# insmod loop
+bash# lsmod 
 </code>
+You can set the PATH which the insmod searches in /etc/modules.conf.
 
 
-
-<sect1> Kernel Does Not Load Module - "Unresolved symbols" Error Messages
-<p>
-When you boot kernel and system tries to load any modules and
-you get "Unresolved symbol : __some_function_name" then it means
-that you did not clean compile the modules and kernel. It is mandatory that
-you should do <bf>make clean</bf> and make the modules. Do this -
+<sect1>Installing the module utilities<p>
+You can install the Module Utilities RPM with:
 <code>
-	bash# cd /usr/src/linux
-	bash# make dep
-	bash# make clean
-	bash# nohup make bzImage &  
-	bash# tail -f nohup.out     (.... to monitor the progress) 
-	bash# make modules
-	bash# make modules_install
+bash# rpm -i /mnt/cdrom/Redhat/RPMS/modutils*.rpm
 </code>
 
-
-
-<sect1> Kernel fails to load a module 
 <p>
-If the kernel fails to load a module (say loadable module for network card
-or other devices), then you may want to try to build the driver for device
-right into the kernel. Sometimes <it><bf>loadable module will NOT 
-work</bf></it> and the driver
-needs to be built right inside the kernel. For example - some network cards do not
-support loadable module feature - you MUST build the driver of the network card
-right into linux kernel. Hence, in 'make xconfig' you MUST not select loadable
-module for this device.
-
-
-
-
-<sect1> Loadable modules
+<tt>insmod</tt> inserts a module into the running kernel. Modules
+usually have a <tt>.o</tt> extension; the example driver mentioned above
+is called <tt>drv_hello.o</tt>, so to insert this, one would say
+`<tt>insmod drv_hello.o</tt>'. To see the modules that the kernel is
+currently using, use <tt>lsmod</tt>. The output looks like this:
+<verb>
+    blah# lsmod
+    Module:        #pages:  Used by:
+    drv_hello          1
+</verb>
+`<tt>drv_hello</tt>' is the name of the module, it uses one page (4k) of
+memory, and no other kernel modules depend on it at the moment. To remove
+this module, use `<tt>rmmod drv_hello</tt>'. Note that <tt>rmmod</tt>
+wants a <it>module name,</it> not a filename; you get this from
+<tt>lsmod</tt>'s listing. The other module utilities' purposes are documented
+in their manual pages.
 <p>
-You can install default loadable modules with -
 
-The step given below may not be required but is needed <bf>ONLY FOR EMERGENCIES</bf> where
-your /lib/modules files are damaged. If you already have 
-the /lib/modules directory and in case you 
-want replace them use the --force to replace the package and 
-select appropriate cpu architecture.
+<sect1>Modules distributed with the kernel<p>
+As of version 2.0.30, most of everything is available as a loadable
+modules. To use
+them, first make sure that you don't configure them into the regular
+kernel; that is, don't say <tt>y</tt> to it during `<tt>make config</tt>'.
+Compile a new kernel and reboot with it. Then, <tt>cd</tt> to
+<tt>/usr/src/linux</tt> again, and do a `<tt>make modules</tt>'. This
+compiles all of the modules which you did not specify in the kernel
+configuration, and places links to them in <tt>/usr/src/linux/modules</tt>.
+You can use them straight from that directory or execute `<tt>make
+modules_install</tt>', which installs them in
+<tt>/lib/modules/x.y.z</tt>, where <tt>x.y.z</tt> is the kernel release.
+<p>
 
-For new versions of linux redhat linux 6.0 and later, the kernel modules are
-included with kernel-2.2*.rpm. Install the loadable modules and the kernel with
+This can be especially handy with filesystems. You may not use the minix
+or msdos filesystems frequently. For example, if I encountered an msdos
+(shudder) floppy, I would <tt>insmod /usr/src/linux/modules/msdos.o</tt>,
+and then <tt>rmmod msdos</tt> when finished. This procedure saves about
+50k of RAM in the kernel during normal operation. A small note is in order for
+the minix filesystem: you should <it>always</it> configure it directly into the
+kernel for use in ``rescue'' disks.
+<p>
+
+
+
+<sect1> Howto Install Just A Single Module ?
+<p>
+Let us assume that you already did 'make modules' and 'make modules_install'.
+And later you did 'make clean' to free up disk space. And now, you want to
+change a "C" file in one of the modules and want to rebuild just that module 
+and copy the module file to /lib/modules. How do you do it?
+
+You can compile just a single module file (say like foo.o) and install it.
+For this simply edit the Makefile and change the SUBDIRS to add only those
+directories you are interested.
+
+For an example, if I am interested in installing only fs/autofs module, then I 
+do the following :
 <code>
-	This will list the already installed package.
-bash# rpm -qa | grep -i kernel
-	
-bash# rpm -U --force  /mnt/cdrom/Redhat/RPMS/kernel-2.2.14-5.0.i686.rpm
-(or)
-bash# rpm -U --force  /mnt/cdrom/Redhat/RPMS/kernel-2.2.14-5.0.i586.rpm
-(or)
-bash# rpm -U --force  /mnt/cdrom/Redhat/RPMS/kernel-2.2.14-5.0.i386.rpm
+cd /usr/src/linux
+cp Makefile Makefile.my
+vi Makefile.my  
+# And comment out the line having 'SUBDIRS' and add the 
+# directory you are interested, for example like fs/autofs as below :
+	#SUBDIRS	=kernel drivers mm fs net ipc lib abi crypto
+	SUBDIRS		=fs/autofs
+# Save the file Makefile.my and give -
+make -f Makefile.my modules
+# This will create module autofs.o
+
+# Now, copy the module object file to destination /lib/modules
+make -f Makefile.my modules_install
+# And this will do 'cp autofs.o /lib/modules/2.4.18-19.8.0/kernel/fs/autofs'
 </code>
 
-This is only for old versions of redhat linux 5.2 and before.
-Boot new kernel and install the loadable 
-modules from RedHat Linux "contrib" cdrom 
+<!--  Adding or changing a variable in gnu make:
+make TOPDIR=/usr/src/linux
+# Another Method: Check with dry run option
+make -n modules > dryrun.txt
+-->
+
+Learn more about Makefile and make. See the manual for GNU make at
+<itemize>
+<item> <url url="http://www.gnu.org/manual/make">.
+<item> University of Utah Makefile 
+<url url="http://www.math.utah.edu/docs/info/make-stds_toc.html">
+<item> University of Hawaii Makefile <url url="http://www.eng.hawaii.edu/Tutor/Make">
+<item> In Linux - man make
+<item> In Linux - info make
+</itemize>
+
+
+Get familiar with the Makefile which makes the modules. The Makefile has module line like
 <code>
-bash# rpm -i /mnt/cdrom/contrib/kernel-modules*.rpm 
-....(For old linux systems which do not have insmod pre-installed) 
+modules: $(patsubst %, _mod_%, $(SUBDIRS))
 </code>
-<p>
 
-<sect1> See Docs
-<p>
-More problems. You can read the /usr/src/linux/README (at least once)
-and also /usr/src/linux/Documentation.
+The patsubst function has the syntax $(patsubst pattern,replacement,text). It uses the 
+percent symbol (%) the same way pattern rules do - as a string which matches in both
+the pattern and the replacement text. It searches the text for whitespace-separated 
+words that match the pattern and substitutes the replacement for them.
 
+This makefile includes shell functions as well as standard make functions. The syntax 
+for a shell function is $(shell command). This returns the output of the shell 
+function (stripping new lines).
 
-<sect1>make clean <p>
-If your new kernel does really weird things after a routine kernel upgrade,
-chances are you forgot to <tt>make clean</tt> before compiling the new
-kernel. Symptoms can be anything from
-your system outright crashing, strange I/O problems, to crummy
-performance. Make sure you do a <tt>make dep</tt>, too.
-<p>
-
-<sect1>Huge or slow kernels <p>
-If your kernel is sucking up a lot of memory, is too large,
-and/or just takes forever to compile even when you've got your new
-Quadbazillium-III/4400 working on it, you've probably got lot of unneeded
-stuff (device drivers, filesystems, etc) configured. If you don't use it,
-don't configure it, because it does take up memory.
-The most obvious symptom of kernel bloat is extreme swapping in and out of
-memory to disk; if your disk is making a lot of noise and it's not one of
-those old Fujitsu Eagles that sound like like a jet landing when turned
-off, look over your kernel configuration.
-<p>
-
-You can find out how much memory the kernel is using by taking the
-total amount of memory in your machine and subtracting from it the
-amount of ``total mem'' in <tt>/proc/meminfo</tt>  or the output of the command
-`<tt>free</tt>'.
-<p>
-
-<sect1>The parallel port doesn't work/my printer doesn't work<p>
-Configuration options for PCs are: First, under the category `General Setup',
-select `Parallel port support' and `PC-style hardware'. Then under
-`Character devices', select `Parallel printer support'.
-<p>
-Then there are the names. Linux 2.2 names the printer devices differently
-than previous releases. The upshot of this is that if you had an <tt>lp1</tt>
-under your old kernel, it's probably an <tt>lp0</tt> under your new one.
-Use `<tt>dmesg</tt>' or look through the logs in <tt>/var/log</tt> to find
-out.
-<p>
-
-<sect1>Kernel doesn't compile <p>
-
-If it does not compile, then it is likely that a patch failed, or your
-source is somehow corrupt. Your version of gcc also might not
-be correct, or could also be corrupt (for example, the include files
-might be in error). Make sure that the symbolic links which
-Linus describes in the <tt>README</tt> are set up correctly. In general, if
-a standard kernel
-does not compile, something is seriously wrong with the system, and 
-reinstallation of certain tools is probably necessary.
-<p>
-
-In some cases, gcc can crash due to hardware problems. The error
-message will be something like ``xxx exited with signal 15'' and it will
-generally look very mysterious. I probably would not mention this, except
-that it happened to me once - I had some bad cache memory, and the compiler
-would occasionally barf at random. Try reinstalling gcc first if you
-experience problems. You should only get suspicious if your kernel compiles
-fine with external cache turned off, a reduced amount of RAM, etc.
-<p>
-
-It tends to disturb people when it's suggested that their hardware has
-problems. Well, I'm not making this up. There is an FAQ for it -- it's at
-<url url="http://www.bitwizard.nl/sig11">.
-<p>
-
-<sect1>New version of the kernel doesn't seem to boot<p>
-
-You did not run LILO, or it is not configured correctly. One thing that
-``got'' me once was a problem in the config file; it said 
-`<tt>boot = /dev/hda1</tt>'
-instead of `<tt>boot = /dev/hda</tt>' (This can be really annoying at first,
-but once you have a working config file, you shouldn't need to
-change it.).
-<p>
-
-<sect1> You forgot to run LILO, or system doesn't boot at all<p>
-
-Ooops! The best thing you can do here is to boot off of a floppy disk or
-CDROM and
-prepare another bootable floppy (such as `<tt>make zdisk</tt>' would do).
-You need to know where your root (<tt>/</tt>) filesystem is and what type
-it is (e.g. second extended, minix). In the example below, you also need
-to know what filesystem your <tt>/usr/src/linux</tt> source
-tree is on, its type, and where it is normally mounted.<p>
-
-In the following example, <tt>/</tt> is <tt>/dev/hda1</tt>, and the
-filesystem which holds <tt>/usr/src/linux</tt>
-is <tt>/dev/hda3</tt>, normally mounted at <tt>/usr</tt>. Both are
-second extended filesystems. The working kernel image in
-<tt>/usr/src/linux/arch/i386/boot</tt> is called <tt>bzImage</tt>.<p>
-
-The idea is that if there is a functioning
-<tt>bzImage</tt>, it is possible to use that
-for the new floppy. Another alternative, which may or may not work better
-(it depends on the particular method in which you messed up your system) is
-discussed after the example.<p>
-
-First, boot from a boot/root disk combo or rescue disk, and
-mount the filesystem which contains the working kernel image:<p>
-
-<verb>
-    mkdir /mnt
-    mount -t ext2 /dev/hda3 /mnt
-</verb>
-
-If <tt>mkdir</tt> tells you that the directory already exists, just ignore
-it. Now, <tt>cd</tt> to the place where the working kernel image was. Note
-that
-<verb>
-/mnt + /usr/src/linux/arch/i386/boot - /usr = /mnt/src/linux/arch/i386/boot
-</verb>
-Place a formatted
-disk in drive ``A:'' (not your boot or root disk!), dump
-the image to the disk, and configure it for your root filesystem:<p>
-
-<verb>
-    cd /mnt/src/linux/arch/i386/boot
-    dd if=bzImage of=/dev/fd0
-    rdev /dev/fd0 /dev/hda1
-</verb>
-
-<tt>cd</tt> to <tt>/</tt> and unmount the normal <tt>/usr</tt> filesystem:<p>
-<verb>
-    cd /
-    umount /mnt
-</verb>
-
-You should now be able to reboot your system as normal from this floppy.
-Don't forget to run lilo (or whatever it was that you did wrong) after
-the reboot!<p>
-
-As mentioned above, there is another common alternative. If you
-happened to have a working kernel image in <tt>/</tt> (<tt>/vmlinuz</tt>
-for example), you can use that for a boot disk. Supposing all of the above
-conditions, and that my kernel image is <tt>/vmlinuz</tt>, just make these
-alterations to the example above: change
-<tt>/dev/hda3</tt> to <tt>/dev/hda1</tt> (the <tt>/</tt> filesystem),
-<tt>/mnt/src/linux</tt> to
-<tt>/mnt</tt>, and <tt>if=bzImage</tt> to <tt>if=vmlinuz</tt>. The
-note explaining how to derive <tt>/mnt/src/linux</tt> may be ignored.
-<p>
-
-Using LILO with big drives (more than 1024 cylinders) can cause problems.
-See the LILO mini-HOWTO or documentation for help on that.
-<p>
-
-<sect1>It says `warning: bdflush not running' <p>
-
-This can be a severe problem. Starting with a kernel release
-after Linux v1.0 (around 20 Apr 1994), a program called `<tt>update</tt>' which
-periodically flushes out the filesystem buffers, was upgraded/replaced. Get
-the sources to `<tt>bdflush</tt>'
-(you should find it where you got your kernel source), and install it (you
-probably want to run your system under the old kernel while doing this). It
-installs itself as `<tt>update</tt>' and after a reboot, the new kernel
-should no longer complain.
-<p>
-
-<sect1>I can't get my IDE/ATAPI CD-ROM drive to work<p>
-Strangely enough, lot of people cannot get their ATAPI drives working,
-probably because there are a number of things that can go wrong.
-<p>
-If your CD-ROM drive is the only device on a particular IDE
-interface, it must be jumpered as ``master'' or ``single.'' Supposedly,
-this is the most common error.
-<p>
-Creative Labs (for one) has put IDE interfaces on their sound cards now.
-However, this leads to the interesting problem that while some people only
-have one interface to being with, many have two IDE interfaces built-in to
-their motherboards (at IRQ15, usually), so a common practice is to make the
-soundblaster interface a third IDE port (IRQ11, or so I'm told).
-<p>
-This causes problems with older Linux versions like 1.3 and below.
-in that versions Linux don't support a third IDE interface.
-To get around this, you have a few choices.<p>
-<p>
-If you have a second IDE port already, chances are that you are not using
-it or it doesn't already have two devices on it. Take the ATAPI drive off
-the sound card and put it on the second interface. You can then disable the
-sound card's interface, which saves an IRQ anyway.
-<p>
-If you don't have a second interface, jumper the sound card's interface
-(not the sound card's sound part) as IRQ15, the second interface. It should
-work.
-<p>
-
-<sect1>It says weird things about obsolete routing requests <p>
-
-Get new versions of the <tt>route</tt> program and any other programs
-which do route manipulation.
-<tt>/usr/include/linux/route.h</tt>  (which is actually a file in
-<tt>/usr/src/linux</tt>) has changed.
-<p>
-
-<sect1>``Not a compressed kernel Image file''<p>
-Don't use the <tt>vmlinux</tt> file created in <tt>/usr/src/linux</tt> as
-your boot image; <tt>[..]/arch/i386/boot/bzImage</tt> is the right
-one.
-<p>
-
-<sect1>Problems with console terminal after upgrade to Linux v1.3.x<p>
-Change the word <tt>dumb</tt> to <tt>linux</tt> in the console termcap
-entry in <tt>/etc/termcap</tt>. You may also have to make a terminfo entry.
-<p>
-
-<sect1> Can't seem to compile things after kernel upgrade<p>
-The linux kernel source includes a number of include files (the things that
-end with <tt>.h</tt>) which are referenced by the standard ones in
-<tt>/usr/include</tt>. They are typically referenced like this (where
-<tt>xyzzy.h</tt> would be something in <tt>/usr/include/linux</tt>):
-<verb>
-    #include <linux/xyzzy.h>
-</verb>
-Normally, there is a link called <tt>linux</tt> in <tt>/usr/include</tt> to
-the <tt>include/linux</tt> directory of your kernel source
-(<tt>/usr/src/linux/include/linux</tt> in the typical system). If this link
-is not there, or points to the wrong place, most things will not compile at
-all. If you decided that the kernel source was taking too much room on the
-disk and deleted it, this will obviously be a problem. Another way it might
-go wrong is with file permissions; if your <tt>root</tt> has a umask
-which doesn't allow other users to see its files by default, and you
-extracted the kernel source without the <tt>p</tt> (preserve filemodes)
-option, those users also won't be able to use the C compiler. Although you
-could use the <tt>chmod</tt> command to fix this, it is probably easier to
-re-extract the include files. You can do this the same way you did the
-whole source at the beginning, only with an additional argument:<p>
-<verb>
-    blah# tar zxvpf linux.x.y.z.tar.gz linux/include
-</verb>
-Note: ``<tt>make config</tt>'' will recreate the <tt>/usr/src/linux</tt>
-link if it isn't there.
-<p>
-
-<sect1>Increasing limits<p>
-The following few <it>example</it> commands may be helpful to those
-wondering how to increase certain soft limits imposed by the kernel:
-<verb>
-echo 4096 > /proc/sys/kernel/file-max
-echo 12288 > /proc/sys/kernel/inode-max
-echo 300 400 500 > /proc/sys/vm/freepages
-</verb>
-<p>
 
 
 <sect> Cloning of Linux Kernels <label id="cloning">
@@ -995,12 +784,8 @@ instructions.
 
 <sect1>What's a loadable module? <p>
 
-These are pieces of kernel code which are not
-linked (included) directly in the kernel. One compiles them separately,
-and can insert and remove them into the running kernel at almost any
-time. Due to its flexibility, this is now the preferred way to code certain
-kernel features. Many popular device drivers, such as the PCMCIA
-drivers and the QIC-80/40 tape driver, are loadable modules.
+See the Modules chapter at <ref id="loadablemodules" name="Loadable Modules">.
+
 <p>
 
 <sect1>How much disk space do I need? <p>
@@ -1165,68 +950,6 @@ frequecy of ``nonstandard'' patches is decreasing significantly.
 
 
 
-<sect>Modules<p>
-Loadable kernel modules can save memory and ease configuration. The scope
-of modules has grown to include filesystems, ethernet card drivers, tape
-drivers, printer drivers, and more.
-<p>
-
-<sect1>Installing the module utilities<p>
-The module utilities are available from wherever you got your kernel
-source as <tt>modutils-x.y.z.tar.gz</tt>; choose the highest
-patchlevel <tt>x.y.z</tt> that is equal to or below that of your current
-kernel. Unpack it with `<tt>tar zxvf modutils-x.y.z.tar.gz</tt>',
-<tt>cd</tt> to the directory it creates (<tt>modutils-x.y.z</tt>), look
-over the <tt>README</tt>, and carry out its installation instructions
-(which is usually something simple, such as <tt>make install</tt>). You
-should now have the programs
-<tt>insmod</tt>, <tt>rmmod</tt>, <tt>ksyms</tt>, <tt>lsmod</tt>, 
-<tt>genksyms</tt>, <tt>modprobe</tt>, and <tt>depmod</tt> in
-<tt>/sbin</tt>. If you wish,
-test out the utilities with the ``hw'' example driver in <tt>insmod</tt>; look
-over the <tt>INSTALL</tt> file in that subdirectory for details.
-<p>
-<tt>insmod</tt> inserts a module into the running kernel. Modules
-usually have a <tt>.o</tt> extension; the example driver mentioned above
-is called <tt>drv_hello.o</tt>, so to insert this, one would say
-`<tt>insmod drv_hello.o</tt>'. To see the modules that the kernel is
-currently using, use <tt>lsmod</tt>. The output looks like this:
-<verb>
-    blah# lsmod
-    Module:        #pages:  Used by:
-    drv_hello          1
-</verb>
-`<tt>drv_hello</tt>' is the name of the module, it uses one page (4k) of
-memory, and no other kernel modules depend on it at the moment. To remove
-this module, use `<tt>rmmod drv_hello</tt>'. Note that <tt>rmmod</tt>
-wants a <it>module name,</it> not a filename; you get this from
-<tt>lsmod</tt>'s listing. The other module utilities' purposes are documented
-in their manual pages.
-<p>
-
-<sect1>Modules distributed with the kernel<p>
-As of version 2.0.30, most of everything is available as a loadable
-modules. To use
-them, first make sure that you don't configure them into the regular
-kernel; that is, don't say <tt>y</tt> to it during `<tt>make config</tt>'.
-Compile a new kernel and reboot with it. Then, <tt>cd</tt> to
-<tt>/usr/src/linux</tt> again, and do a `<tt>make modules</tt>'. This
-compiles all of the modules which you did not specify in the kernel
-configuration, and places links to them in <tt>/usr/src/linux/modules</tt>.
-You can use them straight from that directory or execute `<tt>make
-modules_install</tt>', which installs them in
-<tt>/lib/modules/x.y.z</tt>, where <tt>x.y.z</tt> is the kernel release.
-<p>
-
-This can be especially handy with filesystems. You may not use the minix
-or msdos filesystems frequently. For example, if I encountered an msdos
-(shudder) floppy, I would <tt>insmod /usr/src/linux/modules/msdos.o</tt>,
-and then <tt>rmmod msdos</tt> when finished. This procedure saves about
-50k of RAM in the kernel during normal operation. A small note is in order for
-the minix filesystem: you should <it>always</it> configure it directly into the
-kernel for use in ``rescue'' disks.
-<p>
-
 <sect>Tips and tricks <p>
 
 <sect1>Redirecting output of the make or patch commands <p>
@@ -1324,14 +1047,14 @@ Refer also to other relevant HOWTOs at:
 
 
 
-<sect> Kernel Files Info <label id="kernelinfo">
+<sect> Kernel Files Information <label id="kernelinfo">
 <p>
 This section gives a "very brief" and "introduction" to some of the Linux Kernel System.
 If you have time you can give one reading.
 
 <sect1> vmlinuz and vmlinux <label id="vmlinuz">
 <p>
-This is the Linux kernel executable. This is located at /boot/vmlinuz.
+The vmlinuz is the Linux kernel executable. This is located at /boot/vmlinuz.
 This can be a soft link to something like /boot/vmlinuz-2.4.18-19.8.0
 
 The vmlinux is the uncompressed built kernel,  vmlinuz is the compressed one, 
@@ -1368,6 +1091,37 @@ choose an OS.  So DO NOT touch it.
 
 
 
+<sect1> initrd.img <label id="initrdimg">
+<p>
+See the Appendix A at <ref id="createinitrd" name="Description of initrd.img file">.
+
+
+<sect1> bzImage <label id="bzImagelbl">
+<p>
+The bzImage is the compressed kernel image created with command 'make bzImage' 
+during kernel compile.
+
+
+<sect1> module-info <label id="moduleinfo">
+<p>
+This is created by utils/modlist.
+
+
+<sect1> config <label id="configfiles">
+<p>
+Everytime you compile and install the kernel image in /boot, you should 
+also copy the corresponding config file to /boot area, for documentation
+and future reference. Do NOT touch or edit these files!!
+<code>
+ls -l /boot/config-*
+-rw-r--r--    1 root     root        42111 Sep  4  2002 /boot/config-2.4.18-14
+-rw-r--r--    1 root     root        42328 Jan 26 01:29 /boot/config-2.4.18-19.8.0
+-rw-r--r--    1 root     root        51426 Jan 25 22:21 /boot/config-2.4.18-19.8.0BOOT
+-rw-r--r--    1 root     root        52328 Jan 28 03:22 /boot/config-2.4.18-19.8.0-26mar2003
+</code>
+
+
+
 <sect1> System.map <label id="systemmap">
 <p>
 System.map is a "phone directory" list of function in a particular build  of 
@@ -1694,26 +1448,6 @@ You can also use symlinks:
 
 
 
-<sect1> initrd.img <label id="initrdimg">
-<p>
-See the Appendix A at <ref id="createinitrd" name="Description of initrd.img file">.
-
-
-
-
-<sect1> bzImage <label id="bzImagelbl">
-<p>
-The bzImage is the compressed kernel image created with command 'make bzImage' 
-during kernel compile.
-
-
-
-<sect1> module-info <label id="moduleinfo">
-<p>
-This is created by utils/modlist.
-
-
-
 <sect> Other Formats of this Document
 <p>
 This section is written by 
@@ -1906,28 +1640,21 @@ You can read the latex, LyX output using LyX a X-Windows front end to latex.
 
 <sect> Appendix A - Creating initrd.img file <label id="createinitrd">
 <p>
-The <bf>initrd</bf> is the "initial ramdisk"  It's 
+The <bf>initrd</bf> is the "initial ramdisk".  It is 
 enough files stored in a ramdisk to store needed drivers .  You need the 
-drivers so the kernel can mount / and kick off init.
+drivers so that the kernel can mount /  and kick off init.
 
 You can avoid this if you build your scsi drivers right into the kernel, 
 instead of into modules. (Many persons recommend this).
 
-<sect1> Kernel Docs
-<p>
-To create /boot/initrd.img see the documentation at 
-/usr/src/linux/Documentation/initrd.txt
-and see also
-<url name="Loopback-Root-mini-HOWTO" 
-url="http://www.tldp.org/HOWTO/mini/Loopback-Root-FS-3.html#ss3.3">.
-
-
 <sect1> Using mkinitrd
 <p>
-You can read the mkinitrd man page. It creates an image in a single command. This 
+The mkinitrd utility creates an initrd image in a single command. This 
 is command is peculiar to RedHat. There may be equivalent command of mkinitrd in other 
-distributions of Linux.
-See the next section for the manual method of creating an initrd image.
+distributions of Linux. This is very convenient utility.
+
+You can read the mkinitrd man page. 
+
 <code>
 /sbin/mkinitrd --help   # Or simply type 'mkinitrd --help'
 usage: mkinitrd [--version] [-v] [-f] [--preload <module>]
@@ -1951,6 +1678,16 @@ ls -l initrd-2.4.18-19.8.0custom.img
 cp  ./initrd-2.4.18-19.8.0custom.img   /boot
 </code>
 
+See the following sections for the manual method of creating an initrd image.
+
+<sect1> Kernel Docs
+<p>
+To create /boot/initrd.img see the documentation at 
+/usr/src/linux/Documentation/initrd.txt
+and see also
+<url name="Loopback-Root-mini-HOWTO" 
+url="http://www.tldp.org/HOWTO/mini/Loopback-Root-FS-3.html#ss3.3">.
+
 
 
 <sect1> Linuxman Book
@@ -2359,5 +2096,415 @@ or <url name="firewall.src.rpm" url="http://rpmfind.net/linux/RPM/contrib/noarch
 Refer to HOWTO docs relating to your devices at <url url="http://www.linuxdoc.org">
 
 
+<sect> Appendix E - Troubleshoot Common Mistakes <label id="troubleshoot">
+<p>
+
+<sect1> Compiles OK but does not boot
+<p>
+If the kernel compiles ok but booting never works 
+and it always complains with a kernel panic about /sbin/modprobe.
+
+Solution: You did not create initrd image file. 
+See the Appendix A at <ref id="createinitrd" name="Creating initrd.img file">.
+Also, you must do 'make modules' and 'make  modules_install' in addition to
+creating the initrd image file.
+
+<sect1> The System Hangs at LILO
+<p>
+<bf>Sympton: </bf> After you build the kernel and reboot, the system hangs just before LILO.
+
+<bf>Reason: </bf> Probably you did not set the BIOS to pick up the proper Primary Master IDE and
+Secondary Slave IDE hard disk partition.
+
+<bf>Solution: </bf>Power on the machine and press DEL key to do setup of the BIOS (Basic Input Output system). Select the IDE settings and set proper primary hard disk partition and slave drives.
+When the system boots it looks for the primary IDE hard disk and the Master Boot Record partition.
+It reads the MBR and starts loading the Linux Kernel from the hard disk partition.
+
+
+<sect1> No init found
+<p>
+The following mistake is commited very frequently by new users.
+
+If your new kernel does not boot and you get -
+<code>
+Warning: unable to open an initial console
+Kernel panic: no init found. Try passing init= option to kernel
+</code>
+The problem is that you <bf>did not</bf> set the "root=" parameter properly
+in the /etc/lilo.conf. In my case, I used root=/dev/hda1 which is
+having the root partition "/". You must properly point the root device in your
+lilo.conf, it can be like /dev/hdb2 or /dev/hda7.
+
+The kernel looks for the init command which is located in /sbin/init.
+And /sbin directory lives on the root partition.
+For details see -
+<code>
+bash# man init
+</code>
+See the <ref id="grubconf" name="Appendix C - GRUB details and sample grub.conf"> file
+and see the <ref id="liloconf" name="Appendix B - Sample lilo.conf">.
+
+
+<sect1> Lot of Compile Errors
+<p>
+The 'make', 'make bzImage',  'make modules' or 'make modules_install' 
+gives compile problems.
+You should give 'make mrproper' before doing make.
+<code>
+bash# make mrproper
+</code>
+If this problem persists, then try menuconfig instead of xconfig.
+Sometimes GUI version xconfig causes some problems:
+<code>
+bash# export TERM=VT100
+bash# make menuconfig
+</code>
+
+
+
+
+<sect1> The 'depmod' gives "Unresolved symbol error messages"
+<p>
+When you run <tt>depmod</tt> it gives "Unresolved symbols". A sample error message 
+is given here to demonstrate the case: 
+<code>
+bash$ su - root
+bash# man depmod
+bash# depmod
+depmod: *** Unresolved symbols in /lib/modules/version/kernel/drivers/md/linear.o
+depmod: *** Unresolved symbols in /lib/modules/version/kernel/drivers/md/multipath.o
+depmod: *** Unresolved symbols in /lib/modules/version/kernel/drivers/md/raid0.o
+depmod: *** Unresolved symbols in /lib/modules/version/kernel/drivers/md/raid1.o
+depmod: *** Unresolved symbols in /lib/modules/version/kernel/drivers/md/raid5.o
+</code>
+
+<bf>Reason: </bf> You did not make modules and install the modules after building 
+the new kernel with <tt>"make bzImage"</tt>.
+
+<bf>Solution: </bf> After you build the new kernel, you must do:
+<code>
+bash$ su - root
+bash# cd /usr/src/linux
+bash# make modules
+bash# make modules_install
+</code>
+
+
+
+<sect1> Kernel Does Not Load Module - "Unresolved symbols" Error Messages
+<p>
+When you boot kernel and system tries to load any modules and
+you get "Unresolved symbol : __some_function_name" then it means
+that you did not clean compile the modules and kernel. It is mandatory that
+you should do <bf>make clean</bf> and make the modules. Do this -
+<code>
+	bash# cd /usr/src/linux
+	bash# make dep
+	bash# make clean
+	bash# make mrproper
+	bash# nohup make bzImage &  
+	bash# tail -f nohup.out     (.... to monitor the progress) 
+	bash# make modules
+	bash# make modules_install
+</code>
+
+
+
+<sect1> Kernel fails to load a module 
+<p>
+If the kernel fails to load a module (say loadable module for network card
+or other devices), then you may want to try to build the driver for device
+right into the kernel. Sometimes <it><bf>loadable module will NOT 
+work</bf></it> and the driver
+needs to be built right inside the kernel. For example - some network cards do not
+support loadable module feature - you MUST build the driver of the network card
+right into linux kernel. Hence, in 'make xconfig' you MUST not select loadable
+module for this device.
+
+
+
+
+<sect1> Loadable modules
+<p>
+You can install default loadable modules with -
+
+The step given below may not be required but is needed <bf>ONLY FOR EMERGENCIES</bf> where
+your /lib/modules files are damaged. If you already have 
+the /lib/modules directory and in case you 
+want replace them use the --force to replace the package and 
+select appropriate cpu architecture.
+
+For new versions of linux redhat linux 6.0 and later, the kernel modules are
+included with kernel-2.2*.rpm. Install the loadable modules and the kernel with
+<code>
+	This will list the already installed package.
+bash# rpm -qa | grep -i kernel
+	
+bash# rpm -U --force  /mnt/cdrom/Redhat/RPMS/kernel-2.2.14-5.0.i686.rpm
+(or)
+bash# rpm -U --force  /mnt/cdrom/Redhat/RPMS/kernel-2.2.14-5.0.i586.rpm
+(or)
+bash# rpm -U --force  /mnt/cdrom/Redhat/RPMS/kernel-2.2.14-5.0.i386.rpm
+</code>
+
+This is only for old versions of redhat linux 5.2 and before.
+Boot new kernel and install the loadable 
+modules from RedHat Linux "contrib" cdrom 
+<code>
+bash# rpm -i /mnt/cdrom/contrib/kernel-modules*.rpm 
+....(For old linux systems which do not have insmod pre-installed) 
+</code>
+<p>
+
+<sect1> See Docs
+<p>
+More problems. You can read the /usr/src/linux/README (at least once)
+and also /usr/src/linux/Documentation.
+
+
+<sect1>make clean <p>
+If your new kernel does really weird things after a routine kernel upgrade,
+chances are you forgot to <tt>make clean</tt> before compiling the new
+kernel. Symptoms can be anything from
+your system outright crashing, strange I/O problems, to crummy
+performance. Make sure you do a <tt>make dep</tt>, too.
+<p>
+
+<sect1>Huge or slow kernels <p>
+If your kernel is sucking up a lot of memory, is too large,
+and/or just takes forever to compile even when you've got your new
+Quadbazillium-III/4400 working on it, you've probably got lot of unneeded
+stuff (device drivers, filesystems, etc) configured. If you don't use it,
+don't configure it, because it does take up memory.
+The most obvious symptom of kernel bloat is extreme swapping in and out of
+memory to disk; if your disk is making a lot of noise and it's not one of
+those old Fujitsu Eagles that sound like like a jet landing when turned
+off, look over your kernel configuration.
+<p>
+
+You can find out how much memory the kernel is using by taking the
+total amount of memory in your machine and subtracting from it the
+amount of ``total mem'' in <tt>/proc/meminfo</tt>  or the output of the command
+`<tt>free</tt>'.
+<p>
+
+<sect1>The parallel port doesn't work/my printer doesn't work<p>
+Configuration options for PCs are: First, under the category `General Setup',
+select `Parallel port support' and `PC-style hardware'. Then under
+`Character devices', select `Parallel printer support'.
+<p>
+Then there are the names. Linux 2.2 names the printer devices differently
+than previous releases. The upshot of this is that if you had an <tt>lp1</tt>
+under your old kernel, it's probably an <tt>lp0</tt> under your new one.
+Use `<tt>dmesg</tt>' or look through the logs in <tt>/var/log</tt> to find
+out.
+<p>
+
+<sect1>Kernel doesn't compile <p>
+
+If it does not compile, then it is likely that a patch failed, or your
+source is somehow corrupt. Your version of gcc also might not
+be correct, or could also be corrupt (for example, the include files
+might be in error). Make sure that the symbolic links which
+Linus describes in the <tt>README</tt> are set up correctly. In general, if
+a standard kernel
+does not compile, something is seriously wrong with the system, and 
+reinstallation of certain tools is probably necessary.
+<p>
+
+In some cases, gcc can crash due to hardware problems. The error
+message will be something like ``xxx exited with signal 15'' and it will
+generally look very mysterious. I probably would not mention this, except
+that it happened to me once - I had some bad cache memory, and the compiler
+would occasionally barf at random. Try reinstalling gcc first if you
+experience problems. You should only get suspicious if your kernel compiles
+fine with external cache turned off, a reduced amount of RAM, etc.
+<p>
+
+It tends to disturb people when it's suggested that their hardware has
+problems. Well, I'm not making this up. There is an FAQ for it -- it's at
+<url url="http://www.bitwizard.nl/sig11">.
+<p>
+
+<sect1>New version of the kernel doesn't seem to boot<p>
+
+You did not run LILO, or it is not configured correctly. One thing that
+``got'' me once was a problem in the config file; it said 
+`<tt>boot = /dev/hda1</tt>'
+instead of `<tt>boot = /dev/hda</tt>' (This can be really annoying at first,
+but once you have a working config file, you shouldn't need to
+change it.).
+<p>
+
+<sect1> You forgot to run LILO, or system doesn't boot at all<p>
+
+Ooops! The best thing you can do here is to boot off of a floppy disk or
+CDROM and
+prepare another bootable floppy (such as `<tt>make zdisk</tt>' would do).
+You need to know where your root (<tt>/</tt>) filesystem is and what type
+it is (e.g. second extended, minix). In the example below, you also need
+to know what filesystem your <tt>/usr/src/linux</tt> source
+tree is on, its type, and where it is normally mounted.<p>
+
+In the following example, <tt>/</tt> is <tt>/dev/hda1</tt>, and the
+filesystem which holds <tt>/usr/src/linux</tt>
+is <tt>/dev/hda3</tt>, normally mounted at <tt>/usr</tt>. Both are
+second extended filesystems. The working kernel image in
+<tt>/usr/src/linux/arch/i386/boot</tt> is called <tt>bzImage</tt>.<p>
+
+The idea is that if there is a functioning
+<tt>bzImage</tt>, it is possible to use that
+for the new floppy. Another alternative, which may or may not work better
+(it depends on the particular method in which you messed up your system) is
+discussed after the example.<p>
+
+First, boot from a boot/root disk combo or rescue disk, and
+mount the filesystem which contains the working kernel image:<p>
+
+<verb>
+    mkdir /mnt
+    mount -t ext2 /dev/hda3 /mnt
+</verb>
+
+If <tt>mkdir</tt> tells you that the directory already exists, just ignore
+it. Now, <tt>cd</tt> to the place where the working kernel image was. Note
+that
+<verb>
+/mnt + /usr/src/linux/arch/i386/boot - /usr = /mnt/src/linux/arch/i386/boot
+</verb>
+Place a formatted
+disk in drive ``A:'' (not your boot or root disk!), dump
+the image to the disk, and configure it for your root filesystem:<p>
+
+<verb>
+    cd /mnt/src/linux/arch/i386/boot
+    dd if=bzImage of=/dev/fd0
+    rdev /dev/fd0 /dev/hda1
+</verb>
+
+<tt>cd</tt> to <tt>/</tt> and unmount the normal <tt>/usr</tt> filesystem:<p>
+<verb>
+    cd /
+    umount /mnt
+</verb>
+
+You should now be able to reboot your system as normal from this floppy.
+Don't forget to run lilo (or whatever it was that you did wrong) after
+the reboot!<p>
+
+As mentioned above, there is another common alternative. If you
+happened to have a working kernel image in <tt>/</tt> (<tt>/vmlinuz</tt>
+for example), you can use that for a boot disk. Supposing all of the above
+conditions, and that my kernel image is <tt>/vmlinuz</tt>, just make these
+alterations to the example above: change
+<tt>/dev/hda3</tt> to <tt>/dev/hda1</tt> (the <tt>/</tt> filesystem),
+<tt>/mnt/src/linux</tt> to
+<tt>/mnt</tt>, and <tt>if=bzImage</tt> to <tt>if=vmlinuz</tt>. The
+note explaining how to derive <tt>/mnt/src/linux</tt> may be ignored.
+<p>
+
+Using LILO with big drives (more than 1024 cylinders) can cause problems.
+See the LILO mini-HOWTO or documentation for help on that.
+<p>
+
+<sect1>It says `warning: bdflush not running' <p>
+
+This can be a severe problem. Starting with a kernel release
+after Linux v1.0 (around 20 Apr 1994), a program called `<tt>update</tt>' which
+periodically flushes out the filesystem buffers, was upgraded/replaced. Get
+the sources to `<tt>bdflush</tt>'
+(you should find it where you got your kernel source), and install it (you
+probably want to run your system under the old kernel while doing this). It
+installs itself as `<tt>update</tt>' and after a reboot, the new kernel
+should no longer complain.
+<p>
+
+<sect1>I can't get my IDE/ATAPI CD-ROM drive to work<p>
+Strangely enough, lot of people cannot get their ATAPI drives working,
+probably because there are a number of things that can go wrong.
+<p>
+If your CD-ROM drive is the only device on a particular IDE
+interface, it must be jumpered as ``master'' or ``single.'' Supposedly,
+this is the most common error.
+<p>
+Creative Labs (for one) has put IDE interfaces on their sound cards now.
+However, this leads to the interesting problem that while some people only
+have one interface to being with, many have two IDE interfaces built-in to
+their motherboards (at IRQ15, usually), so a common practice is to make the
+soundblaster interface a third IDE port (IRQ11, or so I'm told).
+<p>
+This causes problems with older Linux versions like 1.3 and below.
+in that versions Linux don't support a third IDE interface.
+To get around this, you have a few choices.<p>
+<p>
+If you have a second IDE port already, chances are that you are not using
+it or it doesn't already have two devices on it. Take the ATAPI drive off
+the sound card and put it on the second interface. You can then disable the
+sound card's interface, which saves an IRQ anyway.
+<p>
+If you don't have a second interface, jumper the sound card's interface
+(not the sound card's sound part) as IRQ15, the second interface. It should
+work.
+<p>
+
+<sect1>It says weird things about obsolete routing requests <p>
+
+Get new versions of the <tt>route</tt> program and any other programs
+which do route manipulation.
+<tt>/usr/include/linux/route.h</tt>  (which is actually a file in
+<tt>/usr/src/linux</tt>) has changed.
+<p>
+
+<sect1>``Not a compressed kernel Image file''<p>
+Don't use the <tt>vmlinux</tt> file created in <tt>/usr/src/linux</tt> as
+your boot image; <tt>[..]/arch/i386/boot/bzImage</tt> is the right
+one.
+<p>
+
+<sect1>Problems with console terminal after upgrade to Linux v1.3.x<p>
+Change the word <tt>dumb</tt> to <tt>linux</tt> in the console termcap
+entry in <tt>/etc/termcap</tt>. You may also have to make a terminfo entry.
+<p>
+
+<sect1> Can't seem to compile things after kernel upgrade<p>
+The linux kernel source includes a number of include files (the things that
+end with <tt>.h</tt>) which are referenced by the standard ones in
+<tt>/usr/include</tt>. They are typically referenced like this (where
+<tt>xyzzy.h</tt> would be something in <tt>/usr/include/linux</tt>):
+<verb>
+    #include <linux/xyzzy.h>
+</verb>
+Normally, there is a link called <tt>linux</tt> in <tt>/usr/include</tt> to
+the <tt>include/linux</tt> directory of your kernel source
+(<tt>/usr/src/linux/include/linux</tt> in the typical system). If this link
+is not there, or points to the wrong place, most things will not compile at
+all. If you decided that the kernel source was taking too much room on the
+disk and deleted it, this will obviously be a problem. Another way it might
+go wrong is with file permissions; if your <tt>root</tt> has a umask
+which doesn't allow other users to see its files by default, and you
+extracted the kernel source without the <tt>p</tt> (preserve filemodes)
+option, those users also won't be able to use the C compiler. Although you
+could use the <tt>chmod</tt> command to fix this, it is probably easier to
+re-extract the include files. You can do this the same way you did the
+whole source at the beginning, only with an additional argument:<p>
+<verb>
+    blah# tar zxvpf linux.x.y.z.tar.gz linux/include
+</verb>
+Note: ``<tt>make config</tt>'' will recreate the <tt>/usr/src/linux</tt>
+link if it isn't there.
+<p>
+
+<sect1>Increasing limits<p>
+The following few <it>example</it> commands may be helpful to those
+wondering how to increase certain soft limits imposed by the kernel:
+<verb>
+echo 4096 > /proc/sys/kernel/file-max
+echo 12288 > /proc/sys/kernel/inode-max
+echo 300 400 500 > /proc/sys/vm/freepages
+</verb>
+<p>
+
+
+
 
 </article>