From owner-freebsd-current  Mon Nov  4 12:46:59 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA26443
          for current-outgoing; Mon, 4 Nov 1996 12:46:59 -0800 (PST)
Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA26391
          for <freebsd-current@FreeBSD.org>; Mon, 4 Nov 1996 12:46:15 -0800 (PST)
Received: from x14.mi.uni-koeln.de (annexr2-40.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA09645
  (5.67b/IDA-1.5 for <freebsd-current@FreeBSD.org>); Mon, 4 Nov 1996 21:36:10 +0100
Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.2/8.6.9) id VAA02139; Mon, 4 Nov 1996 21:36:10 +0100 (MET)
Message-Id: <199611042036.VAA02139@x14.mi.uni-koeln.de>
Date: Mon, 4 Nov 1996 21:36:10 +0100
From: se@zpr.uni-koeln.de (Stefan Esser)
To: richardc@CSUA.Berkeley.EDU (Veggy Vinny)
Cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch),
        freebsd-current@FreeBSD.org (FreeBSD-current users)
Subject: Re: ncrcontrol in -current
In-Reply-To: <Pine.PTX.3.95.961103164657.24523z-100000@soda.CSUA.Berkeley.EDU>; from Veggy Vinny on Nov 3, 1996 16:47:48 -0800
References: <Pine.PTX.3.95.961103164657.24523z-100000@soda.CSUA.Berkeley.EDU>
X-Mailer: Mutt 0.45
Mime-Version: 1.0
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Veggy Vinny writes:
> 
> 
> On Mon, 4 Nov 1996, J Wunsch wrote:
> 
> > As Veggy Vinny wrote:
> > 
> > > 	the ncrcontrol program seems to not work in -current after I
> > > rebuilt the binary just to confirm this.
> > > 
> > > root@bigbang [4:07pm] [~]>> ncrcontrol
> > > 
> > > ncrcontrol: incompatible with kernel. Rebuild!
> > 
> > Mine is working.  Both, /kernel and /usr/sbin/ncrcontrol are dated
> > Oct 28.
> 
> 	Mines are dated November 3.

The reason for a mismatch (if both ncrcontrol and the kernel
were in fact built from corresponding sources) is that you
specified some kernel config option (i.e. the maximum number
of LUNs or TAGs) that have not become visible to the build
process for ncrcontrol.

So, please add those kernel options to the ncrcontrol Makefile
and rebuilt ncrcontrol, if that might be the cause of your 
problem.

I'm going to make ncrcontrol find all the parameters by some
other means (not from compile time options, that is :), but 
this is not on top of my ToDo list ...

Rgeards, STefan