From owner-freebsd-stable@FreeBSD.ORG Thu Mar 6 13:29:01 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECA8B106566B; Thu, 6 Mar 2008 13:28:59 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id C6F6D8FC21; Thu, 6 Mar 2008 13:28:59 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 89DFA1CC033; Thu, 6 Mar 2008 05:28:59 -0800 (PST) Date: Thu, 6 Mar 2008 05:28:59 -0800 From: Jeremy Chadwick To: Ivan Voras Message-ID: <20080306132859.GA88810@eos.sc1.parodius.com> References: <47CE6C6B.8060306@bluegod.net> <47CFE384.4060607@bluegod.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-stable@freebsd.org Subject: Re: kernel backup on 7.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Mar 2008 13:29:01 -0000 On Thu, Mar 06, 2008 at 01:58:08PM +0100, Ivan Voras wrote: > James López (BLuEGoD) wrote: > > > Not exactly.. What I mean is that I want to reinstall FreeBSD due to > > some accidentally deleted files and a behavior on sendfile :S > > So I would like to know if I can backup /boot and the overwrite it once > > I have freebsd installed again... > > Yes. If you don't change FreeBSD versions or hardware, this will work. Clarification: it _might_ work. You need to keep in mind that the kernel/modules he's backing up will very likely *not* match all the binaries he has on his disks, library calls, possibly system calls, etc. etc... This is why building world includes both all the binaries *as well* as the kernel. The reason I point this out is, when certain things in kernel-land change which certain programs rely upon (but haven't been recompiled to be aware of that change), odd things can happen. The most "famous" of the bunch is when top(1) or ps(1) start failing in bizarre ways. Thus, my point: it *probably* will work, but DO NOT assume that it will. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |