Date: Wed, 16 Aug 1995 08:08:35 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: procfs problems in -current? Message-ID: <199508160608.IAA02626@uriah.heep.sax.de> In-Reply-To: <9508152259.AA07894@cs.weber.edu> from "Terry Lambert" at Aug 15, 95 04:59:10 pm
next in thread | previous in thread | raw e-mail | index | archive | help
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. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508160608.IAA02626>