linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bodo Eggert <7eggert@gmx.de>
To: Neil Conway <nconway_kernel@yahoo.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3TB disk hassles
Date: Sun, 6 Feb 2005 20:01:20 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.58.0502061951400.2730@be1.lrz> (raw)
In-Reply-To: <20050206105958.42872.qmail@web26501.mail.ukl.yahoo.com>

On Sun, 6 Feb 2005, Neil Conway wrote:

> Since writing the above, I've been searching for more info.  I
> downloaded four different versions of grub (GNU Grub Legacy, GNU Grub2,
> gentoo and Fedora Core 3).  NONE of these showed any evidence of GPT
> support (I was in a hurry, so I searched for strings EFI, GUID, GPT,
> TB).

I'd use lilo in that case. AFAI understood it can start from any device
provided the BIOS can access the boot files. (May require a 5MB /boot 
partition if the disk is larger than the BIOS can access)

HTH

> I fail to see how grub can work on a GPT boot device if it can't parse
> the partition table.  I conclude that I'm still missing something. 
> Perhaps a layer before grub is supposed to parse the GPT instead?  If
> so, isn't that getting us straight back to a GPT-aware BIOS?

If grub parses the partition table, it will do that without any BIOS
support (except maybe for reading the raw data). So even a GPT-aware BIOS
should not change a thing.

-- 
Funny quotes:
23. If at first you don't succeed, destroy all evidence that you tried.

  reply	other threads:[~2005-02-06 19:13 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-06 10:59 3TB disk hassles Neil Conway
2005-02-06 19:01 ` Bodo Eggert [this message]
2005-02-08 23:33 ` H. Peter Anvin
     [not found] <linux.kernel.20041216145229.29167.qmail@web26502.mail.ukl.yahoo.com>
2005-02-10  0:06 ` Jan Lindheim
     [not found] <fa.fng0mbi.10jm21g@ifi.uio.no>
     [not found] ` <fa.ls0rpqi.104a23q@ifi.uio.no>
2005-02-05  2:58   ` Bodo Eggert
2005-02-05 11:14     ` Neil Conway
  -- strict thread matches above, loose matches on Subject: below --
2004-12-16 22:21 Rico Tudor
2004-12-16 14:52 Neil Conway
2004-12-16 15:33 ` Michelle Konzack
2004-12-16 15:37 ` Mark Watts
2004-12-16 15:38   ` Hans Kristian Rosbach
2004-12-16 16:44     ` Neil Conway
2004-12-16 17:15       ` Tomas Carnecky
2004-12-16 17:38         ` Neil Conway
2004-12-16 18:05           ` Tomas Carnecky
2005-02-05  1:47             ` Neil Conway
2004-12-16 17:40         ` Tomas Carnecky
2004-12-16 15:52   ` Michelle Konzack
2004-12-16 16:03     ` Jan Engelhardt
2004-12-16 16:00       ` Alan Cox
2004-12-18  0:12         ` Andries Brouwer
2004-12-18  3:08           ` H. Peter Anvin
2004-12-18 12:15             ` Andries Brouwer
2004-12-18 23:32               ` H. Peter Anvin
2005-01-03 17:13                 ` Jeff V. Merkey
2005-01-03 17:32                   ` Jeff V. Merkey
2005-01-03 18:11                     ` linux-os
2004-12-16 17:10       ` Michelle Konzack
2004-12-16 19:52 ` Adam Heath
2004-12-16 23:28 ` Pedro Venda (SYSADM)
2005-02-05  1:51   ` Neil Conway

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=Pine.LNX.4.58.0502061951400.2730@be1.lrz \
    --to=7eggert@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nconway_kernel@yahoo.co.uk \
    /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).