Title release 2011.12-rc1: dns bootoption is broken
Priority urgent Status resolved
Superseder Nosy List mika
Assigned To Topics release-stopper

Created on 2011-12-12.11:57:52 by mika, last changed 2011-12-21.00:49:35 by mika.

msg4151 (view) Author: mika Date: 2011-12-21.00:49:35
resolvconf 1.63 is available in Debian/unstable and grml-live repository, issues 
has been solved for us therefore (known to be working in recent daily builds and 
supposed to be working in stable release therefore).
msg4126 (view) Author: mika Date: 2011-12-12.22:07:12
Fixed upstream, we probably need to sync 1.63 from unstable to our repository 
msg4124 (view) Author: mika Date: 2011-12-12.13:00:43
Downgrading resolvconf from 1.62 to 1.61 is supposed to fix our issue.
Details and bug report filed at
msg4123 (view) Author: mika Date: 2011-12-12.12:03:15
When manually invoking "resolvconf -u" the /etc/resolv.conf is OK.
msg4122 (view) Author: mika Date: 2011-12-12.11:57:51
Tested with Grml64 2011.12-rc1.

Expected behaviour: booting with dns= should provide /etc/resolv.conf 
with "nameserver"

Problem: /etc/resolv.conf is a dangling symlink, pointing to a non-existing file

Booting with dns= writes the entry to /etc/resolvconf/resolv.conf.d/base 
but /etc/resolv.conf is a dangling symlink pointing to a non-existing 
/etc/resolvconf/run/resolv.conf. /etc/resolvconf/run itself points to (existing) 
Date User Action Args
2011-12-21 00:49:35mikasetstatus: in-progress -> resolved
messages: + msg4151
2011-12-12 22:07:12mikasetstatus: chatting -> in-progress
messages: + msg4126
2011-12-12 13:00:43mikasettopic: + release-stopper
messages: + msg4124
2011-12-12 12:03:15mikasetstatus: unread -> chatting
messages: + msg4123
2011-12-12 11:57:52mikacreate