Re: make "quickworld"? (like in DragonFly)
On Sun, Aug 15, 2004 at 09:53:30AM -0700, Brooks Davis wrote: > On Sat, Aug 14, 2004 at 10:03:37AM +0200, Geert Hendrickx wrote: > > On Wed, Aug 11, 2004 at 02:47:14PM +0200, Simon L. Nielsen wrote: > > > On 2004.08.11 00:36:06 +0200, Geert Hendrickx wrote: > > > > Hi, > > > > > > > > is there any way (or could it be implemented) to rebuild only the > > > > changes in world and kernel sources after a cvsup? DragonFly BSD > > > > features "make quickworld" and "make quickkernel" which does exactly > > > > that. > > > > > > You can do that already: > > > > > > make buildworld buildkernel -DNOCLEAN > > > > Does adding "NOCLEAN=true" to /etc/make.conf have the same effect? > > Yes, but it's likely to attract flames because NOCLEAN does fail. If > you forget it's in your make.conf there's a good chance you could report > a bug that isn't a bug a waste a bunch of developer time. > Yes, please don't use NOCLEAN routinely. It's certainly okay to use it if you started a clean build, it failed for some reason, you corrected a cause, and want to resume. If may also work if you've updated the sources, but no guarantees -- often it has been shown that "make clean" is necessary to remove some old cruft that now conflicts with the new sources. For example, if compiler sources have been updated, it can generate different code, but foo.o will only depend on foo.c, and will not be rebuilt if you use -DNOCLEAN. In short, don't use it if you don't fully understand all the consequences. ;) Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgpGOBsMPHhOT.pgp Description: PGP signature
Re: make "quickworld"? (like in DragonFly)
On Sat, Aug 14, 2004 at 10:03:37AM +0200, Geert Hendrickx wrote: > On Wed, Aug 11, 2004 at 02:47:14PM +0200, Simon L. Nielsen wrote: > > On 2004.08.11 00:36:06 +0200, Geert Hendrickx wrote: > > > Hi, > > > > > > is there any way (or could it be implemented) to rebuild only the > > > changes in world and kernel sources after a cvsup? DragonFly BSD > > > features "make quickworld" and "make quickkernel" which does exactly > > > that. > > > > You can do that already: > > > > make buildworld buildkernel -DNOCLEAN > > Does adding "NOCLEAN=true" to /etc/make.conf have the same effect? Yes, but it's likely to attract flames because NOCLEAN does fail. If you forget it's in your make.conf there's a good chance you could report a bug that isn't a bug a waste a bunch of developer time. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgpveCRjI1kiI.pgp Description: PGP signature
Re: make "quickworld"? (like in DragonFly)
On Wed, Aug 11, 2004 at 02:47:14PM +0200, Simon L. Nielsen wrote: > On 2004.08.11 00:36:06 +0200, Geert Hendrickx wrote: > > Hi, > > > > is there any way (or could it be implemented) to rebuild only the > > changes in world and kernel sources after a cvsup? DragonFly BSD > > features "make quickworld" and "make quickkernel" which does exactly > > that. > > You can do that already: > > make buildworld buildkernel -DNOCLEAN Does adding "NOCLEAN=true" to /etc/make.conf have the same effect? GH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ISA card and if_ed as module
[keep replies to the list and I'll catch up later, thanks] > : Is it to be expected that the kernel if_ed.ko module appears to > : be unable to probe and attach an ISA NIC, while when I build the > Yes and No. If the ISA nic is PNP, it will just work. IF not, you > have to have the 'hints' in the kernel. I have the hints framework > backported, but I don't know if it was ever committed. Too old for pnp, so I'm out of luck there. I have hints on my -stable machine (for other reasons), and I can see that they show up in the `loader' environment, but that still isn't enough to probe the device. I'll assume this means that hints doesn't work (hasn't been backported) in -stable. Would it be possible for me to get a copy of your work to see if that's enough to make the NIC appear? A pointer would suffice -- particularly if others would want to try it -- unless you prefer to mail it. (I've looked quickly for obvious differences between -stable and -current that would be relevant but don't really see them) And yes, the NIC does show up in -current, so while part of the framework is in -stable, actually turning those environment hints into action just doesn't happen. thanks barry bouwsma ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
