From owner-freebsd-current@freebsd.org Mon Jan 18 01:25:25 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B1F0A867A2 for ; Mon, 18 Jan 2016 01:25:25 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (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 065A112E7 for ; Mon, 18 Jan 2016 01:25:24 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id u0I1Q6Gr037587 for ; Sun, 17 Jan 2016 17:26:12 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: "FreeBSD CURRENT" From: "Chris H" Subject: ATA_STATIC_ID removal Date: Sun, 17 Jan 2016 17:26:12 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <2244d431234bc14fe3b4695507c763be@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Mon, 18 Jan 2016 01:25:25 -0000 Greetings, I just fired off a buildworld w/o *completely* reading UPDATING. Only to discover that ATA_STATIC_ID was removed between my last build on this box, and the one building now. Will the fact that my KERNCONF for this build contains ATA_STATIC_ID cause me any grief? Thanks for any input! --Chris --