Date: Wed, 13 Feb 2008 18:43:43 -0800 From: "Kevin Oberman" <oberman@es.net> To: Gavin Spomer <spomerg@cwu.EDU> Cc: freebsd-stable@freebsd.org Subject: Re: Rebuilding World Problems Message-ID: <20080214024343.979114500F@ptavv.es.net> In-Reply-To: Your message of "Wed, 13 Feb 2008 11:12:45 PST." <47B2D0AD0200009000013E4F@hermes.cwu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_1202957023_41010P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Wed, 13 Feb 2008 11:12:45 -0800 > From: Gavin Spomer <spomerg@cwu.EDU> > Sender: owner-freebsd-stable@freebsd.org > > >>> Kevin Oberman <oberman@es.net> 02/12/08 7:01 PM >>> > > > make buildkernel KERNCONF=YOUR_KERNEL_HERE > > > make installkernel KERNCONF=YOUR_KERNEL_HERE > > If you put KERNCONF into make.conf, you can simplify it to: > > make kernel > > Just to be clear, if I add the appropriate KERNCONF line in > /etc/make.conf, "make kernel" will take care of both "make > buildkernel" AND "make installkernel"? (w/o the KERNCONF= part) Actually, this is really two things that I concatenated just to confuse everyone. 1. "make kernel" is simply defined in the Makefile as 'make buildkernel && make installkernel'. 2. KERNCONF=YOUR_KERNEL_HERE in make.conf allows you to not need to specify the kernel config file name every time you make. Combine the two and you reduce: make buildkernel KERNCONF=YOUR_KERNEL_HERE make installkernel KERNCONF=YOUR_KERNEL_HERE to: make kernel Of course, if you are building now and not re-booting until later, combining the two steps may not be a good idea, but most people do upgrades to their own systems (as opposed to servers or farms) in immediate sequence. > > > > reboot (in single user mode) > > > > > > fsck -p (optional, but a good idea) > > A total waste of time, but I do it anyway since I am paranoid. > > adjkerntz -i > > Like many good admins, I am paranoid too, so I will include this. :) > > > This command has no impact if the hardware clock is set to UTC/GMT, but > > it is often not, especially if the system is dual boot with Windows. > > > mount -u / > > Since the next command does this, the is no need for this, even for the > > paranoid. > > > mount -a -t ufs > > > swapon -a (most cases; optional) > > > > > > cd /usr/src > > > mergemaster -p > > > make installworld > > > mergemaster > > While not in src/UPDATING, I always urge people to use the -iU options > > to save a LOT of time on future builds. > > These options are for mergemaster I take it? I had another look at the > man page for mergemaster and inspected these options, so this sounds > good. '-i' will install newly added files without asking. It save a bit of time. '-U' uses saved MD5 hashes so that files that have never been modified from default are updated without interaction. This is a huge time saver. (Of course, it does not help the first time you run mergemaster, but it will every time in the future. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1202957023_41010P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFHs6rfkn3rs5h7N1ERAiUSAKCteXxVqAEUsX0sXntq+QP69MvUdQCeKRhz H+wToTwMpgw/rgLD9wb/S7k= =5b4b -----END PGP SIGNATURE----- --==_Exmh_1202957023_41010P--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080214024343.979114500F>