Date:        Fri, 14 Jan 2005 11:54:22 +0100
    From:        Tim Jakobsen <tja@jakobsen.vg>
    Message-ID:  <20050114105422.GB417@emperor.jakobsen.vg>

  | I did try setting the NETBSD_RELEASE="2.0" in the default.conf file.
  | This should make a /libkver_osrelease file in the sandbox to fake the
  | uname info but it doesn't do that. I tried making the file myself but
  | still no change. 

You need libkver installed as well, though I think the NETBSD_RELEASE
setting is supposed to cause it to be built & installed for you (when
the sandbox is created).   Sorry, didn't read carefully enough in your
first message to notice that you had this set already.

As Julio said, all this needs to be done when the sandbox is created.

The other thing I forgot to mention in my previous message, is that
provided that you actually had the 2.0 sets installed in the sandbox
when you built the packages, then essentially all of them are going to
work fine, regardless of the kernel version warning (there will be just
a couple that might not, perhaps lsof or others of that nature).

kre