From owner-freebsd-current@FreeBSD.ORG  Thu Oct 30 13:10:41 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@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 9630D7E6
 for <freebsd-current@freebsd.org>; Thu, 30 Oct 2014 13:10:41 +0000 (UTC)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com
 [IPv6:2607:f8b0:4001:c05::22b])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 58A80952
 for <freebsd-current@freebsd.org>; Thu, 30 Oct 2014 13:10:41 +0000 (UTC)
Received: by mail-ig0-f171.google.com with SMTP id hl2so3248026igb.10
 for <freebsd-current@freebsd.org>; Thu, 30 Oct 2014 06:10:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:from:date:message-id
 :subject:to:cc:content-type;
 bh=b2z5ALMFwDF274rch8qVyVFZii6PkqAgvs8amup2pFg=;
 b=taPYqkpSMVQU5yEIea3kxjkphnTjcxEFs7dMF3PQqwZhT6jmjmLwCu5oIKK6Q9Ja8D
 dHBWjRRAS3UGwpoeNV8crxLSr0cLqxOCoCvvqf+3MND2SE0JwOGNod+xdPG1sEM6nkvY
 fP9/gqGc7pW3DtsplCt5IufeL0wX02sSS6cWBqokQtvnv8gKfINsBYXeuHdeFzjVU/Vy
 deiy3APTLaVhe9AxC3wHjKhHWMwXLD9e1soQm1VbYMpZ9EecjMlvFFP/noQnwWfapXtd
 bxZxlnx7/tgCjTBoEYJLoKLSMLjeOj160VLPIcYbxURNw4BAJjeVyeaHxxJz8Tg2F+t1
 TwEw==
X-Received: by 10.107.13.137 with SMTP id 131mr19824491ion.2.1414674640627;
 Thu, 30 Oct 2014 06:10:40 -0700 (PDT)
MIME-Version: 1.0
Sender: carpeddiem@gmail.com
Received: by 10.107.29.207 with HTTP; Thu, 30 Oct 2014 06:10:19 -0700 (PDT)
In-Reply-To: <CAPyFy2AHyau5RhhZ628tbRQWa_smAYntHUrP0Ftd1EW8buZGXg@mail.gmail.com>
References: <CAPyFy2APVUxpAztmWY-ux7gUZ7B8Qk65CLHV_fVYmxsazKgCPg@mail.gmail.com>
 <54511A7E.1020307@multiplay.co.uk>
 <CAPyFy2Bw9JH4w0iZ5hj2R1Ga9T4BZn_Z-8UBJ-jT6tmO+i8VeA@mail.gmail.com>
 <20141030023224.GA42236@troutmask.apl.washington.edu>
 <CAPyFy2AHyau5RhhZ628tbRQWa_smAYntHUrP0Ftd1EW8buZGXg@mail.gmail.com>
From: Ed Maste <emaste@freebsd.org>
Date: Thu, 30 Oct 2014 09:10:19 -0400
X-Google-Sender-Auth: qg8CZheasdh8bkI-PKYXWYp8uPQ
Message-ID: <CAPyFy2DZzxiZUdh4h1ETe2Ozbecnc2-yMOZArfzytCO6c2B=HQ@mail.gmail.com>
Subject: Re: HEADS UP: Standalone kernel debug files moving out of
 /boot/kernel/
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Content-Type: text/plain; charset=UTF-8
Cc: FreeBSD Current <freebsd-current@freebsd.org>,
 Steven Hartland <killing@multiplay.co.uk>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Thu, 30 Oct 2014 13:10:41 -0000

On 30 October 2014 09:07, Ed Maste <emaste@freebsd.org> wrote:
> On 29 October 2014 22:32, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote:
>> On Wed, Oct 29, 2014 at 03:15:50PM -0400, Ed Maste wrote:
>>> On 29 October 2014 12:49, Steven Hartland <killing@multiplay.co.uk> wrote:
>>> > Hmm not sure I like this idea as it would make it more difficult to make a
>>> > copy / backup a kernel.
>>> >
>>> > ATM when I want to copy a kernel for debugging its a one liner, splitting
>>> > debug symbols off to /usr/lib would prevent this.
>>>
>>> To retain the current behaviour you can set DEBUGDIR= (i.e., empty),
>>> as the debug file install path is ${DESTDIR}${DEBUGDIR}${KODIR}.
>>
>> No, you can't.
>>
>> su root
>> cp -pR /boot/kernel /boot/good
>>
>> Where does DEBUGDIR enter the picture?
>
> In your kernel build configuration (src.conf or similar ways).

Oops, that should be "build / install configuration (src.conf or
similar)."  That is, if you set DEBUGDIR= then the debug data will be
installed in the same directory as the kernel / binaries / libraries,
and everything will work as it does today.