On Tue, 26 Sep 2006 10:38:43 -0700, "Kevin Oberman" <[EMAIL PROTECTED]> wrote:
[...] >> >About the only thing you should put in make.conf is the name of your >> >kernel config file: >> >KERNCONF=MY_SYS would cause the config file /sys/i386/conf/MY_SYS to be >> >used, assuming it's an i386 system. >> >> OK. Is that equivalent to declaring it as a make command parameter: >> | make buildkernel KERNCONF=MY_SYS >> or do I really need to put it in make.conf? > >It's the equivalent. It just allows you to leave it off of the make >command and i entirely optional. (Note that /etc/make.conf does not even >exist by default, but will be created if you install Perl.) [...] > >By "in-sync", I mean that world and kernel were either built from the >same sources or you understand any changes well enough to know that >there will be no adverse impact. (Unless you are hacking kernel code, >the second option is null and the sources should be the same.) > >If I understand what you did, you now have a 6.1 world and >6.2-PRERELEASE kernel. This is not likely to work well, I'm afraid. :-( > >FWIW, I have an AMD K6 at home and it's pretty painfully slow building >world or the kernel on that system (and it's 450 MHz). You don't even >want to think about building Gnome! Well, buildworld fell over - but was just that I ran out of space on /usr. Instead of building world again, I decided to: | make clean | make buildkernel KERNCONF=MYKERNEL | make installkernel KERNCONF=MYKERNEL That all completed successful. I had assumed that: | make buildkernel KERNCONF=MYKERNEL was equivalent to: | config MYKERNEL | cd ../compile/MYKERNEL | make cleandepend | make depend | make and would fall over too without building world first, but it seems not. Thanks for your help. Geoff _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
