From owner-freebsd-questions@FreeBSD.ORG Tue Aug 6 17:46:02 2013 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 38A301DC; Tue, 6 Aug 2013 17:46:02 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F24232BA6; Tue, 6 Aug 2013 17:46:01 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa02.fnfis.com (8.14.5/8.14.5) with ESMTP id r76HjsCa015752 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 6 Aug 2013 12:45:54 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.135]) by LTCFISWMSGHT06.FNFIS.com ([10.132.206.17]) with mapi id 14.02.0309.002; Tue, 6 Aug 2013 12:45:53 -0500 From: "Teske, Devin" To: Polytropon Subject: Re: .sh script code to determine IPv4 or IPv6 Thread-Topic: .sh script code to determine IPv4 or IPv6 Thread-Index: AQHOkDzj3H/8RokAXEKdt073gODRzpmDtomAgAAhnICABNzRgIAABo0AgAAB+4CAAA2OAIAAAeIA Date: Tue, 6 Aug 2013 17:45:52 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D72020071EE@ltcfiswmsgmb21> References: <51FCE9C7.7020407@a1poweruser.com> <20988.61897.78070.312049@jerusalem.litteratus.org> <13CA24D6AB415D428143D44749F57D720200229A@ltcfiswmsgmb21> <52012235.3050006@ssimicro.com> <20130806184332.ff7f0c4d.freebsd@edvax.de> <13CA24D6AB415D428143D44749F57D7202006F51@ltcfiswmsgmb21> <20130806193908.bb4ff02a.freebsd@edvax.de> In-Reply-To: <20130806193908.bb4ff02a.freebsd@edvax.de> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.126] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-08-05_07:2013-08-05,2013-08-05,1970-01-01 signatures=0 Cc: markham breitbach , Devin Teske , questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 17:46:02 -0000 On Aug 6, 2013, at 10:39 AM, Polytropon wrote: > On Tue, 6 Aug 2013 16:50:37 +0000, Teske, Devin wrote: >> And yes... to clarify... the port is a mirror of what's in 9.x base. >> (however, see my recent notes in a separate reply; TL;DR: port is >> 9.x only; proceed only if you know you don't care about the dialog(1) >> aspects of the library code). >=20 > I think it should be relatively unproblematic to fetch the > port and only use the subroutines "as is", even if it's just > for educational purposes. :-) >=20 Right. Just a warning though, what is "fetched" in ports is actually in the format= of what's in HEAD (read: not in the format of what gets installed). For example, there are things that end up in /usr/share/bsdconfig that aren= 't in the "bsdconfig/share/" source directory (e.g., all the stuff under /u= sr/share/bsdconfig/networking is under the source directory "bsdconfig/netw= orking/share"). This may be counter-intuitive from an "exploratory" view if= looking at the source directory (what's fetched by ports). And since the port Makefile will prevent you from turning that fetch'ed sou= rce directory into an installed software (putting things where they end up)= , it might be easier to grab this pre-built package that I stashed... http://druidbsd.sf.net/download/bsdconfig/bsdconfig-0.9.0.tbz Because then you can say "pkg_add" and everything will be in the right plac= e (/usr/share/bsdconfig/ will be flush with everything and you won't have t= o hunt-and-peck through the source with a "maintainers" view). --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.