From owner-freebsd-current@FreeBSD.ORG Mon Jun 20 18:48:39 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E04716A41C; Mon, 20 Jun 2005 18:48:39 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (vc4-2-0-66.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 233E643D1D; Mon, 20 Jun 2005 18:48:39 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1]) by harmony.village.org (8.13.3/8.13.3) with ESMTP id j5KIllNX026470; Mon, 20 Jun 2005 12:47:49 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 20 Jun 2005 12:49:05 -0600 (MDT) Message-Id: <20050620.124905.35871665.imp@bsdimp.com> To: rwatson@freebsd.org From: "M. Warner Losh" In-Reply-To: <20050619012425.L56734@fledge.watson.org> References: <20050619012425.L56734@fledge.watson.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: dhclient less functional with nanobsd because of NO_CXX 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: Mon, 20 Jun 2005 18:48:39 -0000 In message: <20050619012425.L56734@fledge.watson.org> Robert Watson writes: : : Observation on dependencies between components and nanobsd: : : In the old world order, dhclient backgrounded and waited for the link : state to come up. In the new world order, dhclient exits if the link : state is down, relying on devd to restart it. devd isn't build if NO_CXX : is set, as it's written in C++, and NO_CXX is a useful (and default) thing : to set for nanobsd for obvious reasons. It sounds like something here is : an argument for: : : - Allowing C++ to be built as a build dependency, but not installed. : - Rewriting devd to not be in C++. : - Providing an option so that dhclient's old and useful behavior can be : restored. It is generally desirable to have a separate 'install' environemnt from the 'build' environment on real embedded systems. The fact that nanobsd doesn't have this useful distinction is a problem with nanobsd, not devd. It should build everything, but install with all the NO_XXX flags set to do subsetting. devd won't be rewritten to not use C++. That's a non-option. Warner