linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: Arjan van de Ven <arjanv@redhat.com>, Andrew Clausen <clausen@gnu.org>
Cc: John Bradford <john@grabjohn.com>,
	Andries Brouwer <aebr@win.tue.nl>,
	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: Sun, 30 Nov 2003 10:40:25 GMT	[thread overview]
Message-ID: <200311301040.hAUAePk6000149@81-2-122-30.bradfords.org.uk> (raw)
In-Reply-To: <1070182676.5214.2.camel@laptop.fenrus.com>

Quote from Arjan van de Ven <arjanv@redhat.com>:
> On Sat, 2003-11-29 at 23:31, Andrew Clausen wrote:
> > On Sat, Nov 29, 2003 at 01:50:00PM +0000, John Bradford wrote:
> > > Why don't we take the opporunity to make all CHS code configurable out
> > > of the kernel, and define a new, more compact, partition table format
> > > which used LBA exclusively, and allowed more than four partitions in
> > > the main partition table?
> >
> > Intel's EFI GPT partition table format seems quite acceptable.
> 
> EFI GPT has some severe downsides (like requiring the last sector on
> disk, which in linux may not be accessible if the total number of
> sectors is not a multiple of 2, and making dd of one disk to another
> impossible if the second one is bigger)

EFI GPT is also a far more elaborate scheme than is necessary for a
lot of installations.

My 'requirements' are:

* Good magic

We have seen support for not very widely used partitioning schemes
broken in the past when other schemes are checked for ahead of them.
A simple scheme with well defined magic values reduces this risk.

* Simple

The code for some of the partitioning schemes is full of workarounds
for different implementations.  Added complexity, and more variations
increase the likelyhood of bugs.

* All partition information stored in one partition table

Linked lists make re-arranging partitions, and backing up the
partition table more difficult.

* Support for more than 4 partitions

This is a common requirement now.

* Support for partitions > 2TB

This will become a standard requirement in a few years.

* No mention of CHS

CHS is so last year.  Modern systems don't even need it to boot.  We
could allow all of the CHS-related code to be configured out of the
kernel, which would be useful on some embedded systems.

The Ultrix partition code comes fairly close to what I'm thinking of,
but not close enough :-).

John.

  parent reply	other threads:[~2003-11-30 10:35 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
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 [this message]
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=200311301040.hAUAePk6000149@81-2-122-30.bradfords.org.uk \
    --to=john@grabjohn.com \
    --cc=aebr@win.tue.nl \
    --cc=apurva@gmx.net \
    --cc=arjanv@redhat.com \
    --cc=bug-parted@gnu.org \
    --cc=clausen@gnu.org \
    --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).