From owner-freebsd-questions@FreeBSD.ORG Thu Oct 16 00:28:39 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 88B60DF1 for ; Thu, 16 Oct 2014 00:28:39 +0000 (UTC) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (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 52D82955 for ; Thu, 16 Oct 2014 00:28:38 +0000 (UTC) Received: from kabini1.local (rbn1-216-180-19-94.adsl.hiwaay.net [216.180.19.94]) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id s9G0SbHi004805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Wed, 15 Oct 2014 19:28:37 -0500 Message-ID: <543F12AB.6070606@hiwaay.net> Date: Wed, 15 Oct 2014 19:34:51 -0500 From: "William A. Mahaffey III" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 CC: "FreeBSD Questions !!!!" Subject: Re: Noob question .... References: <543F041D.7030206@hiwaay.net> <20141016013646.34d542e6.freebsd@edvax.de> <543F0863.60205@hiwaay.net> <20141016020025.27547cc0.freebsd@edvax.de> <543F105A.1090704@hiwaay.net> <20141016022549.e9052163.freebsd@edvax.de> In-Reply-To: <20141016022549.e9052163.freebsd@edvax.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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:28:39 -0000 On 10/15/14 19:25, Polytropon wrote: > 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. Excellent, thx. -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.