From: "A. James Lewis" <james@fsck.co.uk>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: [B.A.T.M.A.N.] Packaging BATMAN
Date: Fri, 21 Sep 2018 16:51:53 +0000 [thread overview]
Message-ID: <44c621ef89e6d369e6c2e7f438123243@mail.fsck.co.uk> (raw)
In-Reply-To: <20180919123238.23742-6-sw@simonwunderlich.de>
Hi all,
I'd like to package an application for RHEL7 which uses BATMAN, but it seems that the module is not distributed by Redhat with their kernel.
Am I going to be stuck with releasing a new package with an updated batman-adv kernel module for every minor update of the OS, or is there a simpler way?...
Any advice/suggestions would be appreciated.
--
A. James Lewis (james@fsck.co.uk)
"Engineering does not require science. Science helps a lot but people
built perfectly good brick walls long before they knew why cement works."
prev parent reply other threads:[~2018-09-21 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 12:32 [B.A.T.M.A.N.] [PATCH 0/5] pull request for net-next: batman-adv 2018-09-19 Simon Wunderlich
2018-09-19 12:32 ` [B.A.T.M.A.N.] [PATCH 1/5] batman-adv: Start new development cycle Simon Wunderlich
2018-09-19 12:32 ` [B.A.T.M.A.N.] [PATCH 2/5] batman-adv: Mark debugfs functionality as deprecated Simon Wunderlich
2018-09-19 12:32 ` [B.A.T.M.A.N.] [PATCH 3/5] batman-adv: Provide debug messages as trace events Simon Wunderlich
2018-09-19 12:32 ` [B.A.T.M.A.N.] [PATCH 4/5] batman-adv: Move OGM rebroadcast stats to orig_ifinfo Simon Wunderlich
2018-09-19 12:32 ` [B.A.T.M.A.N.] [PATCH 5/5] batman-adv: Enable LockLess TX for softif Simon Wunderlich
2018-09-19 16:47 ` [B.A.T.M.A.N.] a dumb question about batman Dave Taht
2018-09-20 6:37 ` Sven Eckelmann
2018-09-20 3:36 ` [B.A.T.M.A.N.] [PATCH 0/5] pull request for net-next: batman-adv 2018-09-19 David Miller
2018-09-21 16:51 ` A. James Lewis [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=44c621ef89e6d369e6c2e7f438123243@mail.fsck.co.uk \
--to=james@fsck.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).