patch-2.4.0-test5 linux/README

• Lines: 134
• Date: Thu Jul 27 07:28:30 2000
• Orig file: v2.4.0-test4/linux/README
• Orig date: Fri Jan 7 19:13:21 2000

diff -u --recursive --new-file v2.4.0-test4/linux/README linux/README
@@ -59,23 +59,27 @@
 
 INSTALLING the kernel:
 
- - If you install the full sources, do a
+ - If you install the full sources, put the kernel tarball in a
+   directory where you have permissions (eg. your home directory) and
+   unpack it:
 
-		cd /usr/src
 		gzip -cd linux-2.3.XX.tar.gz | tar xvf -
 
-   to get it all put in place. Replace "XX" with the version number of the
-   latest kernel.
+   Replace "XX" with the version number of the latest kernel.
+
+   Do NOT use the /usr/src/linux area! This area has a (usually
+   incomplete) set of kernel headers that are used by the library header
+   files.  They should match the library, and not get messed up by
+   whatever the kernel-du-jour happens to be.
 
  - You can also upgrade between 2.3.xx releases by patching.  Patches are
    distributed in the traditional gzip and the new bzip2 format.  To
-   install by patching, get all the newer patch files and do
+   install by patching, get all the newer patch files, enter the
+   directory in which you unpacked the kernel source and execute:
 
-		cd /usr/src
 		gzip -cd patchXX.gz | patch -p0
 
    or
-		cd /usr/src
 		bzip2 -dc patchXX.bz2 | patch -p0
 
    (repeat xx for all versions bigger than the version of your current
@@ -88,17 +92,15 @@
    process.  It determines the current kernel version and applies any
    patches found.
 
-		cd /usr/src
-		linux/scripts/patch-kernel
+		linux/scripts/patch-kernel linux
 
-   The default directory for the kernel source is /usr/src/linux, but
-   can be specified as the first argument.  Patches are applied from
-   the current directory, but an alternative directory can be specified
-   as the second argument.
+   The first argument in the command above is the location of the
+   kernel source.  Patches are applied from the current directory, but
+   an alternative directory can be specified as the second argument.
 
  - Make sure you have no stale .o files and dependencies lying around:
 
-		cd /usr/src/linux
+		cd linux
 		make mrproper
 
    You should now have the sources correctly installed.
@@ -169,14 +171,21 @@
    Please note that you can still run a.out user programs with this
    kernel.
 
- - Do a "make zImage" to create a compressed kernel image.  If you want
+ - Do a "make bzImage" to create a compressed kernel image.  If you want
    to make a boot disk (without root filesystem or LILO), insert a floppy
-   in your A: drive, and do a "make zdisk".  It is also possible to do
-   "make zlilo" if you have lilo installed to suit the kernel makefiles,
+   in your A: drive, and do a "make bzdisk".  It is also possible to do
+   "make install" if you have lilo installed to suit the kernel makefiles,
    but you may want to check your particular lilo setup first. 
 
- - If your kernel is too large for "make zImage", use "make bzImage"
-   instead.
+   To do the actual install you have to be root, but none of the normal
+   build should require that. Don't take the name of root in vain.
+
+ - In the unlikely event that your system cannot boot bzImage kernels you
+   can still compile your kernel as zImage. However, since zImage support
+   will be removed at some point in the future in favor of bzImage we
+   encourage people having problems with booting bzImage kernels to report
+   these, with detailed hardware configuration information, to the
+   linux-kernel mailing list and to H. Peter Anvin <hpa+linux@zytor.com>.
 
  - If you configured any of the parts of the kernel as `modules', you
    will have to do "make modules" followed by "make modules_install".
@@ -192,23 +201,23 @@
    do a "make modules_install".
 
  - In order to boot your new kernel, you'll need to copy the kernel
-   image (found in /usr/src/linux/arch/i386/boot/zImage after compilation)
+   image (found in .../linux/arch/i386/boot/bzImage after compilation)
    to the place where your regular bootable kernel is found. 
 
-   For some, this is on a floppy disk, in which case you can "cp
-   /usr/src/linux/arch/i386/boot/zImage /dev/fd0" to make a bootable
-   floppy.  Please note that you can not boot a kernel by
-   directly dumping it to a 720k double-density 3.5" floppy.  In this
-   case, it is highly recommended that you install LILO on your
-   double-density boot floppy or switch to high-density floppies.
+   For some, this is on a floppy disk, in which case you can copy the
+   kernel bzImage file to /dev/fd0 to make a bootable floppy. Please note
+   that you can not boot a kernel by directly dumping it to a 720k
+   double-density 3.5" floppy.  In this case, it is highly recommended
+   that you install LILO on your double-density boot floppy or switch to
+   high-density floppies.
 
    If you boot Linux from the hard drive, chances are you use LILO which
    uses the kernel image as specified in the file /etc/lilo.conf.  The
-   kernel image file is usually /vmlinuz, or /zImage, or /etc/zImage. 
-   To use the new kernel, save a copy of the old image and copy the new
-   image over the old one.  Then, you MUST RERUN LILO to update the
-   loading map!! If you don't, you won't be able to boot the new kernel
-   image. 
+   kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
+   /boot/bzImage.  To use the new kernel, save a copy of the old image
+   and copy the new image over the old one.  Then, you MUST RERUN LILO
+   to update the loading map!! If you don't, you won't be able to boot
+   the new kernel image.
 
    Reinstalling LILO is usually a matter of running /sbin/lilo. 
    You may wish to edit /etc/lilo.conf to specify an entry for your
@@ -260,9 +269,9 @@
    the above example it's due to a bad kernel pointer). More information
    on making sense of the dump is in Documentation/oops-tracing.txt
 
- - You can use the "ksymoops" program to make sense of the dump.  Find
-   the C++ sources under the scripts/ directory to avoid having to do
-   the dump lookup by hand:
+ - You can use the "ksymoops" program to make sense of the dump.  This
+   utility can be downloaded from ftp://ftp.ocs.com.au/pub/ksymoops .
+   Alternately you can do the dump lookup by hand:
 
  - In debugging dumps like the above, it helps enormously if you can
    look up what the EIP value means.  The hex value as such doesn't help