From owner-freebsd-current@FreeBSD.ORG Sun Mar 1 16:54:51 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7D45F8C1 for ; Sun, 1 Mar 2015 16:54:51 +0000 (UTC) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id B6E327F7 for ; Sun, 1 Mar 2015 16:54:49 +0000 (UTC) Received: (qmail 56407 invoked by uid 89); 1 Mar 2015 16:54:41 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@88.217.180.225) by mail.grem.de with ESMTPA; 1 Mar 2015 16:54:41 -0000 Date: Sun, 1 Mar 2015 17:54:36 +0100 From: Michael Gmelin To: Allan Jude Subject: Re: Massive libxo-zation that breaks everything Message-ID: <20150301175436.2da04674@bsd64.grem.de> In-Reply-To: <54F33D99.2060102@freebsd.org> References: <54F31510.7050607@hot.ee> <54F33D99.2060102@freebsd.org> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; amd64-portbld-freebsd10.0) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org 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 16:54:51 -0000 On Sun, 01 Mar 2015 11:26:01 -0500 Allan Jude wrote: > On 2015-03-01 08: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" > > > > Is there a specific bug you are running in to? So far the only bugs > I've seen with the xo-ification have been ones where the JSON output > was not always well formed. > There was one where uptime(1) wouldn't emit any output when called in a pipeline (missing call to xo_finish, that wouldn't affect the output on a tty due to implicit flush on newline). -- Michael Gmelin