linux-kernel - [PATCH] README: Mention when 386 support ended + update obsolete 386 paths

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20160726074543.21311-1-sunny@sunbase.org>
Date:	Tue, 26 Jul 2016 09:45:43 +0200
From:	Øyvind A. Holm <sunny@...base.org>
To:	linux-kernel@...r.kernel.org
Cc:	Jonathan Corbet <corbet@....net>,
	Diego Viola <diego.viola@...il.com>,
	Øyvind A. Holm <sunny@...base.org>,
	Jiri Kosina <jkosina@...e.com>,
	Vineet Gupta <Vineet.Gupta1@...opsys.com>
Subject: [PATCH] README: Mention when 386 support ended + update obsolete 386 paths

The paragraph about i386 could be misinterpreted as if 386 still is a
valid processor type. Mention when 386 support ended, and change two
"arch/i386/" paths to one that exists, "arch/x86/".

Signed-off-by: Øyvind A. Holm <sunny@...base.org>
---
 README | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/README b/README
index e8c8a6d..2c5c125 100644
--- a/README
+++ b/README
@@ -231,7 +231,8 @@ CONFIGURING the kernel:
 
     - Compiling the kernel with "Processor type" set higher than 386
       will result in a kernel that does NOT work on a 386.  The
-      kernel will detect this on bootup, and give up.
+      kernel will detect this on bootup, and give up. The last kernel
+      with support for 386 was version 3.7.
 
     - A kernel with math-emulation compiled in will still use the
       coprocessor if one is present: the math emulation will just
@@ -289,7 +290,7 @@ COMPILING the kernel:
    LOCALVERSION can be set in the "General Setup" menu.
 
  - In order to boot your new kernel, you'll need to copy the kernel
-   image (e.g. .../linux/arch/i386/boot/bzImage after compilation)
+   image (e.g. .../linux/arch/x86/boot/bzImage after compilation)
    to the place where your regular bootable kernel is found.
 
  - Booting a kernel directly from a floppy without the assistance of a
@@ -391,7 +392,7 @@ IF SOMETHING GOES WRONG:
 
  - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you
    cannot change values or set break points.) To do this, first compile the
-   kernel with -g; edit arch/i386/Makefile appropriately, then do a "make
+   kernel with -g; edit arch/x86/Makefile appropriately, then do a "make
    clean". You'll also need to enable CONFIG_PROC_FS (via "make config").
 
    After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore".
-- 
2.9.2.466.g8c6d1f9