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