From: jdow <jdow@earthlink.net>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-m68k@vger.kernel.org
Subject: Re: Partitions: Amiga RDB partition on 2 TB disk way too big, while OK in AmigaOS 4.1
Date: Sun, 17 Jun 2012 15:27:55 -0700 [thread overview]
Message-ID: <4FDE59EB.8050305@earthlink.net> (raw)
In-Reply-To: <201206172306.03202.Martin@lichtvoll.de>
On 2012/06/17 14:06, Martin Steigerwald wrote:
...
I have a usage note for you and the person who did that partitioning.
If you start the partition at block 1 instead of block zero it probably
can coexist nicely with normal fdisk partitioning as well. (It used to
be able to since x86 partition tables didn't bother with blocks on the
first "cylinder" other than block zero.) I designed RDPrepX and
HDWrench to take advantage of that. (And I used it myself. Erm I used a
LOT of abominations such as safely nested partitions.)
{^_^}
next prev parent reply other threads:[~2012-06-17 22:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 6:41 Partitions: Amiga RDB partition on 2 TB disk way too big, while OK in AmigaOS 4.1 Martin Steigerwald
2012-06-17 10:50 ` jdow
2012-06-17 12:58 ` Martin Steigerwald
2012-06-17 16:36 ` Geert Uytterhoeven
2012-06-17 21:06 ` Martin Steigerwald
2012-06-17 21:58 ` jdow
2012-06-18 21:14 ` Martin Steigerwald
2012-06-17 22:27 ` jdow [this message]
2012-06-17 21:06 ` jdow
2012-06-17 21:15 ` Geert Uytterhoeven
2012-06-17 22:09 ` jdow
2012-06-17 21:20 ` Martin Steigerwald
2012-06-17 22:17 ` jdow
2012-06-18 1:28 ` jdow
2012-06-19 19:46 ` Martin Steigerwald
2012-06-18 20:39 ` Martin Steigerwald
2012-06-18 20:58 ` jdow
-- strict thread matches above, loose matches on Subject: below --
2012-06-17 8:33 Martin Steigerwald
2012-06-17 10:53 ` jdow
2012-06-17 12:51 ` Martin Steigerwald
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=4FDE59EB.8050305@earthlink.net \
--to=jdow@earthlink.net \
--cc=Martin@lichtvoll.de \
--cc=axboe@kernel.dk \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@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;
as well as URLs for NNTP newsgroup(s).