Yes, it is. I'll provide a package with a bunch of related changes from Quantal; namely:
- using dbus instead of a config file;
- using a different dbus name than the default for dnsmasq;
- restarting dnsmasq less often (fixed in using dbus, basically)
- avoid refreshing interface config on every route cache entry notification;
etc.
dnsmasq will still need to be updated to ship the dbus file in dnsmasq-base isntead of dnsmasq, and the biggest, most time-consuming issue is that the dbus name changing patch needs to be adapted to apply to Precise's dnsmasq.
Yes, it is. I'll provide a package with a bunch of related changes from Quantal; namely:
- using dbus instead of a config file;
- using a different dbus name than the default for dnsmasq;
- restarting dnsmasq less often (fixed in using dbus, basically)
- avoid refreshing interface config on every route cache entry notification;
etc.
dnsmasq will still need to be updated to ship the dbus file in dnsmasq-base isntead of dnsmasq, and the biggest, most time-consuming issue is that the dbus name changing patch needs to be adapted to apply to Precise's dnsmasq.