Re: Massive libxo-zation that breaks everything

On 3/1/15 4:57 PM, Harrison Grundy wrote: I like the idea behind this... where I'm running into difficulty is why these bits of functionality need to be combined. What someone does with ifconfig on the command line, versus what someone wants to know about their network interfaces in an XML dump

Re: Massive libxo-zation that breaks everything

On 3/1/15 4:29 PM, Rui Paulo wrote: On Mar 1, 2015, at 11:11, David Chisnall wrote: How would it be in a port? It involves modifying core utilities (some of which, like ifconfig, rely on kernel APIs that change between releases) to emit structured output. Maintaining two copies of each ut

Re: Massive libxo-zation that breaks everything

How about we allow JSON input on those utils too... Then we get into full-blown hell faster. Hmm... I would like to talk with system using JSON. JSON would be in utils that are or at least function similarly to rm, mv, ls, find, mount, zpool, zfs, geom, mdconfig, tar, df, netstat, ifconfig... (or

Re: sa(4) driver changes available for test

On Sun, Mar 01, 2015 at 19:41:07 -0500, Dan Langille wrote: > > > On Mar 1, 2015, at 7:31 PM, Kenneth D. Merry wrote: > > > > On Sun, Mar 01, 2015 at 19:15:05 -0500, Dan Langille wrote: > >> > >>> On Feb 17, 2015, at 1:36 PM, Kenneth D. Merry wrote: > >>> > >>> On Sat, Feb 14, 2015 at 18:22:4

Re: sa(4) driver changes available for test

On Sun, Mar 01, 2015 at 19:40:40 -0500, Dan Langille wrote: > > > On Mar 1, 2015, at 7:36 PM, Kenneth D. Merry wrote: > > > > On Sun, Mar 01, 2015 at 19:28:37 -0500, Dan Langille wrote: > >> > >>> On Mar 1, 2015, at 7:18 PM, Kenneth D. Merry wrote: > >>> > >>> On Sun, Mar 01, 2015 at 17:06:24

Re: Massive libxo-zation that breaks everything

On 2015-03-01 19:20, Arseny Nasokin wrote: > On 1 March 2015 at 22:10, Allan Jude wrote: > >> On 2015-03-01 13:49, Harrison Grundy wrote: >>> Thanks! >>> >>> That does seem useful, but I'm not sure I see the reasoning behind >>> putting into base, over a port or package, since processing XML in b

Re: sa(4) driver changes available for test

> On Mar 1, 2015, at 7:31 PM, Kenneth D. Merry wrote: > > On Sun, Mar 01, 2015 at 19:15:05 -0500, Dan Langille wrote: >> >>> On Feb 17, 2015, at 1:36 PM, Kenneth D. Merry wrote: >>> >>> On Sat, Feb 14, 2015 at 18:22:43 -0500, Dan Langille wrote: > On Feb 13, 2015, at 7:32 PM, Kennet

Re: sa(4) driver changes available for test

> On Mar 1, 2015, at 7:36 PM, Kenneth D. Merry wrote: > > On Sun, Mar 01, 2015 at 19:28:37 -0500, Dan Langille wrote: >> >>> On Mar 1, 2015, at 7:18 PM, Kenneth D. Merry wrote: >>> >>> On Sun, Mar 01, 2015 at 17:06:24 -0500, Dan Langille wrote: > On Feb 13, 2015, at 7:32 PM, Kenneth

Re: sa(4) driver changes available for test

On Sun, Mar 01, 2015 at 19:28:37 -0500, Dan Langille wrote: > > > On Mar 1, 2015, at 7:18 PM, Kenneth D. Merry wrote: > > > > On Sun, Mar 01, 2015 at 17:06:24 -0500, Dan Langille wrote: > >> > >>> On Feb 13, 2015, at 7:32 PM, Kenneth D. Merry wrote: > >>> > >>> > >>> I have a fairly large se

Re: sa(4) driver changes available for test

On Sun, Mar 01, 2015 at 19:15:05 -0500, Dan Langille wrote: > > > On Feb 17, 2015, at 1:36 PM, Kenneth D. Merry wrote: > > > > On Sat, Feb 14, 2015 at 18:22:43 -0500, Dan Langille wrote: > >> > >>> On Feb 13, 2015, at 7:32 PM, Kenneth D. Merry wrote: > >>> > >>> > >>> I have a fairly large s

Re: sa(4) driver changes available for test

> On Mar 1, 2015, at 7:18 PM, Kenneth D. Merry wrote: > > On Sun, Mar 01, 2015 at 17:06:24 -0500, Dan Langille wrote: >> >>> On Feb 13, 2015, at 7:32 PM, Kenneth D. Merry wrote: >>> >>> >>> I have a fairly large set of changes to the sa(4) driver and mt(1) driver >>> that I'm planning to com

Re: Massive libxo-zation that breaks everything

On 1 March 2015 at 22:10, Allan Jude wrote: > On 2015-03-01 13:49, Harrison Grundy wrote: > > Thanks! > > > > That does seem useful, but I'm not sure I see the reasoning behind > > putting into base, over a port or package, since processing XML in base > > is a pain, and it can't serve up JSON or

Re: sa(4) driver changes available for test

On Sun, Mar 01, 2015 at 17:06:24 -0500, Dan Langille wrote: > > > On Feb 13, 2015, at 7:32 PM, Kenneth D. Merry wrote: > > > > > > I have a fairly large set of changes to the sa(4) driver and mt(1) driver > > that I'm planning to commit in the near future. > > > > A description of the changes

Re: sa(4) driver changes available for test

> On Feb 17, 2015, at 1:36 PM, Kenneth D. Merry wrote: > > On Sat, Feb 14, 2015 at 18:22:43 -0500, Dan Langille wrote: >> >>> On Feb 13, 2015, at 7:32 PM, Kenneth D. Merry wrote: >>> >>> >>> I have a fairly large set of changes to the sa(4) driver and mt(1) driver >>> that I'm planning to co

Re: Massive libxo-zation that breaks everything

On 03/01/15 13:25, Craig Rodrigues wrote: > On Sun, Mar 1, 2015 at 10:49 AM, Harrison Grundy < > harrison.gru...@astrodoggroup.com> wrote: > >> Thanks! >> >> That does seem useful, but I'm not sure I see the reasoning behind >> putting into base, over a port or package >> > > >> , since proces

Re: Massive libxo-zation that breaks everything

On Mar 1, 2015, at 11:11, David Chisnall wrote: > How would it be in a port? It involves modifying core utilities (some of > which, like ifconfig, rely on kernel APIs that change between releases) to > emit structured output. Maintaining two copies of each utility, one in the > base system wi

Re: sa(4) driver changes available for test

> On Feb 13, 2015, at 7:32 PM, Kenneth D. Merry wrote: > > > I have a fairly large set of changes to the sa(4) driver and mt(1) driver > that I'm planning to commit in the near future. > > A description of the changes is here and below in this message. > > If you have tape hardware and the in

Re: Massive libxo-zation that breaks everything

On Sun, Mar 1, 2015 at 10:49 AM, Harrison Grundy < harrison.gru...@astrodoggroup.com> wrote: > Thanks! > > That does seem useful, but I'm not sure I see the reasoning behind > putting into base, over a port or package > > , since processing XML in base is a pain, and it can't serve up JSON or >

Re: Massive libxo-zation that breaks everything

On Mar 1, 2015, at 5: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

Re: Massive libxo-zation that breaks everything

On 03/01/15 11:11, David Chisnall wrote: > On 1 Mar 2015, at 18:49, Harrison Grundy > wrote: >> >> That does seem useful, but I'm not sure I see the reasoning >> behind putting into base, over a port or package, since >> processing XML in base is a pain, and it can't serve up JSON or >> HTML with

Re: sa(4) driver changes available for test

> On Feb 28, 2015, at 6:42 PM, Dan Langille wrote: > >> On Feb 28, 2015, at 6:15 PM, Kenneth D. Merry wrote: >> >>> On Sat, Feb 28, 2015 at 17:29:48 -0500, Dan Langille wrote: >>> On Feb 18, 2015, at 7:13 PM, Kenneth D. Merry wrote: I have updated the patches. >>>

Re: Massive libxo-zation that breaks everything

On 1 Mar 2015, at 18:49, Harrison Grundy wrote: > > That does seem useful, but I'm not sure I see the reasoning behind > putting into base, over a port or package, since processing XML in base > is a pain, and it can't serve up JSON or HTML without additional > utilities anyway. How would it be

Re: Massive libxo-zation that breaks everything

On 2015-03-01 13:49, Harrison Grundy wrote: > Thanks! > > That does seem useful, but I'm not sure I see the reasoning behind > putting into base, over a port or package, since processing XML in base > is a pain, and it can't serve up JSON or HTML without additional > utilities anyway. > > (If I'm

Re: Massive libxo-zation that breaks everything

Thanks! That does seem useful, but I'm not sure I see the reasoning behind putting into base, over a port or package, since processing XML in base is a pain, and it can't serve up JSON or HTML without additional utilities anyway. (If I'm reviving a long-settled thing, let me know and I'll drop it

Re: Massive libxo-zation that breaks everything

On Sun, Mar 1, 2015 at 9:25 AM, Harrison Grundy < harrison.gru...@astrodoggroup.com> wrote: > > > If someone could summarize what this is, I'd greatly appreciate it. > https://lists.freebsd.org/pipermail/freebsd-arch/2014-July/015633.html ___ freebsd-cu

Re: Massive libxo-zation that breaks everything

On Mar 1, 2015, at 09:25, Harrison Grundy wrote: > 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 package

Re: Massive libxo-zation that breaks everything

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 contin

Re: Massive libxo-zation that breaks everything

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/mai

Re: Massive libxo-zation that breaks everything

On Sun, Mar 01, 2015 at 11:26:01AM -0500, Allan Jude wrote: > On 2015-03-01 08:33, Sulev-Madis Silber (ketas) wrote: > > 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. > Give

Re: Massive libxo-zation that breaks everything

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 contin

Massive libxo-zation that breaks everything

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/li

Jenkins build is back to normal : FreeBSD_HEAD #2474

See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: PCI SR-IOV infrastructure has been committed to head

Awesome news my friend. I got distracted with some fire drills this week, but I'll make it a priority to get the ixl changes committed next week. Thanks to you and everyone involved for getting this done. Jack On Sat, Feb 28, 2015 at 6:01 PM, Ryan Stone wrote: > I've just finished committing