Hi Folks,

Chuck Silvers spotted a problem with the `e_name[8]' field of struct emul
which currently causes lossage for aoutm68k. Basically, in the following
assignment gcc merrily copies "aoutm68k" *minus* the trailing \0 into the
e_name field with no warnings.

    struct emul emul_netbsd_aoutm68k = {
        "aoutm68k",
        "/emul/aout",
        ...

This causes junk to be displayed when running ktrace on a.out binaries
using the aoutm68k emulation.

Are there any objections to changing struct emul's e_name field from

	char e_name[8];
to
	const char *e_name;

Cheers, Steve