"Also sprach Debian Bug Tracking System:" > > #504409: resolvconf runs too early in boot sequence - can't mkdir > > It has been closed by Petter Reinholdtsen <[email protected]>. > -- > 504409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504409 > Debian Bug Tracking System > Contact [email protected] with problems
-- Start of included mail From: Petter Reinholdtsen <[email protected]> > 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 Yerrs .. I don't know either. I was after an upgrade, as I recall. I happened to check the boot sequence carefully afterwars and noticed that resolvconf failed with an error. I tracked the error to the reported condition. I suppose it's always possible that some strange error along the way cascaded down to the observed conditions. > 2008-11-05 are answered), there is not much more to do. Because of Nobody has asked me questions (I recall a conversation a few months ago the last time this bug report got discussed, but nothing before that!). I'm always willing to answer any questions. > this, I close this bug. If you have more information or an idea how > to reproduce it, please feel free to reopen. Let's look at what I can ... > 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 I don't know why it would have been at S07. Presumably that is some kind of default. It would have possibly been the fact that the debian update-rc.d system had not been run before that> I probably never had that stuff on my system at all at that time. Therefore I would diagnose a possible undeclared dependency on update-rc.d, resulting in update-rc.d not being installed until after resolvconf was installed. > (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 Yes. Notice that update-rc.d is not declared as having to be present. Therefore that definitely seems indicated as the fault! > > resolvconf recommends no packages. > > resolvconf suggests no packages. > Regards Peter -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
