Single disk (resizeable) 1 partition restore
-
I usually build my multi-partition (6+ partitions, 2+ OSs) image by installing on several systems, then capturing the individual partitions from separate machines, and deploying them all to one machine. I tried to do that with the latest release candidate and saw that on deployment, each image overwrote the MBR, GPT partition types, and partition UUIDs.
If I change the download scripts to only modify the target partition on deploy of single partition images, will it be accepted into the dev branch?
====================
PS. Sorry for the long absence. Life’s good but eventful. I’m really impressed with the progress you’ve made with FOG in two years. -
You’re still on the development team, so please feel free, though I’d suggest pushing into the working branch now.
The tree structure is now:
master = stable
dev-branch = RC releases. (typically).
working = latest and greatest. -
@fractal13 said in Single disk (resizeable) 1 partition restore:
each image overwrote the MBR, GPT partition types, and partition UUIDs.
Even if you set it to one single partition in the image settings before deploy? Shouldn’t do so I suppose.