linux-kernel - Re: [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-prev] [day] [month] [year] [list]

Message-ID: <20160805092243.GA19068@amd>
Date:	Fri, 5 Aug 2016 11:22:43 +0200
From:	Pavel Machek <pavel@....cz>
To:	Jonathan Corbet <corbet@....net>
Cc:	Øyvind A. Holm <sunny@...base.org>,
	linux-kernel@...r.kernel.org, Diego Viola <diego.viola@...il.com>,
	Jiri Kosina <jkosina@...e.com>,
	Vineet Gupta <Vineet.Gupta1@...opsys.com>
Subject: Re: [PATCH] README: Mention when 386 support ended + update obsolete
 386 paths

On Tue 2016-07-26 06:12:29, Jonathan Corbet wrote:
> On Tue, 26 Jul 2016 09:45:43 +0200
> Øyvind A. Holm <sunny@...base.org> wrote:
> 
> >      - 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.
> 
> So we want the documentation to reflect current kernels, not those from
> years gone by.  I can't think of a reason why this paragraph should
> continue to exist at all.  Can you make a new version that removes it
> altogether?

You may want to generalize it to "will not boot if you se processor
type too high", but I'd keep v3.7 note -- it is going to be tricky to
find out in any other way.

Best regards,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html