From owner-freebsd-current@FreeBSD.ORG Sun Mar 1 17:27:35 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E341922E for ; Sun, 1 Mar 2015 17:27:35 +0000 (UTC) Received: from mailout.easymail.ca (mailout.easymail.ca [64.68.201.169]) (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 986D3B3E for ; Sun, 1 Mar 2015 17:27:35 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 677E5E414 for ; Sun, 1 Mar 2015 12:27:34 -0500 (EST) X-Virus-Scanned: Debian amavisd-new at mailout.easymail.ca X-Spam-Flag: NO X-Spam-Score: -3.853 X-Spam-Level: X-Spam-Status: No, score=-3.853 required=5 tests=[ALL_TRUSTED=-1.8, AWL=-0.146, BAYES_00=-2.599, DNS_FROM_AHBL_RHSBL=0.692] Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (easymail-mailout.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ysd7DNmsjAN for ; Sun, 1 Mar 2015 12:27:34 -0500 (EST) Received: from bsddt1241.lv01.astrodoggroup.com (unknown [40.141.24.126]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 3D8E1E3AB for ; Sun, 1 Mar 2015 12:27:32 -0500 (EST) Message-ID: <54F34B6E.2040809@astrodoggroup.com> Date: Sun, 01 Mar 2015 09:25:02 -0800 From: Harrison Grundy User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Massive libxo-zation that breaks everything References: <54F31510.7050607@hot.ee> In-Reply-To: <54F31510.7050607@hot.ee> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 01 Mar 2015 17:52:22 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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: Sun, 01 Mar 2015 17:27:36 -0000 On 03/01/15 05:33, Sulev-Madis Silber (ketas) wrote: > Hello. > > First, I would be happy to have JSON and XML output about > filesystems, users, routes... but I don't like how it makes code of > df, w, netstat hard to read/maintain and often broken. > > I don't think it would be good to continue with this. Maybe the > effort should be put to creating new layer/library and then > something on top of it that actually outputs JSON and XML. > > Or, if that's too difficult... maybe just regular df/w/netstat > could be copied to somewhere else and made code libxo-output-only. > And original df/w/netstat changes reverted and left alone. > > Then, maybe later, df/w/netstat/... could be updated to this new > layer/library. Or maybe this should be just left as it is. > > That would mean having two netstat's in system, which could be both > good (separation) and bad (maintaining). > > Just some ideas... I don't know how to solve this issue fully. I'm > also not likely the one who would write code for all this. Hell, > those aren't even all my ideas here. I just worry that system > drop-in xo-zation is bad for overall health of base. > > Oh and, it makes rescue larger and more complex, too? On that, > there was suggestion to maybe create separate "first aid kit" and > "emergency room" types of system rescue utils/methods. > > > Thanks. _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current To > unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" > Forgive my ignorance about exactly what this is, and possibly reviving a long-settled debate, but this sounds like something that would be a great deal more useful as a port/package, rather than in base. Due to the lack of XML parsing code in -base, the difficulty in maintaining yet another interface, and the overhead involved in doing it, I don't quite see where one would really want XML output *and* be entirely opposed to ports or packages. If someone could summarize what this is, I'd greatly appreciate it. --- Harrison