From: jw schultz <jw@pegasys.ws>
To: linux-kernel@vger.kernel.org
Subject: Re: Partition check order in fs/partition/check.c?
Date: Tue, 1 Apr 2003 12:24:46 -0800 [thread overview]
Message-ID: <20030401202446.GB4078@pegasys.ws> (raw)
In-Reply-To: <200304011316.h31DFwTR039380@d06relay02.portsmouth.uk.ibm.com>
On Tue, Apr 01, 2003 at 03:14:56PM +0200, Peter Oberparleiter wrote:
> Hm, what do you think of these additional checks:
>
> 1. Check for overlap of partitions
Be very careful here. While you better not _use_ overlapping
partitions, a partition table with overlapping partitions is
a traditional UNIX default. It is usually something like
part start length
a 0 3/8 drive
b 3/8 1/8 drive
c 0 whole drive
d 0 1/3 drive
e 1/3 1/3 drive
f 2/3 1/3 drive
g 1/3 2/3 drive
h 1/2 1/2 drive
In this way admins wouldn't repartition, just use the default
partitions in suitable combinations. This actually reduced
the likelihood of overlapping partitions because the
partitioning tools were sometimes confusing causing custom
partition to have 1 cylinder overlaps. When drives got to be
larger than 2GB these default partition sizes became
increasingly pointless.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt
prev parent reply other threads:[~2003-04-01 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 9:33 Peter Oberparleiter
2003-04-01 10:35 ` Russell King
2003-04-01 13:14 ` Peter Oberparleiter
2003-04-01 13:27 ` Russell King
2003-04-01 20:24 ` jw schultz [this message]
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=20030401202446.GB4078@pegasys.ws \
--to=jw@pegasys.ws \
--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
all inboxes | Powered by JetHome®