From owner-freebsd-current Tue Aug 15 23:20:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id XAA10083 for current-outgoing; Tue, 15 Aug 1995 23:20:40 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id XAA10075 for ; Tue, 15 Aug 1995 23:20:36 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA03380; Wed, 16 Aug 1995 08:20:33 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id IAA19488 for freebsd-current@FreeBSD.org; Wed, 16 Aug 1995 08:20:32 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id IAA02626 for freebsd-current@FreeBSD.org; Wed, 16 Aug 1995 08:08:36 +0200 From: J Wunsch Message-Id: <199508160608.IAA02626@uriah.heep.sax.de> Subject: Re: procfs problems in -current? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 16 Aug 1995 08:08:35 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.org (FreeBSD-current users) In-Reply-To: <9508152259.AA07894@cs.weber.edu> from "Terry Lambert" at Aug 15, 95 04:59:10 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1112 Sender: current-owner@FreeBSD.org Precedence: bulk As Terry Lambert wrote: > > > > ./vnode_if.h: vnode_if.h > > > > What's this? ... > Why do you ask? 8-). Since i've ran into the following trouble: My user `bin' used to have checked out copies from config, sys and lkm (and include, FWIW) below his home directory. This is where everything happens when i'm playing with new stuff in kernelland. Once in a while, whenever i think it's necessary to upgrade the kernel, i `cvs update' those modules and rebuild everything (including, when required, re-configuring). This used to work all the time, but recently, all loaded VFS modules yielded garbage and eventually panicked the system. (The actual reason must have been the changes in the way the mounts are being tracked, i suppose.) It turned out that cvs remove'ing the whole lkm module and checking it out again actually worked, but then this is only an evidence that something in the dependency handling of the Makefiles (or make(1) itself :) is broken. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)