public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@lists.open-mesh.net
Subject: [B.A.T.M.A.N.] batman's new configuration interface
Date: Mon, 30 Nov 2009 07:36:51 +0800	[thread overview]
Message-ID: <200911300736.51646.lindner_marek@yahoo.de> (raw)


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


                 reply	other threads:[~2009-11-29 23:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200911300736.51646.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox