Re: Bug#595081: ITP: openresolv -- management framework for resolv.conf
On Tue, Aug 31, 2010 at 10:48:47PM +0100, Roy Marples wrote: Package: wnpp Severity: wishlist Owner: Roy Marples r...@marples.name * Package name: openresolv Version : 3.3.5 Upstream Author : Roy Marples r...@marples.name * URL : http://roy.marples.name/projects/openresolv * License : BSD-2 Programming Lang: Shell Description : management framework for resolv.conf Allows multiple daemons to manage resolv.conf and configures local resolvers such as dnsmasq and unbound. We already have one of these called resolvconf, and it has plenty of bugs without adding a *second* framework for managing resolv.conf. Please coordinate with the resolvconf maintainer and, preferably, merge your efforts with the existing package. (In fact, I think that should be a blocker and that the ftp team should reject any upload of a separate openresolv package.) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Re: Bug#595081: ITP: openresolv -- management framework for resolv.conf
On Tue, 31 Aug 2010, Roy Marples wrote: Description : management framework for resolv.conf Allows multiple daemons to manage resolv.conf and configures local resolvers such as dnsmasq and unbound. How does this differ from resolvconf which already has significant buy-in and integration in Debian? Don Armstrong -- You could say to the Universe this is not /fair/. And the Universe would say: Oh it isn't? Sorry. -- Terry Pratchett _Soul Music_ p357 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100831222004.gy22...@rzlab.ucr.edu
Re: Bug#595081: ITP: openresolv -- management framework for resolv.conf
On Tue, 2010-08-31 at 15:17 -0700, Steve Langasek wrote: We already have one of these called resolvconf, and it has plenty of bugs without adding a *second* framework for managing resolv.conf. Please coordinate with the resolvconf maintainer and, preferably, merge your efforts with the existing package. I tried many few years ago, but my patches were rejected (I forget why, don't have the emails anymore), so I created my own variant from scratch keeping a compatible commandline interface. #477723 - author is trying to pass resolvconf off to a new maintainer for over 2 years The other resolvconf bugs do not affect openresolv, and openresolv also solves many of them. (In fact, I think that should be a blocker and that the ftp team should reject any upload of a separate openresolv package.) I find that a very narrow minded view. Thanks Roy -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1283293804.1706.10.ca...@uberpc
Re: Bug#595081: ITP: openresolv -- management framework for resolv.conf
On Tue, 2010-08-31 at 15:20 -0700, Don Armstrong wrote: On Tue, 31 Aug 2010, Roy Marples wrote: Description : management framework for resolv.conf Allows multiple daemons to manage resolv.conf and configures local resolvers such as dnsmasq and unbound. How does this differ from resolvconf which already has significant buy-in and integration in Debian? Taken from http://roy.marples.name/projects/openresolv/wiki/OpenResolvReasons * Works with POSIX shell and userland * Does not need awk, grep or sed which means we can work without /usr mounted * Works with other init systems than Debians' out of the box * Available as a 2 clause BSD license * Prefer configs via IF_METRIC for dynamic ordering * Configures zones for local resolvers other than libc The last point is quite important, especially when running VPN systems. Take the following resolv.conf files which have been generated by a DHCP client and sent to resolvconf: # resolv.conf from bge0 search foo.com nameserver 1.2.3.4 # resolv.conf from tap0 domain bar.org nameserver 5.6.7.8 In this instance, queries for foo.com will go to 1.2.3.4 and queries for bar.org will go to 5.6.7.8. This does require the resolvers to be configured to pickup the resolvconf generated configuration for them though. openresolv ships with helpers for dnsmasq, ISC BIND,PowerDNS Recursor and unbound Other than that, the openresolv is command line compatible with resolvconf. However, the setup is not. Instead of many directories and files to manage, openresolv just uses /etc/resolvconf.conf. Aside from the user specific configuration, openresolv integrates 100% with a Debian based system. Thanks Roy -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1283294701.1706.25.ca...@uberpc
Re: Bug#595081: ITP: openresolv -- management framework for resolv.conf
On Tue, 2010-08-31 at 15:20 -0700, Don Armstrong wrote: On Tue, 31 Aug 2010, Roy Marples wrote: Description : management framework for resolv.conf Allows multiple daemons to manage resolv.conf and configures local resolvers such as dnsmasq and unbound. How does this differ from resolvconf which already has significant buy-in and integration in Debian? * Works with POSIX shell and userland * Does not need awk, grep or sed which means we can work without /usr mounted * Works with other init systems than Debians' out of the box * Available as a 2 clause BSD license * Prefer configs via IF_METRIC for dynamic ordering * Configures zones for local resolvers other than libc The last point is quite important, especially when running VPN systems. Take the following resolv.conf files which have been generated by a DHCP client and sent to resolvconf: # resolv.conf from bge0 search foo.com nameserver 1.2.3.4 # resolv.conf from tap0 domain bar.org nameserver 5.6.7.8 In this instance, queries for foo.com will go to 1.2.3.4 and queries for bar.org will go to 5.6.7.8. This does require the resolvers to be configured to pickup the resolvconf generated configuration for them though. openresolv ships with helpers for dnsmasq, ISC BIND,PowerDNS Recursor and unbound Other than that, the openresolv is command line compatible with resolvconf. However, the setup is not. Instead of many directories and files to manage, openresolv just uses /etc/resolvconf.conf. Aside from the user specific configuration, openresolv integrates 100% with a Debian based system. Thanks Roy -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1283294919.1706.28.ca...@uberpc
