linux-kernel - Re: Proposed update of the i386 boot document

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 17 May 2007 15:42:19 +0530
From:	Vivek Goyal <vgoyal@...ibm.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Andi Kleen <ak@...e.de>, Jeremy Fitzhardinge <jeremy@...p.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Proposed update of the i386 boot document

On Wed, May 16, 2007 at 06:11:14PM -0700, H. Peter Anvin wrote:
> I have noticed that a few items in the i386 boot document have become a
> bit incoherent and/or dated over the years.  Attached is an attempt at
> rewriting a few of the sections; the main things is a field-by-field
> description for the setup header.
> 
> I would appreciate comments as to if this makes it easier to follow or not.
> 

Overall looks good to me. Especially for relocatable kernel, to a boot
loader now it is more clear what is the meaning of different fields
and need to modify code32_start if protected mode kernel was loaded
at non 1MB address.

Thanks
Vivek

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/