From: Sven Luther <sven.luther@wanadoo.fr>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Sven Luther <sven.luther@wanadoo.fr>,
John Bradford <john@grabjohn.com>,
Szakacsits Szabolcs <szaka@sienet.hu>,
Apurva Mehta <apurva@gmx.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
bug-parted@gnu.org
Subject: Re: Disk Geometries reported incorrectly on 2.6.0-testX
Date: Sat, 29 Nov 2003 23:44:11 +0100 [thread overview]
Message-ID: <20031129224411.GA9214@iliana> (raw)
In-Reply-To: <20031129221424.GA5456@win.tue.nl>
On Sat, Nov 29, 2003 at 11:14:24PM +0100, Andries Brouwer wrote:
> On Sat, Nov 29, 2003 at 06:01:03PM +0100, Sven Luther wrote:
>
> > The only problem is that your BIOS will probably not be able
> > to boot from it
>
> You seem to misunderstand the boot sequence.
> The BIOS does not generally do any parsing of partition tables.
A, ok. I am more familiar with open firmware, which does contain
partition table reading code.
That said, i really doubt that a standard BIOS can boot from a not MBR
containing disk, but i may be wrong.
Friendly,
Sven Luther
next prev parent reply other threads:[~2003-11-29 22:44 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 4:58 Disk Geometries reported incorrectly on 2.6.0-testX Apurva Mehta
2003-11-28 14:24 ` Andries Brouwer
2003-11-29 2:22 ` Andrew Clausen
2003-11-29 5:16 ` Szakacsits Szabolcs
2003-11-29 9:18 ` Sven Luther
2003-11-29 12:41 ` Andries Brouwer
2003-11-30 11:44 ` Szakacsits Szabolcs
2003-11-30 15:19 ` Andries Brouwer
2003-11-29 12:34 ` Andries Brouwer
2003-11-29 13:50 ` John Bradford
2003-11-29 14:04 ` Stefan Smietanowski
2003-11-29 17:01 ` Sven Luther
2003-11-29 22:14 ` Andries Brouwer
2003-11-29 22:44 ` Sven Luther [this message]
2003-11-30 0:39 ` Andries Brouwer
2003-11-30 9:35 ` Sergey Vlasov
2003-11-29 22:31 ` Andrew Clausen
2003-11-30 8:57 ` Arjan van de Ven
2003-11-30 7:38 ` Szakacsits Szabolcs
2003-11-30 10:40 ` John Bradford
2003-11-30 11:24 ` Sven Luther
2003-11-30 13:48 ` John Bradford
2003-11-30 17:22 ` Sven Luther
2003-11-30 23:51 ` Andrew Clausen
2003-11-30 22:54 ` Andrew Clausen
2003-11-29 22:27 ` Andrew Clausen
2003-11-30 0:34 ` Andries Brouwer
2003-11-30 11:10 ` Szakacsits Szabolcs
2003-11-30 13:26 ` Andries Brouwer
2003-11-30 12:34 ` Szakacsits Szabolcs
2003-11-30 15:46 ` Andries Brouwer
2003-11-29 22:33 ` Andrew Clausen
2003-11-30 9:16 ` Szakacsits Szabolcs
2003-12-03 11:05 ` Andrew Clausen
2003-12-03 11:28 ` Szakacsits Szabolcs
2003-12-03 11:54 ` Andrew Clausen
2003-12-03 13:07 ` Szakacsits Szabolcs
2003-12-03 23:27 ` Andrew Clausen
2003-12-03 21:55 ` Szakacsits Szabolcs
2003-12-03 23:47 ` bill davidsen
[not found] <200311300220.hAU2K0dr019280@sunrise.pg.gda.pl>
2003-11-30 2:22 ` Andrzej Krzysztofowicz
2003-11-30 13:13 ` Andries Brouwer
2003-11-30 13:58 ` John Bradford
2003-11-30 7:08 Norman Diamond
2003-11-30 7:08 Norman Diamond
2003-11-30 12:49 ` Andries Brouwer
2003-12-03 11:06 ` Andrew Clausen
2003-12-03 14:42 ` Andries Brouwer
2003-12-03 23:11 ` Andrew Clausen
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=20031129224411.GA9214@iliana \
--to=sven.luther@wanadoo.fr \
--cc=aebr@win.tue.nl \
--cc=apurva@gmx.net \
--cc=bug-parted@gnu.org \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=szaka@sienet.hu \
/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;
as well as URLs for NNTP newsgroup(s).