Re: [B.A.T.M.A.N.] Changing vis output ready for mainline...

[Andrew Lunn <andrew@lunn.ch>]

> So, the question is whether we want to make batctl the almighty tool that we 
> always depend on or are we trying to find alternative solutions to avoid that 
> dependency ?
> 
> One option for the case at hand might be debugfs 
> (http://lwn.net/Articles/115282/). It is another filesystem which needs to be 
> mounted seperately - there we can output whatever we want (unlike /proc). It 
> would be possible to create virtual files for the dot draw / json / raw output 
> (raw means the neutral format suggested by Andrew).

I personally don't like the idea of using debugfs for VIS. I would not
call the mesh topology debug information for kernel hackers, which is
the purpose of debugfs.

However i do see a compromise. 

1) Make /proc/net/batman-adv/vis the neutral format i suggested, or
something similar. Extend batctl to use this and apply formatting as
wanted.

2) Add a kernel module internal interface which allows other kernel
modules to get access to the raw VIS data. Write a batman-graphviz and
a batman-json kernel module which outputs the VIS data in formatted
text to debugfs.

If you don't want userspace dependencies, and you know your kernel
supports the optional debugfs, you can use the kernel modules. If not,
batctl will always work, it just requires you have a version which
understands the current proc format.

       Andrew