Lines Matching refs:the
3 These are the release notes for Linux version 4. Read them carefully,
4 as they tell you what this is all about, explain how to install the
9 Linux is a clone of the operating system Unix, written from scratch by
11 the Net. It aims towards POSIX and Single UNIX Specification compliance.
13 It has all the features you would expect in a modern fully-fledged Unix,
18 It is distributed under the GNU General Public License - see the
24 today Linux also runs on (at least) the Compaq Alpha AXP, Sun SPARC and
30 as long as they have a paged memory management unit (PMMU) and a port of the
34 Linux has also been ported to itself. You can now run the kernel as a
40 the Internet and in books, both Linux-specific and pertaining to
41 general UNIX questions. I'd recommend looking into the documentation
42 subdirectories on any Linux FTP site for the LDP (Linux Documentation
43 Project) books. This README is not meant to be documentation on the
46 - There are various README files in the Documentation/ subdirectory:
49 is contained in each file. Please read the Changes file, as it
50 contains information about the problems, which may result by upgrading
57 or "make mandocs" will render the documentation in the requested format.
59 INSTALLING the kernel source:
61 - If you install the full sources, put the kernel tarball in a
67 Replace "X" with the version number of the latest kernel.
69 Do NOT use the /usr/src/linux area! This area has a (usually
70 incomplete) set of kernel headers that are used by the library header
71 files. They should match the library, and not get messed up by
72 whatever the kernel-du-jour happens to be.
75 distributed in the xz format. To install by patching, get all the
76 newer patch files, enter the top level directory of the kernel source
81 Replace "x" for all versions bigger than the version "X" of your current
83 the backup files (some-file-name~ or some-file-name.orig), and make sure
87 Unlike patches for the 4.x kernels, patches for the 4.x.y kernels
88 (also known as the -stable kernels) are not incremental but instead apply
89 directly to the base 4.x kernel. For example, if your base kernel is 4.0
90 and you want to apply the 4.0.3 patch, you must not first apply the 4.0.1
92 want to jump to 4.0.3, you must first reverse the 4.0.2 patch (that is,
93 patch -R) _before_ applying the 4.0.3 patch. You can read more on this in
96 Alternatively, the script patch-kernel can be used to automate this
97 process. It determines the current kernel version and applies any
102 The first argument in the command above is the location of the
103 kernel source. Patches are applied from the current directory, but
104 an alternative directory can be specified as the second argument.
111 You should now have the sources correctly installed.
115 Compiling and running the 4.x kernels requires up-to-date
117 Documentation/Changes for the minimum version numbers required
124 BUILD directory for the kernel:
126 When compiling the kernel, all output files will per default be
127 stored together with the kernel source code.
128 Using the option "make O=output/dir" allow you to specify an alternate
129 place for the output files (including .config).
135 To configure and build the kernel, use:
142 Please note: If the 'O=output/dir' option is used, then it must be
145 CONFIGURING the kernel:
149 odd problems will turn up if the configuration files are not set up
152 only ask you for the answers to new questions.
166 "make oldconfig" Default all questions based on the contents of
171 Like above, but avoids cluttering the screen
173 Additionally updates the dependencies.
179 "make defconfig" Create a ./.config file by using the default
182 depending on the architecture.
185 Create a ./.config file by using the default
207 option that is not needed for the loaded modules.
210 store the lsmod of that machine into a file
223 You can find more information on using the Linux kernel config tools
228 - Having unnecessary drivers will make the kernel bigger, and can
232 - Compiling the kernel with "Processor type" set higher than 386
236 - A kernel with math-emulation compiled in will still use the
237 coprocessor if one is present: the math emulation will just
243 bigger or slower kernel (or both), and can even make the kernel
246 should probably answer 'n' to the questions for "development",
249 COMPILING the kernel:
257 possible to do "make install" if you have lilo installed to suit the
260 To do the actual install, you have to be root, but none of the normal
261 build should require that. Don't take the name of root in vain.
263 - If you configured any of the parts of the kernel as `modules', you
268 Normally, the kernel build system runs in a fairly quiet mode (but not
272 "V=1" in the "make" command. E.g.:
276 To have the build system also tell the reason for the rebuild of each
280 especially true for the development releases, since each new release
282 backup of the modules corresponding to that kernel, as well. If you
283 are installing a new kernel with the same version number as your
287 Alternatively, before compiling, use the kernel config option
288 "LOCALVERSION" to append a unique suffix to the regular kernel version.
289 LOCALVERSION can be set in the "General Setup" menu.
291 - In order to boot your new kernel, you'll need to copy the kernel
293 to the place where your regular bootable kernel is found.
295 - Booting a kernel directly from a floppy without the assistance of a
298 If you boot Linux from the hard drive, chances are you use LILO, which
299 uses the kernel image as specified in the file /etc/lilo.conf. The
301 /boot/bzImage. To use the new kernel, save a copy of the old image
302 and copy the new image over the old one. Then, you MUST RERUN LILO
303 to update the loading map!! If you don't, you won't be able to boot
304 the new kernel image.
308 old kernel image (say, /vmlinux.old) in case the new one does not
309 work. See the LILO docs for more information.
311 After reinstalling LILO, you should be all set. Shutdown the system,
314 If you ever need to change the default root device, video mode,
315 ramdisk size, etc. in the kernel image, use the 'rdev' program (or
316 alternatively the LILO boot options when appropriate). No need to
317 recompile the kernel to change these parameters.
319 - Reboot with the new kernel and enjoy.
324 the file MAINTAINERS to see if there is a particular person associated
325 with the part of the kernel that you are having trouble with. If there
326 isn't anyone listed there, then the second best thing is to mail
328 relevant mailing-list or to the newsgroup.
331 how to duplicate the problem, and what your setup is (use your common
332 sense). If the problem is new, tell me so, and if the problem is
335 - If the bug results in a message like
349 help debugging the problem. The text above the dump is also
350 important: it tells something about why the kernel dumped code (in
351 the above example, it's due to a bad kernel pointer). More information
352 on making sense of the dump is in Documentation/oops-tracing.txt
354 - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump
355 as is, otherwise you will have to use the "ksymoops" program to make
356 sense of the dump (but compiling with CONFIG_KALLSYMS is usually preferred).
359 Alternatively, you can do the dump lookup by hand:
361 - In debugging dumps like the above, it helps enormously if you can
362 look up what the EIP value means. The hex value as such doesn't help
364 kernel setup. What you should do is take the hex value from the EIP
365 line (ignore the "0010:"), and look it up in the kernel namelist to
366 see which kernel function contains the offending address.
368 To find out the kernel function name, you'll need to find the system
369 binary associated with the kernel that exhibited the symptom. This is
370 the file 'linux/vmlinux'. To extract the namelist and match it against
371 the EIP from the kernel crash, do:
376 order, from which it is simple to find the function that contains the
377 offending address. Note that the address given by the kernel
378 debugging messages will not necessarily match exactly with the
380 just 'grep' the list: the list will, however, give you the starting
381 point of each kernel function, so by looking for the function that
382 has a starting address lower than the one you are searching for but
383 is followed by a function with a higher address you will find the one
385 "context" in your problem report, giving a few lines around the
388 If you for some reason cannot do the above (you have a pre-compiled
390 possible will help. Please read the REPORTING-BUGS document for details.
393 cannot change values or set break points.) To do this, first compile the
397 After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore".
398 You can now use all the usual gdb commands. The command to look up the
399 point where your system crashed is "l *0xXXXXXXXX". (Replace the XXXes
400 with the EIP value.)
403 disregards the starting offset for which the kernel is compiled.