<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On Sun, 17 Apr 2011 20:09:40 +0200 Thomas Hood <jdthood@gmail.com>
wrote:<br>
> I have just reassigned this report from resolvconf to<br>
> insserv because I believe that the insserv maintainers<br>
> will have more insight into the problem than I have.<br>
> <br>
> Here is a summary of what we have found out, as<br>
> described earlier in the report's message log.<br>
> <br>
> Resolvconf was misbehaving on the submitter's two fresh<br>
> squeeze machines. This was because resolvconf's initscript<br>
> had been installed in rcS.d at the traditional sequence<br>
> number S38 rather than at the appropriate sequence number<br>
> for the submitter's systems, S13. This was because,<br>
> although the submitter's systems had evidently been<br>
> subjected to boot sequence reordering by (I presume)<br>
> insserv, the /etc/init.d/.legacy-bootordering flag file was<br>
> still present on his systems.<br>
> <br>
> This incongruous situation --- reordered boot sequence, but<br>
> legacy flag file present --- may have resulted from the<br>
> presence of initscripts on the system lacking LSB headers.<br>
> -- <br>
> Thomas Hood<br>
<br>
<br>
This is an interesting bug. Though I'm not sure if it is still a
problem. As far as I know, current versions of update-rc.d and
insserv do not check for the ".legacy-bootordering" file flag (or
create or remove it). I could be mistaken, but I think this was
either resolved quietly in the past, or is outside our scope. I
tried running the latest insserv with and without
/etc/init.d/.legacy-bootordering in place and didn't encounter
differences in behaviour.<br>
<br>
I think we can probably mark this one as closed unless someone
comes up with a way insserv is misbehaving in this situation.<br>
<br>
- Jesse<br>
<br>
</jdthood@gmail.com>
</body>
</html>