Re-partitioning; Adding swap partition; Using GPT partitions
#6
(12-04-2019, 03:54 AM)danielt Wrote: With a bit of trickery it is also possible to preconfigure the GPT so that the idbloader, uboot and trusted firmware images appear as separate partitions. Not only does this make it easier to hack or alter the bootloaders but it also makes it difficult to accidentally damage them (tooling to trim unallocated space for example).

I'm not sure if it possible to create a partition label with a first-lba set to 64 using fdisk. I generally use an sfdisk for this:

cat <<EOF | sudo sfdisk /dev/mmcblk1
unit: sectors
first-lba: 64
/dev/mmcblk1p1 : start= 64, size= 16320, type=8DA63339-0007-60C0-C436-083AC8230908, name="IDBLoader", attrs="RequiredPartition"
/dev/mmcblk1p2 : start= 16384, size= 8192, type=8DA63339-0007-60C0-C436-083AC8230908, name="U-Boot", attrs="RequiredPartition"
/dev/mmcblk1p3 : start= 24576, size= 8192, type=8DA63339-0007-60C0-C436-083AC8230908, name="TrustedFirmware-A", attrs="RequiredPartition"
EOF

Once you have created the disk label above can create other partitions using the normal tooling.
Perfect. I may give that a try. It may make things cleaner & clearer, (at least for me).

@ab1jx, There may be another reason to use FAT for the "/boot" partition. When I ran the update from 1.5 to 1.6, it complained about the standard Unix "lost+found" directory and asked if I wanted to delete it. I said no, and thought about putting in a request to have that directory ignored.

But, another problem seems to have occured. Don't know if it's related to my GPT layout or using EXT4 for "/boot", but for whatever reason, the update to 1.5, and the update 1.5 to 1.6 did not update my kernel.

I'll experiment and see if either the GPT layout or EXT4 for "/boot" had any impact.
--
Arwen Evenstar
Princess of Rivendale


Messages In This Thread
RE: Re-partitioning; Adding swap partition; Using GPT partitions - by Arwen - 12-04-2019, 05:39 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)