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] [thread-next>] [day] [month] [year] [list]
Message-ID: <1279974966.11927.26.camel@lithium.local.net>
Date:	Sat, 24 Jul 2010 13:36:06 +0100
From:	Alex Buell <alex.buell@...ted.org.uk>
To:	Tejun Heo <tj@...nel.org>
Cc:	Jeff Garzik <jeff@...zik.org>, ben.collins@...ntu.com,
	"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>, hmh@...ian.org
Subject: Re: support for drives larger than 2TiB

On Sat, 2010-07-24 at 11:58 +0200, Tejun Heo wrote:
> The only problem is that everything which is necessary for booting
> needs to be located below 2TiB limit.  Please note that this is much
> stricter restriction than the 128GiB limit we had due to LBA28.  That
> limit was caused by BIOSes using LBA28 and vendors could and did
> update and be done with it in many cases.  However, 2TiB limit is
> inherent in the BIOS programming interface and currently the only way
> to overcome it is using a completely different BIOS interface (EFI,
> that is).  Vendors are not likely to introduce EFI for already
> released products although they're much more likely to release updates
> so that BIOSes can access upto 2TiB if they don't work already.  We'll
> be stuck with 2TiB limit on much more configurations for longer period
> of time. 

The only thing that would please me no end with newer replacements for
BIOS is the ability to have 4k boot sectors. Imagine what we can do with
4k what we can't do with 512 bytes. 
-- 
http://www.munted.org.uk

One very high maintenance cat living here.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ