[Resolvconf-devel] Bug#504409: resolvconf runs too early in boot sequence - can't mkdir
Peter T. Breuer
ptb at inv.it.uc3m.es
Mon Nov 3 15:29:15 UTC 2008
Resolvconf was running before /var was mounted at bootup, and tried
to mkdir /var/run/resolvconf while / was readonly.
The result is some mess on screen and some messup when /var is
eventually mounted (since /var/run/resolvconf may not be there)
or else no messup (/var/run/resolvconf happens to be there already).
Anyway, it runs too early. It was linked in at S07. I moved to S36
(after S35mountall). In rcS.d, I mean.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-19-generic (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/bash
Versions of packages resolvconf depends on:
ii coreutils 6.10-6 The GNU core utilities
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
resolvconf recommends no packages.
resolvconf suggests no packages.
-- debconf information excluded
More information about the Resolvconf-devel