Date: Sun, 01 Mar 2015 11:26:01 -0500 From: Allan Jude <allanjude@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: Massive libxo-zation that breaks everything Message-ID: <54F33D99.2060102@freebsd.org> In-Reply-To: <54F31510.7050607@hot.ee> References: <54F31510.7050607@hot.ee>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] 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. -- Allan Jude [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJU8z2cAAoJEJrBFpNRJZKfuOcQAJ1IoB9K9juB+0MRW0c7A7v8 O1gM+IKyzTHuCagmUABH3LE3fR2VFhg+ZSsjdMj8AcstWCgfOk/KpcGXV0o1edJz U0T+e72D2rwfLpSxLbqF41f+fwDNOUMaGl2FUF11GlXs1EuKsAl99OWbobb8X0FG WvObM47TclFJS+CrA+1+FsQIm8YROVq8H1TAb2Qi1Ob6Vv/vWg1FQqWcsMQ5A5GG 7fBYJhomjC6uHfWoGA78yAwAPvdPyZKFnVCMRIQILN+8pVDPxXr1kreVlDwOjvPh 2B2RfrCBaWkbg4z2G2fCBOSi6UvThlIYoELwW3xFtutxWLE/KWv1kc5YtMdhr5sc y6VN6YL7M5cGW1BRPjwTBmtARz74uNfrUAqBME6BEklbcd4YQ3qyZst7aLzf4MfU ewbNfVgKOuC3EQfiLipUAojoxjrkJWtlDqfNyC+W5irZqp372T8UDyoB9PHrsUbj edpMUESPo/0N4ZRd3QXJ0t26wrlzeoy0exHPrygx+9Lk8BbKf9hU7Q5HmlZbdPhC mc+L2b23GyzOWWJYN9FwlqgUwYWQi5GdKHDX+et+Ibw7DVzywG77wmlS8WknKcNI fSTKk8ApIPEuPSW0RFSJ1Ea2atEjjjyMYan9mU55zA8iV+Jr3+qNcgoGkNVRntNB n5itg1rqTOLQJtbS2yVm =dZHx -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54F33D99.2060102>