[ Replying to both messages here, which suggest we should
  try "netbsd" before "netbsd.$arch" ]

> Date: Mon, 29 Jun 1998 22:37:44 -0400 (EDT)
> From: Jim Wise <jwise@unicast.com>
> 
> IMHO, if there is a kernel named `/netbsd', we should always boot off of
> it, for consistency with the other architectures.  If we fail to find
> /netbsd, _then_ we should look for /netbsd.${ARCH}.  THis also allows
> install software to install both, and then add an appropriate symlink.

> Date: Mon, 29 Jun 1998 22:13:18 -0700 (PDT)
> From: Jeremy Cooper <jeremy@broder.com>
> 
> I agree with you on this point.  I and many other users have learned to
> rely on being able to rename a kernel that I don't want in operation in
> order to keep it from being booted.  Searching for alternate names before
> the canonical one not only seems backwards but could possibly bite
> someone who isn't expecting it.

I implemented the search order  { "netbsd.$arch", "netbsd" }
only because it seemed to make sense to try the more specific
name before the more general name, and it seemed a little bit
easier to implement that search order.

Is the concern that someone might have "netbsd.$arch" sitting
around and not want to use it?

It should not be too hard to switch the search order if that's
really a big concern.  (Seemed "small potatoes" to me!:)

Actually I was considering adding some /etc/rc code to make a
symlink from the booted kernel name to /netbsd but maybe that's
just too complicated.

Gordon