From owner-freebsd-current@FreeBSD.ORG  Sat Aug 13 19:51:28 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 1233)
	id 05D2D106566C; Sat, 13 Aug 2011 19:51:28 +0000 (UTC)
Date: Sat, 13 Aug 2011 19:51:28 +0000
From: Alexander Best <arundel@freebsd.org>
To: freebsd-current@freebsd.org
Message-ID: <20110813195127.GA34295@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [rfc] replacing /boot/kernel.old with a unique directory name
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Aug 2011 19:51:28 -0000

hi there,

i just had the following idea: how about instead of copying the current kernel
to /boot/kernel.old and then installing the new one under /boot/kernel as the
results of target installkernel, we create a unique directory name for the old
kernel?

something like /boot/kernel-r${revision}-${/dev/random}?

that would let people not only boot the previous kernel, but all kernels that
have been replaced by target installkernel. this would make tracking issues,
which have been introduced by a certain commit much easier, imho.

i don't think implementing this logic would be that difficult. the only problem
i see is with ${/dev/random} in the case where people are running a kernel
without /dev/{u}random support.

cheers.
alex