All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Carnecky <tom@dbservice.com>
To: Neil Conway <nconway_kernel@yahoo.co.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 3TB disk hassles
Date: Thu, 16 Dec 2004 19:05:20 +0100	[thread overview]
Message-ID: <41C1CE60.5010606@dbservice.com> (raw)
In-Reply-To: <20041216173811.7697.qmail@web26505.mail.ukl.yahoo.com>

Neil Conway wrote:
> Hi Tom...
> 
>  --- Tomas Carnecky <tom@dbservice.com> wrote: 
> 
>>I had a GUID partition table (GPT) on my system (x86, normal 
>>mainboard/BIOS etc) and it worked fine. I didn't need a separate boot
>>disk. I used grub as the boot loader. I think if you enable GPT in
>>the 
>>kernel you should be able to boot stright from the big disk.
> 
> 
> Wow, that's unexpected but encouraging news.  What distro?  Did it
> allow you to go GPT right from the off, or did you have to migrate from
> an MSDOS ptbl to a GPT one after installation?
> 

It was gentoo, and I even think I installed it right onto the GPT disk, 
so no migration. But I'm not sure. You just have to look that your 
kernel supports GPT. I don't know if the kernel from the gentoo livecd 
supports GPT.

Also have a look here how to create GPT partitions:
http://www.google.ch/search?q=site%3Ausefulthings.org.uk+gpt
I think I did it like it's shown there, mklabel, mkpart and mount them.
I don't think I migrated from MSDOS to GPT, because I don't even know 
how it'is possible if you have only one disk with the system on it.

While looking for gentoo GPT support, I found this:
http://www.ussg.iu.edu/hypermail/linux/kernel/0411.1/0624.html
Looks like CONFIG_EFI_PARTITION is enabled by default now on the newer 
kernels.

tom

  reply	other threads:[~2004-12-16 18:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-16 14:52 3TB disk hassles 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2004-12-16 22:21 Rico Tudor
     [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
2005-02-06 10:59 Neil Conway
2005-02-06 19:01 ` Bodo Eggert
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

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=41C1CE60.5010606@dbservice.com \
    --to=tom@dbservice.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.