Lines Matching +full:bootloader +full:- +full:config

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
60 ----------------------------
62 - If you install the full sources, put the kernel tarball in a
66 xz -cd linux-6.x.tar.xz | tar xvf -
73 whatever the kernel-du-jour happens to be.
75 - You can also upgrade between 6.x releases by patching. Patches are
78 (linux-6.x) and execute::
80 xz -cd ../patch-6.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 6.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 6.x kernels requires up-to-date
127 ------------------------------
132 place for the output files (including .config).
135 kernel source code: /usr/src/linux-6.x
140 cd /usr/src/linux-6.x
149 ----------------------
158 - Alternative configuration commands are::
160 "make config" Plain text interface.
171 your existing ./.config file and asking about
172 new config symbols.
178 "make defconfig" Create a ./.config file by using the default
184 Create a ./.config file by using the default
191 Create a ./.config file by setting symbol
195 Create a ./.config file by setting symbol
198 "make allnoconfig" Create a ./.config file by setting symbol
201 "make randconfig" Create a ./.config file by setting symbol
204 "make localmodconfig" Create a config based on current config and
229 "make kvm_guest.config" Enable additional options for kvm guest kernel
232 "make xen.config" Enable additional options for xen dom0 guest kernel
237 You can find more information on using the Linux kernel config tools
240 - NOTES on ``make config``:
242 - Having unnecessary drivers will make the kernel bigger, and can
246 - A kernel with math-emulation compiled in will still use the
252 - The "kernel hacking" configuration details usually result in a
260 --------------------
262 - Make sure you have at least gcc 5.1 available.
265 - Do a ``make`` to create a compressed kernel image. It is also possible to do
274 - If you configured any of the parts of the kernel as ``modules``, you
277 - Verbose kernel compile/build output:
290 - Keep a backup kernel handy in case something goes wrong. This is
298 Alternatively, before compiling, use the kernel config option
302 - In order to boot your new kernel, you'll need to copy the kernel
306 - Booting a kernel directly from a storage device without the assistance
307 of a bootloader such as LILO or GRUB, is no longer supported in BIOS
308 (non-EFI systems). On UEFI/EFI systems, however, you can use EFISTUB
311 bootloader as difficulties can arise with multiple kernels and secure boot.
313 see "Documentation/admin-guide/efi-stub.rst".
315 - It's important to note that as of 2016 LILO (LInux LOader) is no longer in
318 systemd-boot, or EFISTUB. For various reasons, it's not recommended to use
321 - Chances are your distribution includes an install script and running
323 you'll have to identify your bootloader and reference its documentation or
327 ------------------------
330 - If you use LILO the kernel images are specified in the file /etc/lilo.conf.
336 - Reinstalling LILO is usually a matter of running /sbin/lilo. You may wish
341 - After reinstalling LILO, you should be all set. Shutdown the system,
344 - If you ever need to change the default root device, video mode, etc. in the
345 kernel image, use your bootloader's boot options where appropriate. No need
348 - Reboot with the new kernel and enjoy.
352 -----------------------
355 instructions at 'Documentation/admin-guide/reporting-issues.rst'.
358 'Documentation/admin-guide/bug-hunting.rst'. More on debugging the kernel
359 with gdb is in 'Documentation/dev-tools/gdb-kernel-debugging.rst' and
360 'Documentation/dev-tools/kgdb.rst'.