use a single partitioned loop device #641
Conversation
|
I've merged this into the internal nightly build system. If it doesn't cause any issues, I'll merge the PR in a few days. Thanks! |
|
Pushed a couple of fixes.
Then if the loopback device is attached but the either partition is not mounted, you get If the mounted partitions have subdirectories mounted, then I've also changed it to iterate over all the partitions rather than assuming there are only two. |
|
Seems to work now, thanks. |
…i-Distro-master * 'master' of https://github.com/RPi-Distro/pi-gen: use a single partitioned loop device (RPi-Distro#641) Add parameter to keep cap_setfcap Updates to avoid common pitfalls when changing the RELEASE variable stage2: pre-install kms++-utils apt/retries: specify option from the Acquire group (RPi-Distro#638) Update README.md document WPA_COUNTRY Code format (RPi-Distro#636) Update release notes Disable first run wizard if DISABLE_FIRST_BOOT_USER_RENAME is set Update release notes Update release notes nodered is no longer included in full images
* RPi-Distro-master: use a single partitioned loop device (RPi-Distro#641) Add parameter to keep cap_setfcap Updates to avoid common pitfalls when changing the RELEASE variable stage2: pre-install kms++-utils apt/retries: specify option from the Acquire group (RPi-Distro#638) Update README.md document WPA_COUNTRY Code format (RPi-Distro#636) Update release notes Disable first run wizard if DISABLE_FIRST_BOOT_USER_RENAME is set Update release notes Update release notes nodered is no longer included in full images
per #639, use a single partitioned loop device rather than multiple devices with offset/length.
testing is limited to "works for me, and doesn't leave any new errors in the output of build.sh". is there an actual test suite or anything like that?