Re: Bug#517790: ITP: mydns -- DNS server using MySQL or PostgreSQL for data storage
First, I'm a perl programmer so TMTOWTDI is pretty ingrained into my culture. I use mydns -- yi.org is based off of it, and I also use it as an easy way to set up dynamic virtual hosts for automated builds on another project, in conjunction with libapache2-mod-macro and mod_proxy on the frontend, and m4 to dynamically rewrite the port numbers of daemons in cdebootstrap-based chroot environments on the backend (the way this project is set up, whenever there is a new checkin into a subversion branch, we end up with a pristine debian environment running the software...) All these technologies are "redundant" -- why do we still have both "debootstrap" and "cdebootstrap" anyway? -- why do we still have squid if there's a mod_proxy? Why do we have libapache2-mod-macro if mod_perl or m4 can do all of that? Why do we even have PowerDNS *or* MyDNS now that BIND-DLZ is part of the mainline? Personally, I'm abandoning MyDNS in the mid-term as well, but if somebody wants to keep packaging it up for debian, please don't discourage them. Thanks, Tyler Russell Coker wrote: > Having different programs to perform a task will decrease the portion of the > user-base that runs a given program and if a bug is found it will give some > degree of herd immunity. But the down-side is that more programs means more > potential security flaws and spreading the time of people who want to fix > security problems (including the security team) across more targets. > > The range of software that is available also adds to the work that I have to > do in writing SE Linux policy. I am not complaining, merely noting a fact > about the development work. > > > -- > To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > -- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#517790: ITP: mydns -- DNS server using MySQL or PostgreSQL for data storage
On Wednesday 04 March 2009 03:45:19 Giacomo A. Catenazzi wrote: > It is a network daemon, so you should also considering security: > different implementations *could* help security, > so redundancy not always is wast of time. Having different programs to perform a task will decrease the portion of the user-base that runs a given program and if a bug is found it will give some degree of herd immunity. But the down-side is that more programs means more potential security flaws and spreading the time of people who want to fix security problems (including the security team) across more targets. The range of software that is available also adds to the work that I have to do in writing SE Linux policy. I am not complaining, merely noting a fact about the development work. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#517790: ITP: mydns -- DNS server using MySQL or PostgreSQL for data storage
On Mon, 2009-03-02 at 22:59 +0100, Guus Sliepen wrote: > On Mon, Mar 02, 2009 at 09:10:21PM +, Ben Hutchings wrote: > > > > On Mon, Mar 02, 2009 at 02:02:08AM -0600, William Pitcock wrote: > > > > > > > > What does this have over PowerDNS? > > > > > > Probably nothing, else that I am using it and packaging it for my own > > > and thought that it would be a good idea to contribute to Debian, is > > > redundancy a problem ? > > > > Even if you're a perfectly responsible maintainer, a new package still > > requires some work by ftpmaster, the release team, possibly the security > > team, > > and so on. It also increases the number of options a user has to choose > > between. If the package is redundant, this is a waste of their time. > > If it is really redundant then it is also a waste of upstream's time. William, > since you're trying to package it, could you compare it in detail to PowerDNS, > and if there is really little difference, try to see if both upstreams can > work > together and merge their efforts? That would help everyone in the end. > It's not me who is trying to package it, but Sylvain Rochet. William signature.asc Description: This is a digitally signed message part
Re: Bug#517790: ITP: mydns -- DNS server using MySQL or PostgreSQL for data storage
On Mon, 2009-03-02 at 16:42 +0100, Sylvain Rochet wrote: > Hi, > > On Mon, Mar 02, 2009 at 02:02:08AM -0600, William Pitcock wrote: > > > > What does this have over PowerDNS? > > Probably nothing, else that I am using it and packaging it for my own > and thought that it would be a good idea to contribute to Debian, is > redundancy a problem ? No, I was just wondering if it had anything over PowerDNS because PowerDNS has some design concepts that I do not necessarily agree with. Specifically, the behaviour of PowerDNS's listen-address and listen-ipv6 being separate seems like an unpleasant design that I have found annoying. listen-address and listen-ipv6 break in unpleasant ways if one is global scope, and the other is not -- this results in the server failing to start. I should probably file a bug on that, but I am not sure if it is a bug or an intentional thing yet. William signature.asc Description: This is a digitally signed message part
Re: Bug#517790: ITP: mydns -- DNS server using MySQL or PostgreSQL for data storage
Ben Hutchings wrote: On Mon, Mar 02, 2009 at 04:42:19PM +0100, Sylvain Rochet wrote: Hi, On Mon, Mar 02, 2009 at 02:02:08AM -0600, William Pitcock wrote: What does this have over PowerDNS? Probably nothing, else that I am using it and packaging it for my own and thought that it would be a good idea to contribute to Debian, is redundancy a problem ? Even if you're a perfectly responsible maintainer, a new package still requires some work by ftpmaster, the release team, possibly the security team, and so on. It also increases the number of options a user has to choose between. If the package is redundant, this is a waste of their time. It is a network daemon, so you should also considering security: different implementations *could* help security, so redundancy not always is wast of time. ciao cate -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#517790: ITP: mydns -- DNS server using MySQL or PostgreSQL for data storage
William Pitcock writes: > What does this have over PowerDNS? AFAIUI it is a dependency of ispconfig3 (which is not packaged yet). -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#517790: ITP: mydns -- DNS server using MySQL or PostgreSQL for data storage
* Ben Hutchings [Mon, 02 Mar 2009 21:10:21 +]: > On Mon, Mar 02, 2009 at 04:42:19PM +0100, Sylvain Rochet wrote: > > Hi, > > On Mon, Mar 02, 2009 at 02:02:08AM -0600, William Pitcock wrote: > > > What does this have over PowerDNS? > > Probably nothing, else that I am using it and packaging it for my own > > and thought that it would be a good idea to contribute to Debian, is > > redundancy a problem ? > Even if you're a perfectly responsible maintainer, a new package still > requires some work by ftpmaster, the release team, possibly the security team, > and so on. It also increases the number of options a user has to choose > between. If the package is redundant, this is a waste of their time. This is true. However, while increasing the number of options a user has to choose from is a drawback, it's at the same time a benefit. Figuring out which software you want to use for a particular purpose is painful, because all suck in their own ways and you need to find the one that sucks less for you. And when you find it without having to get outside of your distribution's pool, you'll be thankful that somebody made that happen. Sadly, I don't think the decision of deciding which ones will suck less for users can be outsourced to the maintainers, at least not in an unopinionated distribution. Which is of course quite different from saying that we should not be setting a minimum quality bar for all packages, I'm all for that (but how?). So, if mydns is a reasonably fine piece of software, I see no reason why we shouldn't include it. We need less crap in the archive, not less good software as well.¹ Encouraging upstreams to work together is fine, but in practice very seldom will yield results, so I don't have anything against it being done, but I don't think it should be a substitute for packaging the software. (¹) I realize mydns could be complete crap, but the argument still holds. My off-the-top-of-my-heart 2¢, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org A hacker does for love what other would not do for money. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#517790: ITP: mydns -- DNS server using MySQL or PostgreSQL for data storage
On Mon, Mar 02, 2009 at 09:10:21PM +, Ben Hutchings wrote: > > On Mon, Mar 02, 2009 at 02:02:08AM -0600, William Pitcock wrote: > > > > > > What does this have over PowerDNS? > > > > Probably nothing, else that I am using it and packaging it for my own > > and thought that it would be a good idea to contribute to Debian, is > > redundancy a problem ? > > Even if you're a perfectly responsible maintainer, a new package still > requires some work by ftpmaster, the release team, possibly the security team, > and so on. It also increases the number of options a user has to choose > between. If the package is redundant, this is a waste of their time. If it is really redundant then it is also a waste of upstream's time. William, since you're trying to package it, could you compare it in detail to PowerDNS, and if there is really little difference, try to see if both upstreams can work together and merge their efforts? That would help everyone in the end. -- Met vriendelijke groet / with kind regards, Guus Sliepen signature.asc Description: Digital signature
Re: Bug#517790: ITP: mydns -- DNS server using MySQL or PostgreSQL for data storage
On Mon, Mar 02, 2009 at 04:42:19PM +0100, Sylvain Rochet wrote: > Hi, > > On Mon, Mar 02, 2009 at 02:02:08AM -0600, William Pitcock wrote: > > > > What does this have over PowerDNS? > > Probably nothing, else that I am using it and packaging it for my own > and thought that it would be a good idea to contribute to Debian, is > redundancy a problem ? Even if you're a perfectly responsible maintainer, a new package still requires some work by ftpmaster, the release team, possibly the security team, and so on. It also increases the number of options a user has to choose between. If the package is redundant, this is a waste of their time. Ben. -- Ben Hutchings Logic doesn't apply to the real world. - Marvin Minsky -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#517790: ITP: mydns -- DNS server using MySQL or PostgreSQL for data storage
Hi, On Mon, Mar 02, 2009 at 02:02:08AM -0600, William Pitcock wrote: > > What does this have over PowerDNS? Probably nothing, else that I am using it and packaging it for my own and thought that it would be a good idea to contribute to Debian, is redundancy a problem ? Sylvain signature.asc Description: Digital signature
Re: Bug#517790: ITP: mydns -- DNS server using MySQL or PostgreSQL for data storage
On Mon, 2009-03-02 at 03:19 +0100, Sylvain Rochet wrote: > Package: wnpp > Severity: wishlist > Owner: Sylvain Rochet > > > * Package name: mydns > Version : 1.2.8.26 > Upstream Author : Howard Wilkinsin > * URL : http://mydns.pl/ > * License : GPLv2 > Programming Lang: C > Description : DNS server using MySQL or PostgreSQL for data storage > > Free DNS server for UNIX implemented from scratch and designed to > utilise the MySQL or PostgreSQL database for data storage. > .. > Its primary objectives are stability, security, interoperability, and > speed, though not necessarily in that order. > .. > MyDNS does not include recursive name service, nor a resolver library. > .. > It is primarily designed for organisations with many zones and/or > resource records who desire the ability to perform real-time dynamic > updates on their DNS data via MySQL or PostgreSQL. What does this have over PowerDNS? William signature.asc Description: This is a digitally signed message part
Bug#517790: ITP: mydns -- DNS server using MySQL or PostgreSQL for data storage
Package: wnpp Severity: wishlist Owner: Sylvain Rochet * Package name: mydns Version : 1.2.8.26 Upstream Author : Howard Wilkinsin * URL : http://mydns.pl/ * License : GPLv2 Programming Lang: C Description : DNS server using MySQL or PostgreSQL for data storage Free DNS server for UNIX implemented from scratch and designed to utilise the MySQL or PostgreSQL database for data storage. .. Its primary objectives are stability, security, interoperability, and speed, though not necessarily in that order. .. MyDNS does not include recursive name service, nor a resolver library. .. It is primarily designed for organisations with many zones and/or resource records who desire the ability to perform real-time dynamic updates on their DNS data via MySQL or PostgreSQL. -- System Information: Debian Release: squeeze/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
