Your message dated Sun, 28 Jun 2009 20:16:11 +0200
with message-id <[email protected]>
and subject line Re: Bug#504409: resolvconf runs too early in boot sequence -
can't mkdir
has caused the Debian Bug report #504409,
regarding resolvconf runs too early in boot sequence - can't mkdir
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
504409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504409
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: resolvconf
Version: 1.42
Severity: normal
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
--- End Message ---
--- Begin Message ---
With the provided informasjon, we are unable to figure out how the
machine in question ended up with the strange state of the boot
system. Without more informasjon (and none of my questions from
2008-11-05 are answered), there is not much more to do. Because of
this, I close this bug. If you have more information or an idea how
to reproduce it, please feel free to reopen.
Happy hacking,
--
Petter Reinholdtsen
--- End Message ---
