ts-7000
[Top] [All Lists]

[ts-7000] Re: What tool did TS use to partition their SD cards?

To:
Subject: [ts-7000] Re: What tool did TS use to partition their SD cards?
From: "Tom" <>
Date: Tue, 13 Apr 2010 00:34:33 -0000




--- In  "Blair" <> wrote:
>
> Anyone know what tool TS used to partition their SD cards or how they did it 
> if they used fdisk or GParted?
> 
> The partition table is funky in that there are non-standard size partitions 
> and empty space between them.  Where I'm going with this is that partition 2 
> where the kernel lives is just a bit too small for a custom kernel I want to 
> use uncompressed.  Partition 3 is also a bit small and doesn't have enough 
> free file "slots".
>

Don't think it matters.  The empty space is there for a reason.
I just went thru the process of creating an SD card from scratch.
Here is an excerpt from my notes:
=========================================================
    p1    kernel  same kernel for ts-sdboot AND debian-sd
                dd'ed
    p2    ext2 for ts-sdboot /
               1. must be type df (non FS-data) or ts-sdboot won't boot
               2. partition can be made bigger (currently free space afterward)
                  but doing so slows down the boot time:
                     at size=2048          1.53
                     at size=6656          2.57secs
    p3   ext2 for debian-sd /
         also mounted readonly at /mnt/root by ts-sdboot
              there are symbolic links in ts-sdboot:/(p2) that point here
===========================================================

The free space is to allow ts-sdboot to grown without moving the next 
partition.  The partition is made as small as possible to minimize the boot 
time of ts-sdboot.

I think p2 can be made as large as you want.  I remember making it subsume all 
the free space for sure.

p3 can be made as large as you want.

What I'm a little fuzzy on is how the prior boot code finds and loads the 
kernel.  I'm GUESSING you can make p1 as big as you want.  I left it the same 
size because I couldn't afford the time to experiment any more.

I'd suggest
1. get a bigger SD
2. dd if=/dev/mmcblk<working> of=/dev/mmcblk<bigger>
3. get it to boot
4. play with your favorite partition manager to make p1 bigger.
5. fixup up (gpartd may do this) the 2 ext2 filesystems or reinstall them.
6.  dd the same kernel back into p1 and see if boots.
7  assuming success, dd your bigger kernel in.

The only thing I'd ask, if you try it, report the results.

tc





------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/ts-7000/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/ts-7000/join
    (Yahoo! ID required)

<*> To change settings via email:
     
    

<*> To unsubscribe from this group, send an email to:
    

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

<Prev in Thread] Current Thread [Next in Thread>
Admin

Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU