On Thu, Jul 27, 2000 at 12:39:51AM -0700, Linus Torvalds wrote:
> Is there some documentation file that I've not updated and that people
> are slavishly following outdated information in? I don't read the
> documentation myself, so I'd never notice ;)
Like someone else pointed out there are many references to
/usr/src/linux in the documentation, but I think the main README file is the
one most people look at. How about this patch for a start?
--- linux-2.4.0-test5-pre6/README Thu Jul 27 14:12:51 2000
+++ linux/README Thu Jul 27 15:00:26 2000
@@ -59,23 +59,22 @@
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.
- 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 +87,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.
@@ -196,15 +193,15 @@
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/bzImage 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/bzImage /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
--// André
- 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/
This archive was generated by hypermail 2b29 : Mon Jul 31 2000 - 21:00:23 EST