patch-1.3.1 linux/README

• Lines: 64
• Date: Tue Jun 13 10:47:46 1995
• Orig file: v1.3.0/linux/README
• Orig date: Wed Apr 12 08:12:14 1995

diff -u --recursive --new-file v1.3.0/linux/README linux/README
@@ -1,10 +1,24 @@
 
-	Linux kernel release 1.2.xx
+	Linux kernel release 1.3.xx
 
-These are the release notes for linux version 1.2.  Read them carefully,
+These are the release notes for linux version 1.3.  Read them carefully,
 as they tell you what this is all about, explain how to install the
 kernel, and what to do if something goes wrong. 
 
+Linux version 1.3 is a DEVELOPMENT kernel, and not intended for general 
+public use.  Different releases may have various and sometimes severe 
+bugs.  It is *strongly* recommended that you back up the previous kernel 
+before installing any new 1.3.xx release.
+
+If you need to use a proven and stable Linux kernel, please use either 
+1.0.9 or 1.2.xx.  All features which will be in the 1.3.xx releases will 
+be contained in 1.4.xx when the code base has stabilized again.
+
+If you decide to use 1.3, it is recommended that you join the kernel mailing 
+list.  To do this, e-mail majordomo@vger.rutgers.edu, and put in the body 
+of the message "subscribe linux-kernel" or "subscribe linux-kernel-digest" 
+for a daily digest of the mailing list (it is a high-traffic list.)
+
 WHAT IS LINUX?
 
   Linux is a Unix clone for 386/486-based PCs written from scratch by
@@ -33,12 +47,13 @@
  - If you install the full sources, do a
 
 		cd /usr/src
-		gzip -cd linux-1.2.XX.tar.gz | tar xfv -
+		gzip -cd linux-1.3.XX.tar.gz | tar xfv -
 
    to get it all put in place. Replace "XX" with the version number of the
    latest kernel.
 
- - Installing by patching is not worth the effort because the full set of
+ - You can also upgrade between 1.3.xx releases by patching.  For a large
+   set of revisions, it is not worth the effort since the full set of 
    patches is bigger than a new kernel distribution. Instead, get the
    latest full source archive and install as above. Then, get all newer
    patch files, and do
@@ -105,7 +120,8 @@
    versions can have problems compiling newer versions of linux.  If you
    upgrade your compiler, remember to get the new binutils package too
    (for as/ld/nm and company). Do not use gcc-2.6.0; it has a few serious
-   bugs.
+   bugs.  Some problems have been reported occasionally with 2.6.3 as well,
+   so use that version at your own risk.
 
  - do a "make zImage" to create a compressed kernel image.  If you want
    to make a bootdisk (without root filesystem or lilo), insert a floppy
@@ -113,7 +129,9 @@
    "make zlilo" if you have lilo installed to suit the kernel makefiles,
    but you may want to check your particular lilo setup first. 
 
- - keep a backup kernel handy in case something goes wrong. 
+ - keep a backup kernel handy in case something goes wrong.  This is 
+   especially true for the development releases, since each new release
+   contains new code which has not been debugged. 
 
  - 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)