public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
* [B.A.T.M.A.N.] batman's new configuration interface
@ 2009-11-29 23:36 Marek Lindner
  0 siblings, 0 replies; only message in thread
From: Marek Lindner @ 2009-11-29 23:36 UTC (permalink / raw)
  To: b.a.t.m.a.n


Hey folks,

I have given the new interface (designed in Brussels - specs are at the bottom 
of this page: http://www.open-mesh.net/wiki/2009-10-23-batman-goes-mainline) a 
little bit of thought. The main idea is to have batman list all available 
interfaces inside of /proc/sys/net/batman-adv/interfaces to let the user 
enable/disable/configure each interface individually via sysctl or batctl.

Back then we decided to create a "mesh" folder that should contain all 
relevant meshing data such as the originator table, translation tables, vis 
data, etc. We did not consider that the sysctl interface is not made for such 
data. It easily allows to set small variables but other (read-only) 
information should be placed elsewhere.

Now, we have to rethink the location. The creator of the new interface (Linus) 
suggested to create 2 folders inside of /proc: The first folder should be part 
of sysctl and contain all files that are writeable. The other should be 
/proc/net/batman-adv and contains all read-only information.
Alternatively, we could keep everything in one folder but outside of the 
sysctl interface.

Other ideas ? Opinions ?

Regards,
Marek


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2009-11-29 23:36 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-11-29 23:36 [B.A.T.M.A.N.] batman's new configuration interface Marek Lindner

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox