From owner-freebsd-questions@FreeBSD.ORG Thu Oct 16 00:25:52 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 706B0BDD for ; Thu, 16 Oct 2014 00:25:52 +0000 (UTC) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3100A925 for ; Thu, 16 Oct 2014 00:25:51 +0000 (UTC) Received: from r56.edvax.de (port-92-195-30-92.dynamic.qsc.de [92.195.30.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id 5E53527652; Thu, 16 Oct 2014 02:25:50 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id s9G0Pnl6005087; Thu, 16 Oct 2014 02:25:50 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Thu, 16 Oct 2014 02:25:49 +0200 From: Polytropon To: "William A. Mahaffey III" Subject: Re: Noob question .... Message-Id: <20141016022549.e9052163.freebsd@edvax.de> In-Reply-To: <543F105A.1090704@hiwaay.net> References: <543F041D.7030206@hiwaay.net> <20141016013646.34d542e6.freebsd@edvax.de> <543F0863.60205@hiwaay.net> <20141016020025.27547cc0.freebsd@edvax.de> <543F105A.1090704@hiwaay.net> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Questions !!!! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2014 00:25:52 -0000 On Wed, 15 Oct 2014 19:24:58 -0500, William A. Mahaffey III wrote: > On 10/15/14 19:00, Polytropon wrote: > > > > > There isn't much work to do: freebsd-update does it out of the box. > > Just keep in mind that you can only use it to track -RELEASE, either > > follow the -RELEASE branch and add security updates, or increase the > > -RELEASE version number. Dealing with a custom kernel is also > > possible, but as few "custom additions" you have, the happier > > freebsd-update will be. :-) > > https://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html > > See 24.2.3. for details about program invocation. > > *Booooyah* !!!! That web page mentions keeping a GENERIC kernel in > /boot/GENERIC. I have *NO* plans to start using custom kernels, but if I > cracked up & decided to, what exactly needs to be copied into > /boot/GENERIC ? Just checking It's not a bad idea to have such a kernel in place, just for the case that you can't currently imagine. When such a case happens, you can "boot GENERIC" and have a kernel that reliably works (because that's what GENERIC has been designed for). It doesn't take much space to do so, and it does not interfere with the rest of the system. You simply copy the whole /boot/kernel/* directory content to /boot/GENERIC/, which contains the kernel modules as well as the kernel itself. I think in case of the -RELEASE set, the *.symbol files will also be included. # cd /boot # cp -r kernel GENERIC The "make installkernel" procedure creates a backup of the previous kernel (which _could_ be the GENERIC kernel, but doesn't have to be). By providing your own GENERIC backup, you'll be safe in case of a failed kernel update. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...