Processed: Re: [Resolvconf-devel] Bug#651801: resolvconf: /etc/resolv.conf is a broken link after reboot

2011-12-13 Thread Debian Bug Tracking System
of Bug 651827 to the same value. > tags 651801 confirmed pending Bug #651801 [resolvconf] resolvconf: /etc/resolv.conf is a broken link after reboot Added tag(s) confirmed and pending. > merge 651801 651827 Bug#651801: resolvconf: /etc/resolv.conf is a broken link after reboot Bug#651827: resolvco

Bug#651801: [Resolvconf-devel] Bug#651801: resolvconf: /etc/resolv.conf is a broken link after reboot

2011-12-12 Thread Eike von Seggern
Hi Thomas, adding the `resolvconf -u' indeed fixes this problem. Thank you very much! Just to let you know my use-case: I have a /etc/resolvconf/resolv.conf.d/tail with some fall-back nameserver entries. This is probably not the correct way, but it worked, and saves me specifying these fall-backs

Bug#651801: [Resolvconf-devel] Bug#651801: resolvconf: /etc/resolv.conf is a broken link after reboot

2011-12-12 Thread Thomas Hood
Hi again Elke, Also, please make the change I described earlier in this bug thread and let me know whether or not this fixes your problem. (The change is to add a "resolvconf -u" to the initscript just after "resolvconf --create-runtime-directories".) -- Thomas

Bug#651801: [Resolvconf-devel] Bug#651801: resolvconf: /etc/resolv.conf is a broken link after reboot

2011-12-12 Thread Thomas Hood
Hi there and thanks very much for the additional information. The mere absence of a file /etc/resolv.conf is not a bug. This is an allowed situation if there is no nameserver information; the resolver does not require the file to be present. But from the fact that you are reporting here I infer

Bug#651801: resolvconf: /etc/resolv.conf is a broken link after reboot

2011-12-12 Thread Eike von Seggern
Package: resolvconf Version: 1.62 Followup-For: Bug #651801 Dear Thomas, I have the same issue as Teodor: After a reboot my wireless interface is up and working but /etc/resolv.conf points to /run/resolvconf/resolv.conf, which does not exist. After a reboot the layout of /etc/resolvconf/ is #

Bug#651801: [Resolvconf-devel] Bug#651801: resolvconf: /etc/resolv.conf is a broken link after reboot

2011-12-12 Thread Thomas Hood
It is possible that this is the same issue as #651827. The issue there is that no update is run at boot, so if your system only uses the base file (and no interface configurers, e.g., ifupdown, dhclient, are run) then your dynamically generated /etc/resolv.conf will be absent. If you think that t

Bug#651801: [Resolvconf-devel] Bug#651801: resolvconf: /etc/resolv.conf is a broken link after reboot

2011-12-12 Thread Thomas Hood
Hi there, thanks for the bug report and apologies for whatever I've screwed up in version 1.62. Can you please let me know a little more about your configuration? > Every time I reboot the system I have to fix /etc/resolv.conf to have DNS > working again. Since /etc/resolv.conf -> /etc/resolvcon

Bug#651801: resolvconf: /etc/resolv.conf is a broken link after reboot

2011-12-12 Thread Teodor
Package: resolvconf Version: 1.62 Severity: grave Hi, Every time I reboot the system I have to fix /etc/resolv.conf to have DNS working again. Since /etc/resolv.conf -> /etc/resolvconf/run/resolv.conf, the later is not automatically created at reboot. I see now that this is actually a symlink to