Date: Wed, 28 May 2003 12:07:32 +0200 From: Marcin Dalecki <mdcki@gmx.net> To: Daniel O'Connor <doconnor@gsoft.com.au> Cc: freebsd-current@freebsd.org Subject: Re: policy on GPL'd drivers? Message-ID: <3ED48A64.7070405@gmx.net> In-Reply-To: <200305281840.46645.doconnor@gsoft.com.au> References: <200305281350.27953.doconnor@gsoft.com.au> <200305281447.02322.doconnor@gsoft.com.au> <20030528.030900.55833611.imp@bsdimp.com> <200305281840.46645.doconnor@gsoft.com.au>
index | next in thread | previous in thread | raw e-mail
Daniel O'Connor wrote: > On Wed, 28 May 2003 18:39, M. Warner Losh wrote: > >>: > : Maybe the kernel build stuff can look in /usr/local/src/sys/modules >>: > : for things to build or something.. >>: > >>: > YUCK! >>: >>: *WHY?* >>: >>: I have asked this before BTW, and I haven't been told why it sucks. >> >>Because there are other, more elegant ways of dealing with these >>things. I don't like /usr/local/src anything, which was the main >>complaint. > > > If there are more elegant solutions I would like to know what they are. Trivial: ./buildmykernel where buildmykernel contains something along the lines of: #!/bin/sh # My rebuild procedure ( cd /usr/src/; make buildkernel; make installkernel ) && \ ( cd /usr/ports/comms/ltxxx; make; make deinstall; make reinstall ) Don't forget the shell! Automatin is the easiest way to handle repeating tasks. As an added bonus it is documenting the decisions you have made.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3ED48A64.7070405>