Remork does that mean that resizing the existing partition (the process described in the link) is NOT the way to go?
rather, create a whole new partition?
that describes how to resize the Linux partition (NOT BELABOOT
). That is fine (and that's what I'd do), but it will not show up as a device on the host unless your host is a Linux machine or a Windows machine with drivers installed for ext4 file system. This means that in order to add files to it you'd need to use scp
or rsync
over the virtual network created via USB. If you wanted a FAT32 partition that shows up on your host, then you cannot resize BELABOOT
, but you should create a new partition for this purpose.
Remork "The two partitions /dev/mmcblk0p1 and /dev/mmcblk0p2 are the small FAT32 boot partition (a few MB) and your root filesystem, respectively.", does that describe BELABOOT and the other partition?
yes. BELABOOT
is /dev/mmcblk0p1
and the Linux partition is /dev/mmcblk0p2
.
Remork should i then create a primary partition number 3 (1 being BELABOOT and 2 being linux/program)
That sounds right. The steps described there would need to be modified slightly to create a new partition and you may need to call something else like
mkfs.vfat /dev/mmcblk0p3
dosfslabel /dev/mmcblk0p3 BIG_FAT
after you created it. The good thing is that this shouldn't be as dangerous as trying to enlarge an existing partition, so you can almost do via trial and error (i.e.: using fdisk
' s built in help) or even Google and trial!