From owner-freebsd-stable Sun Oct 12 20:22:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA10769 for stable-outgoing; Sun, 12 Oct 1997 20:22:08 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA10764 for ; Sun, 12 Oct 1997 20:22:05 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id NAA22033; Mon, 13 Oct 1997 13:18:46 +1000 Date: Mon, 13 Oct 1997 13:18:46 +1000 From: Bruce Evans Message-Id: <199710130318.NAA22033@godzilla.zeta.org.au> To: Arjan.deVet@adv.IAEhv.nl, stable@FreeBSD.ORG Subject: Re: 2.2-stable and /usr/sbin/ncrcontrol: still problems Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>... >>> However, when I tried running '/usr/sbin/ncrcontrol -i', I get 'incompatible >>> with kernel. Rebuild!' >> >>The problem is that "ncrcontrol" accesses some data structure >>in the kernel, and whenever a kernel is built with a different >>definition of that structure, ncrcontrol has to be rebuilt, too. >> >>> Is there something I'm missing here, or should this work? I've not tried >>> using it before, so I have no idea if/when it ever worked here. It shouldn't work with the GENERIC kernel in any version of 2.2 or 3.0. >>... >I still see the same problem, even with GENERIC kernel configurations on >both 2.2.1-RELEASE and 2.2-STABLE from a few days ago. I patched >ncrcontrol to print the kernel_version and ncr_version variables: Don't use the GENERIC kernel except for installation. It has the FAILSAFE option (which causes this problem) and other pessimizations. Bruce