Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
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: Jesper Juhl <jj@chaosbits.net>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
+18
-25
+18
-25
Documentation/Changes
+18
-25
Documentation/Changes
···
2
2
=====
3
3
4
4
This document is designed to provide a list of the minimum levels of
5
-
software necessary to run the 2.6 kernels, as well as provide brief
6
-
instructions regarding any other "Gotchas" users may encounter when
7
-
trying life on the Bleeding Edge. If upgrading from a pre-2.4.x
8
-
kernel, please consult the Changes file included with 2.4.x kernels for
9
-
additional information; most of that information will not be repeated
10
-
here. Basically, this document assumes that your system is already
11
-
functional and running at least 2.4.x kernels.
5
+
software necessary to run the 3.0 kernels.
12
6
13
7
This document is originally based on my "Changes" file for 2.0.x kernels
14
8
and therefore owes credit to the same people as that file (Jared Mauch,
···
16
22
encountered a bug! If you're unsure what version you're currently
17
23
running, the suggested command should tell you.
18
24
19
-
Again, keep in mind that this list assumes you are already
20
-
functionally running a Linux 2.4 kernel. Also, not all tools are
21
-
necessary on all systems; obviously, if you don't have any ISDN
22
-
hardware, for example, you probably needn't concern yourself with
23
-
isdn4k-utils.
25
+
Again, keep in mind that this list assumes you are already functionally
26
+
running a Linux kernel. Also, not all tools are necessary on all
27
+
systems; obviously, if you don't have any ISDN hardware, for example,
28
+
you probably needn't concern yourself with isdn4k-utils.
24
29
25
30
o Gnu C 3.2 # gcc --version
26
31
o Gnu make 3.80 # make --version
···
107
114
108
115
If the unthinkable happens and your kernel oopses, you may need the
109
116
ksymoops tool to decode it, but in most cases you don't.
110
-
In the 2.6 kernel it is generally preferred to build the kernel with
111
-
CONFIG_KALLSYMS so that it produces readable dumps that can be used as-is
112
-
(this also produces better output than ksymoops).
113
-
If for some reason your kernel is not build with CONFIG_KALLSYMS and
114
-
you have no way to rebuild and reproduce the Oops with that option, then
115
-
you can still decode that Oops with ksymoops.
117
+
It is generally preferred to build the kernel with CONFIG_KALLSYMS so
118
+
that it produces readable dumps that can be used as-is (this also
119
+
produces better output than ksymoops). If for some reason your kernel
120
+
is not build with CONFIG_KALLSYMS and you have no way to rebuild and
121
+
reproduce the Oops with that option, then you can still decode that Oops
122
+
with ksymoops.
116
123
117
124
Module-Init-Tools
118
125
-----------------
···
254
261
NFS-utils
255
262
---------
256
263
257
-
In 2.4 and earlier kernels, the nfs server needed to know about any
258
-
client that expected to be able to access files via NFS. This
264
+
In ancient (2.4 and earlier) kernels, the nfs server needed to know
265
+
about any client that expected to be able to access files via NFS. This
259
266
information would be given to the kernel by "mountd" when the client
260
267
mounted the filesystem, or by "exportfs" at system startup. exportfs
261
268
would take information about active clients from /var/lib/nfs/rmtab.
···
265
272
fail-over. Even when the system is working well, rmtab suffers from
266
273
getting lots of old entries that never get removed.
267
274
268
-
With 2.6 we have the option of having the kernel tell mountd when it
269
-
gets a request from an unknown host, and mountd can give appropriate
270
-
export information to the kernel. This removes the dependency on
271
-
rmtab and means that the kernel only needs to know about currently
272
-
active clients.
275
+
With modern kernels we have the option of having the kernel tell mountd
276
+
when it gets a request from an unknown host, and mountd can give
277
+
appropriate export information to the kernel. This removes the
278
+
dependency on rmtab and means that the kernel only needs to know about
279
+
currently active clients.
273
280
274
281
To enable this new functionality, you need to:
275
282