From: Matt Domsch <Matt_Domsch@dell.com>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
Cc: Michael E Brown <mebrown@michaels-house.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] Add boot sector checksums to EDD
Date: Wed, 10 Nov 2004 09:35:34 -0600 [thread overview]
Message-ID: <20041110153533.GA23981@lists.us.dell.com> (raw)
In-Reply-To: <4191ABE8.1060703@gmx.net>
On Wed, Nov 10, 2004 at 06:49:28AM +0100, Carl-Daniel Hailfinger wrote:
> Michael E Brown schrieb:
(copying lkml again)
> > I'm curious, do you have a tool that uses the boot sector checksum? I
> > can think of a couple of places it could be useful, but all of my
> > use-cases are adequately covered by simple signature.
>
> The tool is SUSE hwinfo. Currently its author does the checksumming
> in the bootloader which kills some BIOSes (1st EDD request in the
> bootloader is ok, second request by kernel EDD startup code hangs
> the machine).
I'd be curious to understand this better. i.e. failure mode, why it
fails, for what systems, etc.
> I have some drives with identical mbr_signature (drives were wiped
> with dd before I got them). Using a checksum gives me at least some
> chance to identify them better because one has a bootloader, the
> other hasn't, they have different partition tables etc.
What wrote the bootloader to the first disk? Can *that* write a
unique signature into the disk? Red Hat's build of parted includes a
patch I wrote (not yet included in parted upstream IIRC) which has
parted write a unique signature to each disk, so that's how we solve
it there...
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next parent reply other threads:[~2004-11-10 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4191A8D7.1030300@michaels-house.net>
[not found] ` <4191ABE8.1060703@gmx.net>
2004-11-10 15:35 ` Matt Domsch [this message]
2004-11-10 4:43 Carl-Daniel Hailfinger
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=20041110153533.GA23981@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mebrown@michaels-house.net \
/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
Powered by JetHome