From owner-freebsd-current@FreeBSD.ORG Sat Aug 13 19:59:03 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10250106564A; Sat, 13 Aug 2011 19:59:03 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by mx1.freebsd.org (Postfix) with ESMTP id C4C718FC08; Sat, 13 Aug 2011 19:59:02 +0000 (UTC) Received: by iye7 with SMTP id 7so9427295iye.17 for ; Sat, 13 Aug 2011 12:59:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=THd7GZS8pbb6XAcXgts4acpbZdZvYjJEYgyUYv5RGi0=; b=UW8YJuCdVYQtvZyhRLS4DZjBi8zEEsJKjQNnSXe0noq7TPEMI4dOtQ79rua5zfL+Xf jdPCnBcBOTjSJ714SW9fh1QpMh4pRo4XI1ML2r7366e/bUn8Gr0l4g6WrUiQ+e0VVYiP pQL3MHBi3mWNaMQMLM2PXoO3UbjW9yv5MsCEU= Received: by 10.231.56.75 with SMTP id x11mr4072264ibg.98.1313265542087; Sat, 13 Aug 2011 12:59:02 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.182.77 with HTTP; Sat, 13 Aug 2011 12:58:32 -0700 (PDT) In-Reply-To: <20110813195127.GA34295@freebsd.org> References: <20110813195127.GA34295@freebsd.org> From: Chris Rees Date: Sat, 13 Aug 2011 20:58:32 +0100 X-Google-Sender-Auth: Si7rDjUoEu6WbUyywddVCYJg5m4 Message-ID: To: Alexander Best Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Aug 2011 19:59:03 -0000 On 13 August 2011 20:51, Alexander Best wrote: > 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 mktemp? Chris