-----BEGIN PGP SIGNED MESSAGE-----

On Wed, 1 Jul 1998 gwr@netbsd.org wrote:

>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.

Well, it seems that most architectures look for /netbsd first and then
some arch-specific list of alternate names.  I'd rather we keep this
consistent accross platforms.

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

Yeah, basically.  Someone coming from another port who builds a new
kernel for their machine is probably going to copy it into /netbsd
first, and would be quite reasonably surprised when the old kernel still
booted.  Most userland utilities will also be looking in /netbsd first,
so you need to modify (at least) libkvm if /netbsd is not going to be
the default location for the booted kernel...

>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.

Well, again I think there is a reasonable expectation that /netbsd
contains an image of the booted kernel if we have booted from a local
disk with no magic flags to the booter...

I dunno.  It's not a huge concern, certainly, but I think consistency is
good...

- -- 
				Jim Wise
				jwise@unicast.com

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
Charset: noconv

iQEVAwUBNZqMWxg+dMhCouwfAQFV4gf+MmBWtp6nhUq5UXTUETzbyatOLd7Z4iro
7YDUvJnMPsraGmC16Egbp0z0UzkK3tw8f9AWRNS8FPf4L4zyKuqlV8mRm9mGaEcE
K/wsSlorjYaShNxtTU25T2lQC6GM/LzxtVxTHf+kEgnur/jrC7+TiL9841AhcpPI
j1x+XluHNNce0EB5TS8u/SKq2Aetyv+q/bQnbgtDVJSrXPSIiTl4/uC8FxBoB3Ok
nHS1Ekp0QvI/XSDjEPUcFutrTYWQR7zu5A8toGQ0GpfF7XZzEMmBMfscrKFEIBmU
BfhcBTA21c1R/5sTc5SDQb4MCBPbF+hueN/OWGfQW4yX/SMDTSHcxA==
=2Eul
-----END PGP SIGNATURE-----