On Sat, 30 May 1998, Dr. Bill Studenmund wrote:

> On Sat, 30 May 1998, Frederick Bruckman wrote:
> 
> > The Booter displays this messge:
> > 
> > 	Booting...File "netbsd.2hi" not found
> > 	Could not open kernel "(0,?)netbsd.2hi"
> > 
> Wait. You do remember that the booter only handles old-style ffs
> partitions? I think they're level 1. So the booter and installer will have
> problems with a partition that's at level 2 or 3.
> 
> I run into this as I used to use UNION mounts, which need a level 2 fs on
> the upper layer (so they can make white-outs). The booter & installer
> won't work w/ that, so I have root an old-style fs, and /y1 a level 2.
> All the unionfs stuff happens on /y1. :-)

Someone on this list pointed out that he was booting from a "newfs" made,
level 3 partition. This is what encouraged me to upgrade the level of my
Root&Usr, which was originally level 0. It's the Installer that seems to
have limitations--it will only make old-style file-systems. 

In any case, I've been booting from this partition, as is, for several
months without problems. (I can't remember any farther back than that!) It
always boots from any kernel that's "cp"'d into the root directory. Only I
usually "mv" from the build directory. The consistent and reproducible
feature is that it will boot only if the inode number of the kernel is
less than 47500. You would never see this if you always cp, gunzip, or
otherwise create your kernel file in the root directory.

What I would like to know, is, is anyone able to boot from a kernel with
an inode number (as viewed with ``ls -i'') of 47500 or greater? If so, 
I'll just attribute this to gremlins, and reformat the disk.