From owner-cvs-all Tue Feb 27 6:56:21 2001 Delivered-To: cvs-all@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 8C4E637B71D; Tue, 27 Feb 2001 06:56:07 -0800 (PST) (envelope-from julian@elischer.org) Received: from elischer.org (i079-084.nv.iinet.net.au [203.59.79.84]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id WAA22823; Tue, 27 Feb 2001 22:55:41 +0800 Message-ID: <3A9BBFC5.47C850E1@elischer.org> Date: Tue, 27 Feb 2001 06:55:01 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Peter Wemm Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/conf NOTES src/sys/conf files.alphafiles.i386 files.pc98 References: <200102271235.f1RCZK726878@mobile.wemm.org> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > > Julian Elischer wrote: > > Peter Wemm wrote: > > > > > > peter 2001/02/27 00:11:29 PST > > > > > > Modified files: > > > sys/i386/conf NOTES > > > sys/conf files.alpha files.i386 files.pc98 > > > Log: > > > Add and document the LINPROCFS option, so that we can build linprocfs > > > (either as a module or in the kernel) after sys/modules/* dies. > > ^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > errrrrrr care to explain this? > > is it planned? > > I don't think I'm parsing this correctly. > > sys/modules was always a temporary hack, which is why we have gone to a lot > of trouble to not put source code or other files in there. I have a patch > that uses a unified build mechanism so that we avoid the duplicate > building. It builds modules and kernel at the same time. The unified build > is working, but not quite right yet. I always test by stuff during development by cd /sys/modules/netgraph cp -pr UI NEW_THING cd NEW_THING vi Makefile #point to new sources make depend; make this allows me to test jsut the new module without building the entire kernel. Specifically I may not even be ABLE to build a real kernel if the tree is broken but I don't care.. I can still build my module and work on killing warnings etc. without having to have a working config or even any built kernels. Will I still be able to do this? If I can cd to /sys/dev/ed and do "make module" that would suit me. > > Cheers, > -Peter > -- > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > "All of this is for nothing if we don't go to the stars" - JMS/B5 -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message