Lines Matching full:you
7 as they tell you what this is all about, explain how to install the
17 It has all the features you would expect in a modern fully-fledged Unix,
39 Linux has also been ported to itself. You can now run the kernel as a
62 - If you install the full sources, put the kernel tarball in a
63 directory where you have permissions (e.g. your home directory) and
75 - You can also upgrade between 5.x releases by patching. Patches are
83 source tree, **in_order**, and you should be ok. You may want to remove
86 If there are, either you or I have made a mistake.
91 and you want to apply the 5.0.3 patch, you must not first apply the 5.0.1
92 and 5.0.2 patches. Similarly, if you are running kernel version 5.0.2 and
93 want to jump to 5.0.3, you must first reverse the 5.0.2 patch (that is,
94 patch -R) **before** applying the 5.0.3 patch. You can read more on this in
107 - Make sure you have no stale .o files and dependencies lying around::
112 You should now have the sources correctly installed.
123 you can just update packages when obvious problems arise during
131 Using the option ``make O=output/dir`` allows you to specify an alternate
151 Do not skip this step even if you are only upgrading one minor
154 as expected. If you want to carry your existing configuration to a
156 only ask you for the answers to new questions.
212 Also, you can preserve modules in certain folders
226 all module options to built in (=y) options. You can
237 You can find more information on using the Linux kernel config tools
255 break bad code to find kernel problems (kmalloc()). Thus you
262 - Make sure you have at least gcc 5.1 available.
265 Please note that you can still run a.out user programs with this kernel.
268 possible to do ``make install`` if you have lilo installed to suit the
269 kernel makefiles, but you may want to check your particular lilo setup first.
271 To do the actual install, you have to be root, but none of the normal
274 - If you configured any of the parts of the kernel as ``modules``, you
280 totally silent). However, sometimes you or other kernel developers need
292 contains new code which has not been debugged. Make sure you keep a
293 backup of the modules corresponding to that kernel, as well. If you
295 working kernel, make a backup of your modules directory before you
302 - In order to boot your new kernel, you'll need to copy the kernel
309 If you boot Linux from the hard drive, chances are you use LILO, which
313 and copy the new image over the old one. Then, you MUST RERUN LILO
314 to update the loading map! If you don't, you won't be able to boot
318 You may wish to edit /etc/lilo.conf to specify an entry for your
322 After reinstalling LILO, you should be all set. Shutdown the system,
325 If you ever need to change the default root device, video mode,
335 - If you have problems that seem to be due to kernel bugs, please check
337 with the part of the kernel that you are having trouble with. If there
342 - In all bug-reports, *please* tell what kernel you are talking about,
345 old, please try to tell me when you first noticed it.
360 incomprehensible to you, but it does contain information that may
366 - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump
367 as is, otherwise you will have to use the ``ksymoops`` program to make
371 Alternatively, you can do the dump lookup by hand:
373 - In debugging dumps like the above, it helps enormously if you can
376 kernel setup. What you should do is take the hex value from the EIP
380 To find out the kernel function name, you'll need to find the system
387 This will give you a list of kernel addresses sorted in ascending
391 function addresses (in fact, that is very unlikely), so you can't
392 just 'grep' the list: the list will, however, give you the starting
394 has a starting address lower than the one you are searching for but
395 is followed by a function with a higher address you will find the one
396 you want. In fact, it may be a good idea to include a bit of
400 If you for some reason cannot do the above (you have a pre-compiled
405 - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you
408 clean``. You'll also need to enable CONFIG_PROC_FS (via ``make config``).
410 After you've rebooted with the new kernel, do ``gdb vmlinux /proc/kcore``.
411 You can now use all the usual gdb commands. The command to look up the