Lines Matching +full:operating +full:- +full:points +full:- +full:v2
11 --------------
13 Linux is a clone of the operating system Unix, written from scratch by
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
60 ----------------------------
62 - If you install the full sources, put the kernel tarball in a
66 xz -cd linux-5.x.tar.xz | tar xvf -
73 whatever the kernel-du-jour happens to be.
75 - You can also upgrade between 5.x releases by patching. Patches are
78 (linux-5.x) and execute::
80 xz -cd ../patch-5.x.xz | patch -p1
84 the backup files (some-file-name~ or some-file-name.orig), and make sure
85 that there are no failed patches (some-file-name# or some-file-name.rej).
89 (also known as the -stable kernels) are not incremental but instead apply
94 patch -R) **before** applying the 5.0.3 patch. You can read more on this in
95 :ref:`Documentation/process/applying-patches.rst <applying_patches>`.
97 Alternatively, the script patch-kernel can be used to automate this
101 linux/scripts/patch-kernel linux
107 - Make sure you have no stale .o files and dependencies lying around::
115 ---------------------
117 Compiling and running the 5.x kernels requires up-to-date
127 ------------------------------
135 kernel source code: /usr/src/linux-5.x
140 cd /usr/src/linux-5.x
149 ----------------------
158 - Alternative configuration commands are::
232 - NOTES on ``make config``:
234 - Having unnecessary drivers will make the kernel bigger, and can
238 - A kernel with math-emulation compiled in will still use the
244 - The "kernel hacking" configuration details usually result in a
252 --------------------
254 - Make sure you have at least gcc 4.6 available.
259 - Do a ``make`` to create a compressed kernel image. It is also
266 - If you configured any of the parts of the kernel as ``modules``, you
269 - Verbose kernel compile/build output:
282 - Keep a backup kernel handy in case something goes wrong. This is
294 - In order to boot your new kernel, you'll need to copy the kernel
298 - Booting a kernel directly from a floppy without the assistance of a
322 - Reboot with the new kernel and enjoy.
325 -----------------------
327 - If you have problems that seem to be due to kernel bugs, please check
331 them to me (torvalds@linux-foundation.org), and possibly to any other
332 relevant mailing-list or to the newsgroup.
334 - In all bug-reports, *please* tell what kernel you are talking about,
339 - If the bug results in a message like::
356 on making sense of the dump is in Documentation/admin-guide/bug-hunting.rst
358 - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump
365 - In debugging dumps like the above, it helps enormously if you can
392 If you for some reason cannot do the above (you have a pre-compiled
394 possible will help. Please read the :ref:`admin-guide/reporting-bugs.rst <reportingbugs>`
397 - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you
398 cannot change values or set break points.) To do this, first compile the
399 kernel with -g; edit arch/x86/Makefile appropriately, then do a ``make
407 gdb'ing a non-running kernel currently fails because ``gdb`` (wrongly)