Comment 23 for bug 1003842

On 29/05/12 07:06, Thomas Hood wrote:
> We aren't getting duplicates of #1000244 so it's probably not a
> frequently occurring problem. If resolvconf were systematically
> failing to create the resolv.conf symlink we'd be getting hundreds of
> reports about it. Based on what we know now it's most probable that
> #1000244 was a result of some sort of administrator error. The version
> of resolvconf that was included in Precise wasn't perfect but the bugs
> were fairly minor and the known ones have since been fixed.

I'm certain that it was not an 'administration error' - I discovered
that my networking was broken within an hour of clean install. Others
at my office have complained of search domains not working, which smells
of resolvconf being broken (my understanding is that resolvconf is
responsible for populating search domains in this new resolution chain).

I also don't know how you can release a system resolver implementation
that "wasn't perfect", or even close to it (when the existing one wasn't
broken and the new implementation adds serious complexity for
questionable gain), particularly in an LTS release, but suggesting that
'the users broke it' isn't going to fix things.

In any case, I'm still subscribed to the other bug, so happy for any
continued discussion of that particular issue to happen there.