From owner-freebsd-current@FreeBSD.ORG Tue Feb 24 21:20:43 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2362D106566B for ; Tue, 24 Feb 2009 21:20:43 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.freebsd.org (Postfix) with ESMTP id 037718FC15 for ; Tue, 24 Feb 2009 21:20:42 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id 70AF01A000EAB for ; Tue, 24 Feb 2009 13:20:42 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at smtp.sd73.bc.ca Received: from coal.localnet (s10.sbo [192.168.0.10]) by smtp.sd73.bc.ca (Postfix) with ESMTP id 11B491A000B0E for ; Tue, 24 Feb 2009 13:20:41 -0800 (PST) From: Freddie Cash To: freebsd-current@freebsd.org Date: Tue, 24 Feb 2009 13:20:40 -0800 User-Agent: KMail/1.11.0 (Linux/2.6.26-1-686; KDE/4.2.0; i686; ; ) References: <1235502625.4345.2.camel@localhost.localdomain> <49A45558.9060000@math.missouri.edu> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902241320.40451.fjwcash@gmail.com> Subject: Re: Default FS Layout Too Small? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2009 21:20:43 -0000 On February 24, 2009 1:03 pm Rick Macklem wrote: > On Tue, 24 Feb 2009, Stephen Montgomery-Smith wrote: > > Sean Bruno wrote: > > cd /usr/src > > make installkernel > > .... this dies with a "file system full" error > > rm -r /boot/kernel.old > > make installkernel > > Although I wouldn't recommend it "in general", for your case I would > make sure everything you need is configured into the kernel you build > (so it doesn't need any loadable modules) and then: > > cd /usr/src/sys//compile/GENERIC > mkdir /boot/kernel.new > cp kernel /boot/kernel.new > > so that you can boot the new one and see it work before deleting the > old one. cd /usr/src make KERNCONF=WHATEVER buildkernel make KERNCONF=WHATEVER KODIR=/boot/kernel.new installkernel nextboot -k kernel.new reboot That will install the new kernel into a separate directory, and will cause the next boot *only* to use the new kernel. If things fail, you just reboot, and it goes back to the old kernel. If things work, then it's a simple rename of the kernel directory: cd /boot mv kernel kernel.old mv kernel.new kernel reboot KODIR and nextboot are very handy ... especially for remote upgrades. -- Freddie fjwcash@gmail.com