From: Jo-Philipp Wich <jow@openwrt.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] How to create a Firmware o Image with a specific batman-adv configuration
Date: Fri, 12 Oct 2012 12:04:30 +0200 [thread overview]
Message-ID: <5077EB2E.1040906@openwrt.org> (raw)
In-Reply-To: <50776C62.4040406@nixbits.net>
Hey.
> That is very much all about openwrt and the wiki provides all the
> information. When you build the image just ad your configuration
> files to "backfire/package/base-files/files/etc/config/
Don't do that. Not all targets use the base-files configs and its a
nuissance to have local changes while trying to stay in sync with the repo.
The proper wqay to overlay the build with custom configs is to create a
toplevel files/ directory and put the configs there, e.g.
files/etc/rc.local
files/etc/config/network
and so on. Toplevel here means the directory where you run make in.
Regards,
Jow
prev parent reply other threads:[~2012-10-12 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 0:00 [B.A.T.M.A.N.] How to create a Firmware o Image with a specific batman-adv configuration Esteban Municio
2012-10-12 1:03 ` HeXiLeD
2012-10-12 10:04 ` Jo-Philipp Wich [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=5077EB2E.1040906@openwrt.org \
--to=jow@openwrt.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/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