09-12-2020, 09:22 PM
We are seeing frequent updates on armbsd.org lately. This is awesome.
But what we get is a bootable "disk" image. Rather than starting from scratch with every update, I've been updating my installation thusly:
1) flash image from armbsd.org to an SD-card.
2) boot to the SD-card (I find this difficult but it works)
3) when booting from SD,
/dev/rdk0 is the MS-DOS boot partition on the SD card
/dev/rdk1 is the NetBSD root on the SD card
/dev/rdk2 is the MS-DOS boot partition on the eMMC
/dev/rdk3 is the NetBSD root on the eMMC
I copy (via dd) /dev/rdk0 to /dev/rdk2
4) I mount /dev/rdk3, as /mnt
5) I copy /netbsd to /mnt
6) I copy (recursively) /libdata to /mnt/libdata
I do not know if I'm missing anything, or even if doing this at all is a good idea. But it seems to work.
But what we get is a bootable "disk" image. Rather than starting from scratch with every update, I've been updating my installation thusly:
1) flash image from armbsd.org to an SD-card.
2) boot to the SD-card (I find this difficult but it works)
3) when booting from SD,
/dev/rdk0 is the MS-DOS boot partition on the SD card
/dev/rdk1 is the NetBSD root on the SD card
/dev/rdk2 is the MS-DOS boot partition on the eMMC
/dev/rdk3 is the NetBSD root on the eMMC
I copy (via dd) /dev/rdk0 to /dev/rdk2
4) I mount /dev/rdk3, as /mnt
5) I copy /netbsd to /mnt
6) I copy (recursively) /libdata to /mnt/libdata
I do not know if I'm missing anything, or even if doing this at all is a good idea. But it seems to work.