From owner-freebsd-questions@FreeBSD.ORG  Thu Nov 20 00:42:36 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 691F33EE
 for <freebsd-questions@freebsd.org>; Thu, 20 Nov 2014 00:42:36 +0000 (UTC)
Received: from mail.ferrarishields.com (mail.ferrarishields.com [75.140.46.78])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4F4B2F94
 for <freebsd-questions@freebsd.org>; Thu, 20 Nov 2014 00:42:35 +0000 (UTC)
Received: from danco (dan [10.70.153.20]) (Authenticated sender: dan)
 by mail.ferrarishields.com (Postfix) with ESMTPSA id 8AAA0435AA3;
 Wed, 19 Nov 2014 16:36:01 -0800 (PST)
Reply-To: <dan@ferrarishields.com>
From: "Dan O'Connor" <dan@ferrarishields.com>
To: "'Erich Dollansky'" <erichsfreebsdlist@alogt.com>,
 "'Marko Turk'" <markoml@markoturk.info>
References: <20141119184230.GA36984@vps.markoturk.info>
 <20141120081504.4c04d4c0@X220.alogt.com>
In-Reply-To: <20141120081504.4c04d4c0@X220.alogt.com>
Subject: RE: Handbook update section for custom kernel
Date: Wed, 19 Nov 2014 16:35:58 -0800
Organization: Ferrari Shields & Associates
Message-ID: <033101d00459$f41b61a0$dc5224e0$@ferrarishields.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQJwRGTf83yUMdbBrGJSp4VLm1LfhAGy5vaDmxqRPyA=
Content-Language: en-us
Cc: freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Nov 2014 00:42:36 -0000

> 
> Hi,
> 
> On Wed, 19 Nov 2014 19:42:30 +0100
> Marko Turk <markoml@markoturk.info> wrote:
> 
> > in handbook, section 24.2.3.1. Custom Kernels with FreeBSD 9.X and
> > Later says:
> > "Before using freebsd-update, ensure that a copy of the GENERIC kernel
> > exists in /boot/GENERIC. If a custom kernel has only been built once,
> > the kernel in /boot/kernel.old is the GENERIC kernel. Simply rename
> > this directory to /boot/kernel."
> >
> > Should the last sentence be
> > "Simply rename this directory to /boot/GENERIC."
> >
> > or am I missing something?
> >
> shouldn't it be /boot/kernel in all cases? I have never seen a
/boot/GENERIC on
> my machines. Not even after a fresh install.
> 
> Erich

Mark, is correct. 

Your newnly-built custom kernel is /boot/kernel. mv'ing /boot/kernel.old to
/boot/kernel will overwrite the newly built custom kernel with the old
GENERIC kernel.

Instead, rename /boot/kernel.old to /boot/GENERIC (I use
/boot/kernel.GENERIC) to preserve the old GENERIC kernel...

Remember, this applies to the first time you build your custom kernel. After
subsequent kernel builds, /boot/kernel.old will be your old custom kernel.
Don't overwrite your saved GENERIC kernel with an old custom kernel!

-Dan