Hi Thomas Hood Many thanks for your response, I'm sorry for the late answer to your further questions.
On Sun, Aug 03, 2008 at 09:27:16PM +0200, Thomas Hood wrote: > Salvatore Bonaccorso wrote: >> resolvconf: Error: /etc/resolvconf/run/interface is not a directory > > > As implied, /etc/resolvconf/run/interface must be a directory. > /etc/resolvconf/run is a symbolic link. The initscript /etc/init.d/resolvconf > creates the target of this symbolic link as a directory (if it is not already > there) and also creates its subdirectory "interface". > > * Perhaps you do not have /etc/init.d/resolvconf configured to run in > runlevel S resolvconf get's started on boot, but as said, it seems it fails somewhere. Probably relative to your second question. First I have the following: lorien:/etc/init.d# ls -l /etc/rcS.d/S14resolvconf lrwxrwxrwx 1 root root 20 2008-08-02 22:56 /etc/rcS.d/S14resolvconf -> ../init.d/resolvconf lorien:/etc/init.d# > * Perhaps the filesystem into which /etc/resolvconf/run points is not > mounted Yes, /etc/resolvconf/run points to a tmpfs filesystem, but this at the end is mounted correctly: lorien:/etc/init.d# ls -l /etc/resolvconf/run lrwxrwxrwx 1 root root 23 2008-08-02 22:56 /etc/resolvconf/run -> /lib/init/rw/resolvconf lorien:/etc/init.d# mount | grep /lib/init/rw tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) lorien:/etc/init.d# Is this possible that resolvconf (but by what change? I had previously before the date given in in the first email, and before upgrading the packagelist attached) working resolvconf correctly? Many thanks in advance, I will try to provide more needed information. Best regards Salvatore -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]