Draft.

Author: mirage335

_prog-ops/ops-custom.sh

@@ -3,7 +3,46 @@ _custom() {
 }
 
 _custom-expand() {
-	true
+	local currentExitStatus
+	currentExitStatus="0"
+	
+	_messageNormal '_custom-expand: dd'
+
+	# ATTENTION: Expand ONLY the additional amount needed for custom additions . This is APPENDED .
+	! dd if=/dev/zero bs=1M count=1000 >> "$scriptLocal"/vm.img && _messageFAIL
+
+	# Alternatively, it may be possible, but STRONGLY DISCOURAGED, to pad the file to a size. This, however, assumes the upstream 'ubdist/OS', etc, has not unexpectedly grown larger, which is still a VERY BAD assumption.
+	# https://unix.stackexchange.com/questions/196715/how-to-pad-a-file-to-a-desired-size
+	
+	
+	_messageNormal '_custom-expand: growpart'
+	! _openLoop && _messagePlain_bad 'fail: openLoop' && _messageFAIL
+	
+	export ubVirtPlatform="x64-efi"
+	#_determine_rawFileRootPartition
+	
+	export ubVirtImagePartition="p5"
+	
+	local current_imagedev=$(cat "$scriptLocal"/imagedev)
+	local current_rootpart=$(echo "$ubVirtImagePartition" | tr -dc '0-9')
+	
+	! _messagePlain_probe_cmd sudo -n growpart "$current_imagedev" "$current_rootpart" && _messageFAIL
+	
+	unset ubVirtPlatform
+	unset ubVirtImagePartition
+	
+	! _closeLoop && _messagePlain_bad 'fail: closeLoop' && _messageFAIL
+	
+	_messageNormal '_custom-expand: btrfs resize'
+	! _openChRoot && _messagePlain_bad 'fail: openChRoot' && _messageFAIL
+	
+	
+	! _messagePlain_probe_cmd _chroot btrfs filesystem resize max / && _messageFAIL
+	
+	
+	! _closeChRoot && _messagePlain_bad 'fail: closeChRoot' && _messageFAIL
+	
+	return 0
 }
 
 _custom-repo() {