Commit 5adaf851 authored by Linus Torvalds's avatar Linus Torvalds

Documentation/Changes: remove some really obsolete text

That file harkens back to the days of the big 2.4 -> 2.6 version jump,
and was based even then on older versions.  Some of it is just obsolete,
and Jesper Juhl points out that it talks about kernel versions 2.6 and
should be updated to 3.0.

Remove some obsolete text, and re-phrase some other to not be 2.6-specific.
Reported-by: default avatarJesper Juhl <jj@chaosbits.net>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent c15000b4
...@@ -2,13 +2,7 @@ Intro ...@@ -2,13 +2,7 @@ Intro
===== =====
This document is designed to provide a list of the minimum levels of This document is designed to provide a list of the minimum levels of
software necessary to run the 2.6 kernels, as well as provide brief software necessary to run the 3.0 kernels.
instructions regarding any other "Gotchas" users may encounter when
trying life on the Bleeding Edge. If upgrading from a pre-2.4.x
kernel, please consult the Changes file included with 2.4.x kernels for
additional information; most of that information will not be repeated
here. Basically, this document assumes that your system is already
functional and running at least 2.4.x kernels.
This document is originally based on my "Changes" file for 2.0.x kernels This document is originally based on my "Changes" file for 2.0.x kernels
and therefore owes credit to the same people as that file (Jared Mauch, and therefore owes credit to the same people as that file (Jared Mauch,
...@@ -22,11 +16,10 @@ Upgrade to at *least* these software revisions before thinking you've ...@@ -22,11 +16,10 @@ Upgrade to at *least* these software revisions before thinking you've
encountered a bug! If you're unsure what version you're currently encountered a bug! If you're unsure what version you're currently
running, the suggested command should tell you. running, the suggested command should tell you.
Again, keep in mind that this list assumes you are already Again, keep in mind that this list assumes you are already functionally
functionally running a Linux 2.4 kernel. Also, not all tools are running a Linux kernel. Also, not all tools are necessary on all
necessary on all systems; obviously, if you don't have any ISDN systems; obviously, if you don't have any ISDN hardware, for example,
hardware, for example, you probably needn't concern yourself with you probably needn't concern yourself with isdn4k-utils.
isdn4k-utils.
o Gnu C 3.2 # gcc --version o Gnu C 3.2 # gcc --version
o Gnu make 3.80 # make --version o Gnu make 3.80 # make --version
...@@ -114,12 +107,12 @@ Ksymoops ...@@ -114,12 +107,12 @@ Ksymoops
If the unthinkable happens and your kernel oopses, you may need the If the unthinkable happens and your kernel oopses, you may need the
ksymoops tool to decode it, but in most cases you don't. ksymoops tool to decode it, but in most cases you don't.
In the 2.6 kernel it is generally preferred to build the kernel with It is generally preferred to build the kernel with CONFIG_KALLSYMS so
CONFIG_KALLSYMS so that it produces readable dumps that can be used as-is that it produces readable dumps that can be used as-is (this also
(this also produces better output than ksymoops). produces better output than ksymoops). If for some reason your kernel
If for some reason your kernel is not build with CONFIG_KALLSYMS and is not build with CONFIG_KALLSYMS and you have no way to rebuild and
you have no way to rebuild and reproduce the Oops with that option, then reproduce the Oops with that option, then you can still decode that Oops
you can still decode that Oops with ksymoops. with ksymoops.
Module-Init-Tools Module-Init-Tools
----------------- -----------------
...@@ -261,8 +254,8 @@ needs to be recompiled or (preferably) upgraded. ...@@ -261,8 +254,8 @@ needs to be recompiled or (preferably) upgraded.
NFS-utils NFS-utils
--------- ---------
In 2.4 and earlier kernels, the nfs server needed to know about any In ancient (2.4 and earlier) kernels, the nfs server needed to know
client that expected to be able to access files via NFS. This about any client that expected to be able to access files via NFS. This
information would be given to the kernel by "mountd" when the client information would be given to the kernel by "mountd" when the client
mounted the filesystem, or by "exportfs" at system startup. exportfs mounted the filesystem, or by "exportfs" at system startup. exportfs
would take information about active clients from /var/lib/nfs/rmtab. would take information about active clients from /var/lib/nfs/rmtab.
...@@ -272,11 +265,11 @@ which is not always easy, particularly when trying to implement ...@@ -272,11 +265,11 @@ which is not always easy, particularly when trying to implement
fail-over. Even when the system is working well, rmtab suffers from fail-over. Even when the system is working well, rmtab suffers from
getting lots of old entries that never get removed. getting lots of old entries that never get removed.
With 2.6 we have the option of having the kernel tell mountd when it With modern kernels we have the option of having the kernel tell mountd
gets a request from an unknown host, and mountd can give appropriate when it gets a request from an unknown host, and mountd can give
export information to the kernel. This removes the dependency on appropriate export information to the kernel. This removes the
rmtab and means that the kernel only needs to know about currently dependency on rmtab and means that the kernel only needs to know about
active clients. currently active clients.
To enable this new functionality, you need to: To enable this new functionality, you need to:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment