Lines Matching +full:ipv4 +full:- +full:single +full:- +full:target
10 Linus Torvalds with assistance from a loosely-knit team of hackers across
11 the Net. It aims towards POSIX and Single UNIX Specification compliance.
13 It has all the features you would expect in a modern fully-fledged Unix,
15 loading, shared copy-on-write executables, proper memory management,
16 and multistack networking including IPv4 and IPv6.
18 It is distributed under the GNU General Public License - see the
23 Although originally developed first for 32-bit x86-based PCs (386 or higher),
26 IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64, AXIS CRIS,
29 Linux is easily portable to most general-purpose 32- or 64-bit architectures
35 userspace application - this is called UserMode Linux (UML).
39 - There is a lot of documentation available both in electronic form on
40 the Internet and in books, both Linux-specific and pertaining to
46 - There are various README files in the Documentation/ subdirectory:
47 these typically contain kernel-specific installation notes for some
48 drivers for example. See Documentation/00-INDEX for a list of what
53 - The Documentation/DocBook/ subdirectory contains several guides for
55 number of formats: PostScript (.ps), PDF, HTML, & man-pages, among others.
61 - If you install the full sources, put the kernel tarball in a
65 xz -cd linux-4.X.tar.xz | tar xvf -
72 whatever the kernel-du-jour happens to be.
74 - You can also upgrade between 4.x releases by patching. Patches are
77 (linux-4.X) and execute:
79 xz -cd ../patch-4.x.xz | patch -p1
83 the backup files (some-file-name~ or some-file-name.orig), and make sure
84 that there are no failed patches (some-file-name# or some-file-name.rej).
88 (also known as the -stable kernels) are not incremental but instead apply
93 patch -R) _before_ applying the 4.0.3 patch. You can read more on this in
94 Documentation/applying-patches.txt
96 Alternatively, the script patch-kernel can be used to automate this
100 linux/scripts/patch-kernel linux
106 - Make sure you have no stale .o files and dependencies lying around:
115 Compiling and running the 4.x kernels requires up-to-date
132 kernel source code: /usr/src/linux-4.X
137 cd /usr/src/linux-4.X
154 - Alternative configuration commands are:
213 target$ lsmod > /tmp/mylsmod
214 target$ scp /tmp/mylsmod host:/tmp
226 - NOTES on "make config":
228 - Having unnecessary drivers will make the kernel bigger, and can
232 - Compiling the kernel with "Processor type" set higher than 386
236 - A kernel with math-emulation compiled in will still use the
242 - The "kernel hacking" configuration details usually result in a
251 - Make sure you have at least gcc 3.2 available.
256 - Do a "make" to create a compressed kernel image. It is also
263 - If you configured any of the parts of the kernel as `modules', you
266 - Verbose kernel compile/build output:
277 target, use "V=2". The default is "V=0".
279 - Keep a backup kernel handy in case something goes wrong. This is
291 - In order to boot your new kernel, you'll need to copy the kernel
295 - Booting a kernel directly from a floppy without the assistance of a
319 - Reboot with the new kernel and enjoy.
323 - If you have problems that seem to be due to kernel bugs, please check
327 them to me (torvalds@linux-foundation.org), and possibly to any other
328 relevant mailing-list or to the newsgroup.
330 - In all bug-reports, *please* tell what kernel you are talking about,
335 - If the bug results in a message like
352 on making sense of the dump is in Documentation/oops-tracing.txt
354 - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump
361 - In debugging dumps like the above, it helps enormously if you can
388 If you for some reason cannot do the above (you have a pre-compiled
390 possible will help. Please read the REPORTING-BUGS document for details.
392 - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you
394 kernel with -g; edit arch/i386/Makefile appropriately, then do a "make
402 gdb'ing a non-running kernel currently fails because gdb (wrongly)