April 17, 2017
10:11 a.m.
On Mon, Apr 17, 2017 at 02:07:40PM +0530, K K Subbu wrote:
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.
Thanks! This should make it straightforward to update the startup scripts. Cheers, Alistair