To summarise the discssion:

The following tupples have been tabled (I've omitted the ARCH-unknown
bit):

       CPU_TYPE-MANUFACTURER-KERNEL-OPERATING_SYSTEM

	        ELF               a.out
	*-netbsdelf          *-netbsdaout
	*-netbsd-netbsdelf   *-netbsd-netbsdaout
	*-netbsd-elf         *-netbsd-aout

(BTW the patterns *-netbsd*elf | *-netbsd*aout always work).  I'll get a
clarification of exactly what the ``KERNEL'' and ``OPERATING_SYSTEM''
should refer to.  It really depends on what the ``ABI'' (Application
binary interface) is part of: The kernel or the Operating System.  I
strongly suspect that, in this context, it is part of the kernel.

Anyway:

I think I can discard the following as they don't reflect reality:

	*-netbsdelf          *-netbsd
	*-netbsd             *-netbsdaout

Some targets were always ELF, some are not going to be ELF for some time
(read months).  It would just lead to confusion.

I think I can discard the following as they preclude the use of the
vendor field (by a vendor) of the tupple:

	ARCH-elf-netbsd      ARCH-aout-netbsd

We shouldn't preclude the possability of things like
``ARCH-{gateway,redhat}-linux-gnu''.

	Andrew