Lines Matching +full:directory +full:- +full:based
11 --------------
14 Linus Torvalds with assistance from a loosely-knit team of hackers across
17 It has all the features you would expect in a modern fully-fledged Unix,
19 loading, shared copy-on-write executables, proper memory management,
22 It is distributed under the GNU General Public License v2 - see the
26 -----------------------------
28 Although originally developed first for 32-bit x86-based PCs (386 or higher),
31 IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64 Xtensa, and
34 Linux is easily portable to most general-purpose 32- or 64-bit architectures
40 userspace application - this is called UserMode Linux (UML).
43 -------------
45 - There is a lot of documentation available both in electronic form on
46 the Internet and in books, both Linux-specific and pertaining to
52 - There are various README files in the Documentation/ subdirectory:
53 these typically contain kernel-specific installation notes for some
54 drivers for example. See Documentation/00-INDEX for a list of what
61 ----------------------------
63 - If you install the full sources, put the kernel tarball in a
64 directory where you have permissions (e.g. your home directory) and
67 xz -cd linux-4.X.tar.xz | tar xvf -
74 whatever the kernel-du-jour happens to be.
76 - You can also upgrade between 4.x releases by patching. Patches are
78 newer patch files, enter the top level directory of the kernel source
79 (linux-4.X) and execute::
81 xz -cd ../patch-4.x.xz | patch -p1
85 the backup files (some-file-name~ or some-file-name.orig), and make sure
86 that there are no failed patches (some-file-name# or some-file-name.rej).
90 (also known as the -stable kernels) are not incremental but instead apply
95 patch -R) **before** applying the 4.0.3 patch. You can read more on this in
96 :ref:`Documentation/process/applying-patches.rst <applying_patches>`.
98 Alternatively, the script patch-kernel can be used to automate this
102 linux/scripts/patch-kernel linux
105 kernel source. Patches are applied from the current directory, but
106 an alternative directory can be specified as the second argument.
108 - Make sure you have no stale .o files and dependencies lying around::
116 ---------------------
118 Compiling and running the 4.x kernels requires up-to-date
127 Build directory for the kernel
128 ------------------------------
136 kernel source code: /usr/src/linux-4.X
137 build directory: /home/name/build/kernel
141 cd /usr/src/linux-4.X
150 ----------------------
159 - Alternative configuration commands are::
163 "make menuconfig" Text based color menus, radiolists & dialogs.
165 "make nconfig" Enhanced text based color menus.
167 "make xconfig" Qt based configuration tool.
169 "make gconfig" GTK+ based configuration tool.
171 "make oldconfig" Default all questions based on the contents of
205 "make localmodconfig" Create a config based on current config and
233 - NOTES on ``make config``:
235 - Having unnecessary drivers will make the kernel bigger, and can
239 - A kernel with math-emulation compiled in will still use the
245 - The "kernel hacking" configuration details usually result in a
253 --------------------
255 - Make sure you have at least gcc 3.2 available.
260 - Do a ``make`` to create a compressed kernel image. It is also
267 - If you configured any of the parts of the kernel as ``modules``, you
270 - Verbose kernel compile/build output:
283 - Keep a backup kernel handy in case something goes wrong. This is
288 working kernel, make a backup of your modules directory before you
295 - In order to boot your new kernel, you'll need to copy the kernel
299 - Booting a kernel directly from a floppy without the assistance of a
323 - Reboot with the new kernel and enjoy.
326 -----------------------
328 - If you have problems that seem to be due to kernel bugs, please check
332 them to me (torvalds@linux-foundation.org), and possibly to any other
333 relevant mailing-list or to the newsgroup.
335 - In all bug-reports, *please* tell what kernel you are talking about,
340 - If the bug results in a message like::
357 on making sense of the dump is in Documentation/admin-guide/bug-hunting.rst
359 - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump
366 - In debugging dumps like the above, it helps enormously if you can
393 If you for some reason cannot do the above (you have a pre-compiled
395 possible will help. Please read the :ref:`admin-guide/reporting-bugs.rst <reportingbugs>`
398 - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you
400 kernel with -g; edit arch/x86/Makefile appropriately, then do a ``make
408 gdb'ing a non-running kernel currently fails because ``gdb`` (wrongly)