From owner-freebsd-current@FreeBSD.ORG Mon Oct 28 16:58:05 2013 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 41040EEC; Mon, 28 Oct 2013 16:58:05 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B77222D5E; Mon, 28 Oct 2013 16:58:04 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.7/8.14.7) with ESMTP id r9SGw2u1053794; Mon, 28 Oct 2013 20:58:02 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.7/8.14.7/Submit) id r9SGw2is053793; Mon, 28 Oct 2013 20:58:02 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 28 Oct 2013 20:58:02 +0400 From: Gleb Smirnoff To: drosih@rpi.edu Subject: Re: [heads up] axing AppleTalk and IPX/SPX Message-ID: <20131028165802.GX52889@glebius.int.ru> References: <201310281648.r9SGmlQQ008874@smtp10.server.rpi.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201310281648.r9SGmlQQ008874@smtp10.server.rpi.edu> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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, 28 Oct 2013 16:58:05 -0000 On Mon, Oct 28, 2013 at 12:49:14PM -0400, drosih@rpi.edu wrote: d> As far as the kernel-level support, I assume you're just removing all d> the code tied to the kernel options NETATALK and NETATALKDEBUG? Or does d> it entail some other changes, which might wreck my custom compile of CAP? Yes, that is the plan. If remove of NETATALK hurts your build, we can work this out. Either leave some header in system, or move it into your custom build. -- Totus tuus, Glebius.