There is a difference in the documentation: Documentation/Changes says you
need at least gcc-2.7.2.3 for 2.2, README says that version 2.7.0 is
okay. (Changed to 2.7.2.3)
The Ramdisk size is adjusted dynamically since the new ramdisk code in 1.3.
Is it changeable by rdev any more? (Removed the ramdisk example)
All examples are for the i386 CPU (cp ..i386/boot/zImage..). How is it on
other architectures? I don't know, I think you don't need a compressed
image at all? (added "in case of a i386 compatible CPU")
ksymoops is now a C programm
The rest is 2.1 -> 2.2 cosmetic
START OF PATCH
--- linux/README~ Sun Jan 3 10:49:41 1999
+++ linux/README Mon Jan 4 16:17:23 1999
@@ -48,12 +48,12 @@
- If you install the full sources, do a
cd /usr/src
- gzip -cd linux-2.1.XX.tar.gz | tar xfv -
+ gzip -cd linux-2.2.XX.tar.gz | tar xfv -
to get it all put in place. Replace "XX" with the version number of the
latest kernel.
- - You can also upgrade between 2.1.xx releases by patching. Patches are
+ - You can also upgrade between 2.2.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
@@ -91,7 +91,7 @@
SOFTWARE REQUIREMENTS
- Compiling and running the 2.1.x kernels requires up-to-date
+ Compiling and running the 2.2.x kernels requires up-to-date
versions of various software packages. Consult
./Documentation/Changes for the minimum version numbers required
and how to get updates for these packages. Beware that using
@@ -145,7 +145,7 @@
COMPILING the kernel:
- - Make sure you have gcc-2.7.0 or newer available. It seems older gcc
+ - Make sure you have gcc-2.7.2.3 or newer available. It seems older gcc
versions can have problems compiling newer versions of Linux. This
is mainly because the older compilers can only generate "a.out"-format
executables. As of Linux 2.1.0, the kernel must be compiled as an
@@ -178,8 +178,9 @@
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)
- to the place where your regular bootable kernel is found.
+ image (in case of a 386 compatible CPU found in
+ /usr/src/linux/arch/i386/boot/zImage 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
@@ -204,10 +205,10 @@
After reinstalling LILO, you should be all set. Shutdown the system,
reboot, and enjoy!
- If you ever need to change the default root device, video mode,
- ramdisk size, etc. in the kernel image, use the 'rdev' program (or
- alternatively the LILO boot options when appropriate). No need to
- recompile the kernel to change these parameters.
+ If you ever need to change the default root device, video mode etc. in
+ the kernel image, use the 'rdev' program (or alternatively the LILO boot
+ options when appropriate). No need to recompile the kernel to change
+ these parameters.
- Reboot with the new kernel and enjoy.
@@ -247,8 +248,8 @@
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:
+ the C sources under the scripts/ksymoops-0.6 directory to avoid having to
+ 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
END OF PATCH
Regards,
Carsten
-- What happens if a big asteroid hits Earth? Judging from simulations involving a sledge hammer and a laboratory frog, we can assume it will be pretty bad. Carsten Gross carsten@sol.wohnheim.uni-ulm.de Wohnheim Heilmeyersteige Sebastian Kneipp Weg 6, 89075 Ulm
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/