From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] ifupdown-0.8.2 / dhcp-4.1-ESV-R12 incompatibility
Date: Sat, 9 Jan 2016 10:09:34 -0300 [thread overview]
Message-ID: <5691068E.4090003@zacarias.com.ar> (raw)
In-Reply-To: <CA+sos78-UX4YD5WeO3qr4ahn+5iN33hX2pr2koiT9JtekdA8uA@mail.gmail.com>
On 09/01/16 09:56, Beno?t Th?baudeau wrote:
> A few months ago, 4.1-ESV-R12 had an EoL date set to Dec. 2015 on
> https://www.isc.org/downloads/, but now it is TBA. It probably means
> that they did not have a chance to finalize the deprecation of 4.1 in
> Dec. 2015, and that they are rescheduling it, but that it will come
> soon. Also, several distributions like Ubuntu have already switched to
> 4.3.x, and this version seems to fix the ifupdown 0.8.2 issue
> according to what has been previously said in this thread. Regarding
> the build, Gustavo has said above that it is broken with a bind
> external to the dhcp package, but it should hopefully work fine with
> the built-in bind.
>
> All in all, we should probably bump the version to 4.3.3 rather than
> killing this package.
>
> Best regards,
> Beno?t
Hi all.
I agree, for a full-blown server there's not much alternative (there's
dnsmasq for a small one, but it's not nearly as featured).
The bundled bind build is broken as well, since it doesn't pass any
toolchain variables it tries to build with the distro gcc and so on,
resulting in mixed architecture files.
The bundled version might be outdated with respect to bug/security fixes
in bind as well, though it's not that likely since it uses just a small
subset of functionality.
IMO the best solution would be to fix the makefiles/build and submit
upstream, they were responsive the 1-2 times i submitted patches to fix
things so it's probably the best bet.
Regards.
prev parent reply other threads:[~2016-01-09 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 14:26 [Buildroot] ifupdown-0.8.2 / dhcp-4.1-ESV-R12 incompatibility rdkehn at yahoo.com
2016-01-07 19:11 ` Gustavo Zacarias
2016-01-07 20:30 ` Benoît Thébaudeau
2016-01-07 20:35 ` Gustavo Zacarias
2016-01-09 0:18 ` Arnout Vandecappelle
2016-01-09 12:56 ` Benoît Thébaudeau
2016-01-09 13:09 ` Gustavo Zacarias [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=5691068E.4090003@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.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