From: "Aleksey Gorelov" <Aleksey_Gorelov@Phoenix.com>
To: <etienne.lorrain@masroudeau.com>, <linux-kernel@vger.kernel.org>
Subject: RE: IDE disk and HPA
Date: Thu, 4 Aug 2005 10:15:49 -0700 [thread overview]
Message-ID: <0EF82802ABAA22479BC1CE8E2F60E8C341EB82@scl-exch2k3.phoenix.com> (raw)
>-----Original Message-----
>From: linux-kernel-owner@vger.kernel.org
>[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of
>Etienne Lorrain
>Sent: Thursday, August 04, 2005 5:11 AM
>To: linux-kernel@vger.kernel.org
>Subject: Re: IDE disk and HPA
>
>> > > My question is now: why is an HPA disabled i.e. disprotected when
>> > > detected? Why not let the HPA alone, because a certain
>set of disk
>> > > sectors shall not be accessible by the OS?
>> >
>> > Because the HPA is most commonly used to hide all but a
>fraction of a
>> > disk to work with older BIOSes.
>>
>> But as to my knowledge, the HPA was had been introduced to allow HW
>> vendors to store things like diagnostic programs in a part of the
>> disk protected from partitioning and filesystems.
>> The point is, IF there is an HPA, there MIGHT be a partitioning
>> scheme and some filesystems on the disk which rely on the size of
>> disk being the native size MINUS the HPA.
>
> If those HW vendors want to store software in the HPA of the IDE
> hard disk, and they employ people able to read the IDE specifications,
> they know that this HPA can be protected by password and so Linux
> just display a failure when trying to restore the capacity of the
> Hard Disk - because it lacks the unlocking password.
Yep, you are right. When used by BIOS/firmware, it is usually
protected by password. And interesting enough, as in this particular
case, they employ people to not only read them, but to write them as
well ;)
However, if not protected by the password, it is probably Ok
to make it visible (as things currently are).
>
> Note that this HPA is a good place to store a bootloader too, in fact
> I like to think of it as the big floppy drive of the PC which no more
> have any floppy drive: create a FAT filesystem of 64 Mbytes there and
> copy all the floppy you used to have there. Your bootloader, if it
> is good enough, will be able to run software from this area.
If your bootloader if the first thing to run in the system, you can
use & protect portion of your hardrive for yourself - just make sure you
lock with set max with password when passing control to 'normal'
OS/loader.
Aleks.
next reply other threads:[~2005-08-04 17:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 17:15 Aleksey Gorelov [this message]
2005-08-05 9:50 ` Etienne Lorrain
-- strict thread matches above, loose matches on Subject: below --
2005-08-04 12:11 Etienne Lorrain
2005-08-04 21:45 ` Gustavo Guillermo Pérez
2005-08-05 10:15 ` Etienne Lorrain
2005-07-22 12:17 Oliver Tennert
2005-07-22 14:47 ` Alan Cox
2005-08-04 7:14 ` Oliver Tennert
2005-08-04 11:41 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0EF82802ABAA22479BC1CE8E2F60E8C341EB82@scl-exch2k3.phoenix.com \
--to=aleksey_gorelov@phoenix.com \
--cc=etienne.lorrain@masroudeau.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®