Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
Following the instructions at
http://gumstix.org/create-a-bootable-microsd-card.html I am getting a
third (extra) partition created automatically in the sfdisk step. I
have had it happen on a few 16gig and one 2gig sd cards. I am rounding
down the cylinder count, should I round down and subtract one?
From: Ash Charles <ashcharles@gm...> - 2011-10-05 02:29:02
On Mon, Oct 3, 2011 at 9:55 AM, Gavin Swanson <gavinswanson@...> wrote:
> have had it happen on a few 16gig and one 2gig sd cards. I am rounding
> down the cylinder count, should I round down and subtract one?
Hmm---I also see sfdisk allocating any leftover bits to a third
partition. I can't figure out how to prevent this behaviour from the
sfdisk command line. In a script, I get the correct behaviour if I
just specify two partitions. Any one have an idea?
In any case, I think this probably not a major issue as a handful of
bits is always going to be wasted and the third partition remains
unformatted as per the current instructions. Perhaps I'm forgetting
From: Don Quixote de la Mancha <quixote@du...> - 2011-10-06 05:24:49
On Tue, Oct 4, 2011 at 7:28 PM, Ash Charles <ashcharles@...> wrote:
> Hmm---I also see sfdisk allocating any leftover bits to a third
> partition. I can't figure out how to prevent this behaviour from the
> sfdisk command line. In a script, I get the correct behaviour if I
> just specify two partitions. Any one have an idea?
I'm pretty sure Master Boot Record partition tables always have a
total of four primary and extended partitions. That's because there
is a fixed-sized array in the boot sector that is four slots long.
I think you could remove the unwanted sector by zeroing out the
contents of the third partition slot. It might not be hard to patch
the sfdisk source to do that, or you could do it with a hex editor if
you look up the byte offset of the partition table in the MBR.
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and Beauty