qemu issues

[Dan Nelson]

In the last episode (Aug 05), John Nielsen said:
> On Sunday 05 August 2007, Zane C.B. wrote:
> > Any time I've used qemu recently, it exits with a 140 and prints out
> > "Bad system call".
> >
> > Any ideas?
> 
> Don't forget to load the aio kernel module on your host.

Wouldn't returning ENOSYS be a lost nicer to the calling process than
signaling SIGSYS?  I always think of SIGSYS as a hint that you're
trying to run a binary from a completely different OS, rather than just
trying to use a valid syscall that just hasn't been enabled.

-- 
	Dan Nelson
	dnelson at allantgroup.com