Date: Tue, 27 Feb 2001 19:21:08 -0800 From: Peter Wemm <peter@netplex.com.au> To: Julian Elischer <julian@elischer.org> 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 Message-ID: <200102280321.f1S3L8734246@mobile.wemm.org> In-Reply-To: <3A9BBFC5.47C850E1@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer wrote: > 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. This isn't quite in a final usable form, but there are two points that I want to make. - the existing duplicated infrastructure in modules/* can go away, but there is nothing stopping you doing a custom module for the time being. Use of .include <bsd.kmod.mk> would still work for a while, but our standard modules would come with the kernel build. - when this is finished, you will be able to (in some form or another) cp GENERIC MYMOD and then edit out the devices, leaving just 'module ng_foo'. Doing a make will result in ng_foo.ko being built on its own without an associated kernel. ie: you will be able to build a "GENERIC" portable module without any trouble. The syntax and exact mechanism to do this is still being kicked around but there are several viable ones including quick command line based stuff. (eg: buildmod GENERIC mymod.ko) Note that these dont require a kernel compile. Dont worry too much, there will be an easy way to do it. (There has to be or people will kill 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102280321.f1S3L8734246>