Non yum upgrade to bind removes as service

[frinklabs]

My CENTOS 5.8 DNS servers can only be updated to BIND 9.3.6 through yum

I need 9.9.4 to get the RRL functionality.

I can download and make the sources and named runs if I start it from the command line

The package did not install any of the INIT scripts and the service named does not work any more

Is there a way to create these scripts? Did I miss a step in the compile? Is it easier to leave the old BIND setup then simply replace the executable with the new version?

[TrevorH]

Leaving the old package installed and source installing over the top of it is a sure way to break things, maybe not right now but as soon as yum tries to update the original it will overwrite half your source install since it knows nothing about it. Not the right solution.

You might try exploding the current package with rpm2cpio and extracting the initscript from it and installing that manually but I wouldn't guarantee that it's compatible with your source install. I'm also not sure what will happen with all the other bind-* packages that are installed and required by other packages in the system - e.g. bind-libs.

Really the correct* solution to this is to grab the SRPM for the current bind, or perhaps one from a more recent Fedora from prior to the switchover to systemd (which is a new initscript system that's incompatible with the one in use on el5). Grab the SRPM and install that and hack the spec file about to build your own bind RPMs.

http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment
http://wiki.centos.org/HowTos/RebuildSRPM

* correct as in 'least bad'

[frinklabs]

What if there is no RPM?

I compiled from source downloaded from here: https://www.isc.org/downloads/

There's no os-specific RPM listed here: http://rpmfind.net/linux/rpm2html/search.php?query=bind

[TrevorH]

I mean grab the current CentOS SRPM and rebuild that. Once you can rebuild that without modification, change the version numbers in the spec file, download and insert your required tarball inside it, rebuild it again with the version you want to actually use. Might be easier to use a Fedora SRPM to do the rebuild but the startup scripts have all changed from upstart to systemd in the latest Fedora versions so any startup script that they supply will probably not work on CentOS.

[frinklabs]

That sounds like fun but it isn't, for me, the path of least resistance

I can wait until there's a release of CentOS that includes the required BIND revision in its yum updates.

Meanwhile, does this mean that there's no chewing-gum-and-rolling-papers way around this? Like, there's no equivalent to the windows run-as-service functionality?

Besides the security issues, are there problems with using auto-login and a user script?

[WhatsHisName]

Well, Linux isn't Windows.

The simplest fix for you is to spin up a small Fedora guest and to use it for late bind releases.

Fedora 20 is sceduled for release on December 10 (6 days from now).

[frinklabs]

Well, Linux isn't Windows.

Thank the FSM's Noodly Appendages for that.

Meanwhile, I added the executable to the inittab file and it boots up ok

Is there any reason not to go this way?