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
236 You can find more information on using the Linux kernel config tools
254 break bad code to find kernel problems (kmalloc()). Thus you
261 - Make sure you have at least gcc 4.9 available.
264 Please note that you can still run a.out user programs with this kernel.
267 possible to do ``make install`` if you have lilo installed to suit the
268 kernel makefiles, but you may want to check your particular lilo setup first.
270 To do the actual install, you have to be root, but none of the normal
273 - If you configured any of the parts of the kernel as ``modules``, you
279 totally silent). However, sometimes you or other kernel developers need
291 contains new code which has not been debugged. Make sure you keep a
292 backup of the modules corresponding to that kernel, as well. If you
294 working kernel, make a backup of your modules directory before you
301 - In order to boot your new kernel, you'll need to copy the kernel
308 If you boot Linux from the hard drive, chances are you use LILO, which
312 and copy the new image over the old one. Then, you MUST RERUN LILO
313 to update the loading map! If you don't, you won't be able to boot
317 You may wish to edit /etc/lilo.conf to specify an entry for your
321 After reinstalling LILO, you should be all set. Shutdown the system,
324 If you ever need to change the default root device, video mode,
334 - If you have problems that seem to be due to kernel bugs, please check
336 with the part of the kernel that you are having trouble with. If there
341 - In all bug-reports, *please* tell what kernel you are talking about,
344 old, please try to tell me when you first noticed it.
359 incomprehensible to you, but it does contain information that may
365 - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump
366 as is, otherwise you will have to use the ``ksymoops`` program to make
370 Alternatively, you can do the dump lookup by hand:
372 - In debugging dumps like the above, it helps enormously if you can
375 kernel setup. What you should do is take the hex value from the EIP
379 To find out the kernel function name, you'll need to find the system
386 This will give you a list of kernel addresses sorted in ascending
390 function addresses (in fact, that is very unlikely), so you can't
391 just 'grep' the list: the list will, however, give you the starting
393 has a starting address lower than the one you are searching for but
394 is followed by a function with a higher address you will find the one
395 you want. In fact, it may be a good idea to include a bit of
399 If you for some reason cannot do the above (you have a pre-compiled
404 - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you
407 clean``. You'll also need to enable CONFIG_PROC_FS (via ``make config``).
409 After you've rebooted with the new kernel, do ``gdb vmlinux /proc/kcore``.
410 You can now use all the usual gdb commands. The command to look up the