Lines Matching refs:you
4 as they tell you what this is all about, explain how to install the
13 It has all the features you would expect in a modern fully-fledged Unix,
61 - If you install the full sources, put the kernel tarball in a
62 directory where you have permissions (eg. your home directory) and
89 source tree, _in_order_) and you should be ok. You may want to remove
91 failed patches (xxx# or xxx.rej). If there are, either you or me has
109 - If you are upgrading between releases using the stable series patches
112 example, if your base kernel is 2.6.12 and you want to apply the
113 2.6.12.3 patch, you do not and indeed must not first apply the
114 2.6.12.1 and 2.6.12.2 patches. Similarly, if you are running kernel
115 version 2.6.12.2 and want to jump to 2.6.12.3, you must first
120 - Make sure you have no stale .o files and dependencies lying around:
135 you can just update packages when obvious problems arise during
142 Using the option "make O=output/dir" allow you to specify an alternate
159 Do not skip this step even if you are only upgrading one minor
162 as expected. If you want to carry your existing configuration to a
164 only ask you for the answers to new questions.
218 break bad code to find kernel problems (kmalloc()). Thus you
224 - Make sure you have at least gcc 3.2 available.
227 Please note that you can still run a.out user programs with this kernel.
230 possible to do "make install" if you have lilo installed to suit the
231 kernel makefiles, but you may want to check your particular lilo setup first.
233 To do the actual install you have to be root, but none of the normal
236 - If you configured any of the parts of the kernel as `modules', you
242 totally silent). However, sometimes you or other kernel developers need
254 contains new code which has not been debugged. Make sure you keep a
255 backup of the modules corresponding to that kernel, as well. If you
257 working kernel, make a backup of your modules directory before you
263 - In order to boot your new kernel, you'll need to copy the kernel
270 If you boot Linux from the hard drive, chances are you use LILO which
274 and copy the new image over the old one. Then, you MUST RERUN LILO
275 to update the loading map!! If you don't, you won't be able to boot
283 After reinstalling LILO, you should be all set. Shutdown the system,
286 If you ever need to change the default root device, video mode,
295 - If you have problems that seem to be due to kernel bugs, please check
297 with the part of the kernel that you are having trouble with. If there
302 - In all bug-reports, *please* tell what kernel you are talking about,
305 old, please try to tell me when you first noticed it.
320 incomprehensible to you, but it does contain information that may
326 - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump
327 as is, otherwise you will have to use the "ksymoops" program to make
331 Alternately you can do the dump lookup by hand:
333 - In debugging dumps like the above, it helps enormously if you can
336 kernel setup. What you should do is take the hex value from the EIP
340 To find out the kernel function name, you'll need to find the system
347 This will give you a list of kernel addresses sorted in ascending
351 function addresses (in fact, that is very unlikely), so you can't
352 just 'grep' the list: the list will, however, give you the starting
354 has a starting address lower than the one you are searching for but
355 is followed by a function with a higher address you will find the one
356 you want. In fact, it may be a good idea to include a bit of
360 If you for some reason cannot do the above (you have a pre-compiled
364 - Alternately, you can use gdb on a running kernel. (read-only; i.e. you
369 After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore".