From: Jamie Lokier <jamie@shareable.org>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 2.4] EDD 4-byte MBR disk signature for the boot disk
Date: Fri, 10 Oct 2003 15:51:37 +0100 [thread overview]
Message-ID: <20031010145137.GC28795@mail.shareable.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0310100903360.2846-100000@iguana.domsch.com>
Matt Domsch wrote:
> There are 4 bytes in the MSDOS master boot record, at offset 0x228,
> which may contain a per-system-unique signature. By writing into this
> signature from a tool that makes real-mode int13 calls a unique
> signature such as "BOOT" for the boot disk (int13 dev 80h), Linux may
> then retrieve this information and use it to compare against disks it
> knows as named /dev/[hs]d[a-z].
If I put a hard disk from another system into my computer, and it has
the "BOOT" signature, Linux will see two disks with the signature. Barf!
Same if I boot from two different disks at different times, and more
so if one of them fails to boot properly so that it's not even
possible for the booted kernel to erase the signature on its boot
disk.
It would be better to have the boot loader pick a likely-unique number
such as the CMOS time in seconds since whenever and store that, and
pass it as boot parameter to the kernel. A few bits could be reserved
to indicate that it was from our boot loaders; it would be good if we
had a list of existing per-system-unique signatures to avoid. Do you
know of such a list?
-- Jamie
next prev parent reply other threads:[~2003-10-10 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 14:05 [RFC][PATCH 2.4] EDD 4-byte MBR disk signature for the boot disk Matt Domsch
2003-10-10 14:51 ` Jamie Lokier [this message]
2003-10-10 16:50 ` Matt Domsch
2003-10-10 20:28 ` Jamie Lokier
2003-10-14 10:45 ` Andries Brouwer
2003-10-14 13:38 ` Matt Domsch
2003-10-25 2:28 ` Herbert Poetzl
2003-10-25 4:56 ` Valdis.Kletnieks
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=20031010145137.GC28795@mail.shareable.org \
--to=jamie@shareable.org \
--cc=Matt_Domsch@dell.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