In Fatdog64, you can just double-click the qv.img file with ROX and you can view the contents. Two additional drive icons will be shown on the desktop (dm-0 and dm-1), and you can mount them by clicking on the drive icon as usual. The main btrfs partition would be in dm-1.
To un-mount it, just click on the green checkbox on dm-1 (the same way you unmount other partitions), and then double-click the original qv.img to remove dm-0/dm-1 drive icons (and you must do it in that order: unmount the partition, then unmount qv.img).
No additional tool or script is needed.
This whole magic is done with the venerable filemnt (old timers will remember this), so from the command line you can do exactly the same thing by doing filemnt qv.img
(to open the image file and access dm-0 and dm-1), followed by mount /dev/dm-1 /mnt/data
to access the partition. To close it, just reverse the order: umount /mnt/data
, and then filemnt qv.img
.
PS: if you want to use Fatdog's filemnt script in other Puppies, please be aware that it depends on two uncommon binaries: guess_fstype (this is available in most puppies), and kpartx (this is from a package called multipath-tools). If you don't have these two binaries, filemnt will not work on your system.
---------------
I can't say much about mount-img or qv-installer; but I would humbly suggest to Barry to:
a) put all the external script dependencies (like mount-img) inside the qv-installer so it does not depend them being externally available (e.g. copy the contents of mount-img and put it in a function called mount-img inside the qv-installer; the same for probepart2, etc)
b) detect that the tools required for operations exist (e.g. which mkfs.btrfs
) and if they don't, bail out while giving the reason why (e.g. "mkfs.btrfs does not exist, please install btrfs-tools package" or something like that).
This is of course if the plan is to use qv-installer from outside QV itself. If the plan is to use qv-installer only from inside QV itself, then the suggestions above is not relevant.