On Mon, 27 May 2002 @ 1:09pm (-0400), Joseph St. Onge wrote:

JSO> This complicates things greatly.  Anyone time to rebuild a new snapshot
JSO> (or fix that tarball)?
JSO>
JSO> I manually unpacked/used the kernel in:
JSO>
JSO> $snapshotdir/install/binary/kernel/netbsd-GENERIC.gz
JSO>
JSO> ...except that kernel freezes when it tries to access rootdev (wd0a in

Joseph et All:

I've placed a freshly compiled sparc64 kernel up at:

http://digitalfreaks.org/~lavalamp/netbsd/current-052902-sparc64-GENERIC-rev_1.147-rev32_1.39.bz2

It's a GENERIC build from rev 1.47 of GENERIC and rev 1.39 of GENERIC32.

....of course, that's a moot point considering the announcement of
releng.netbsd.org I just read...

-lava

JSO> my case).  Is there any way to pass the kernel a flag from openboot to
JSO> specify a rootdev (checking google now).  I don't want to try an older
JSO> kernel from an older snapshot (bootblock mismatches, etc.)
JSO>
JSO> I'll try to get bootparams to specify a rootdev.
JSO>
JSO> -gf
JSO>
JSO> Tim Goodwin wrote:
JSO>
JSO> > Tomi Nylund <wizard@finland.invalid> writes:
JSO> >
JSO> >
JSO> >>I tried installing the 1.5ZC today, and ran into a strange problem:
JSO> >>pax wouldn't unpack the kern-GENERIC.tgz from binary/sets, no matter
JSO> >>what.
JSO> >>
JSO> >
JSO> > I can't shed much light on this, except to say that I experienced
JSO> > exactly the same problem (and worked around it in the same way) with a
JSO> > release that I built for local consumption on 2002-05-09.
JSO> >
JSO> > In other words, I think this is (or was) a generic problem in the
JSO> > build process, and not, say, a one-off corrupted file.
JSO> >
JSO> > Tim.
JSO> >
JSO> >