On Monday 17 April 2017 01:04 PM, Luke Gorrie wrote:
I wonder if some DWIM would make sense here. For example, my bash wrapper that starts the VM could inspect the image file and decide which VM is appropriate (spur, non-spur, 32-it, 64-bit, etc.) Otherwise the user needs to guess and decipher cryptic error messages.
You can use the attached magic file with file(1) command: file -m magic <image files> ... to detect the image type. or register the patterns with binfmt_misc to match the vm to the image type automatically. BTW, I goofed in my earlier email. I was using 64/vm60 and not 64/vmT60. Sorry for the confusion. With 64/vmT60, I use the following : $ sudo prlimit --rtprio=2 --pid $$ $ ./pharo Pharo.image eval 3+4 Regards .. Subbu