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.org
Cc: Grant <grant@mrit.co.za>
Subject: Re: [B.A.T.M.A.N.] Libelf
Date: Wed, 25 Jan 2012 18:59:59 +0800	[thread overview]
Message-ID: <201201251900.00268.lindner_marek@yahoo.de> (raw)
In-Reply-To: <008101ccdb4a$96aaf1b0$c400d510$@co.za>


Hi,

> Thanks for responding. I was under the impression I did reply to the list,
> but no stress, I will do it in future.

ok, thanks!


> I have worked through the guide. It took me a while to figure out what
> needed to be done exactly. The initial attempt to download straight to a
> openwrt install gave me the libelf error. I then follow through the guide
> and eventually worked on my own build. But, it still did not work.
> 
> The documentation I think make some assumption that you are a highly
> experienced wireless person using openwrt in everyday. I doesn't seem to
> cater for someone coming to it for the first time.
> 
> I am looking at solutions as your is quiet dynamic which is why I like it.
> It does not exactly state how a gateway would work, a cpe or similar and
> how exactly to get wifi working on a solution. So, maybe a bit more "for
> dummies" stuff would be great.

Well, our website is about batmand/batman-adv. If you require documentation 
about OpenWrt go to their website and for wifi check the linux wifi docs.
We have to assume that certain knowlwedge is given otherwise we end up writing 
documentation about everything. Where does it end ? How to cross-compile / how 
does my kernel work / how does the IP protocol work / etc.

A document on "how to build $your_solution on top of batman" also is difficult 
to make. There are so many possible ways of doing things ..

Feel free to make suggestions on "how to get it working easier". We put a lot 
of effort into making things easy but we are willing to do more if you have a 
good idea.

Regards,
Marek

      reply	other threads:[~2012-01-25 10:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <009f01ccda89$f0502260$d0f06720$@co.za>
2012-01-24 16:49 ` [B.A.T.M.A.N.] Libelf Marek Lindner
2012-01-24 23:46   ` elektra
     [not found]   ` <565583648-1327431441-cardhu_decombobulator_blackberry.rim.net-851327728-@b4.c14.bise7.blackberry>
2012-01-25 10:08     ` Marek Lindner
2012-01-25 10:17       ` Grant
2012-01-25 10:59         ` Marek Lindner [this message]

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=201201251900.00268.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=grant@mrit.co.za \
    /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