Ken Heard wrote: > > Unable to migrate to dependency-based boot system. > > Tests have determined that problems in the boot system exist which prevent migration to dependency-based boot sequencing: > > ... > > package hdparm removed but not purged, > > package lisa removed but not purged, > > package lm-sensors removed but not purged > > > > http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot That wiki page is really the canonical place for this information. But basically you have a common situation. You have installed packages and you have removed packages. Some of those packages have files in /etc/init.d/*. Some of those have been removed but not purged. Packages that are removed keep their conffiles behind on the system so that you can easily install them again and have the same configuration as before. And that is the problem here. Packages that have been removed but not purged are also not updated and therefore have old copies of /etc/init.d/* files that do not have all of the headers in them that the new system requires. All of that is pretty much typical of a system that has been around for a while. But to complete an upgrade the lint needs to be cleaned up. > I got so far as to find out what dependency-based boot system is but I > have been unable to find out what -- if anything -- I need to do with > respect to these apparent problems before running "dpkg-reconfigure > sysv-rc". I read the referenced URL and other sites turned up by a > Google search but I am none the wiser. Could someone please enlighten me? It is a good time to tidy up the system. Look through your list of removed packages that have not been purged. Those are ones that have been removed 'r' but still have configuration files for them 'c' left on the system. dpkg -l | grep ^rc Review that list and purge anything that you don't need anymore. Using the suggestions from your output above: dpkg --purge lm-sensors lisa hdparm That might be enough. Start there. But it is also possible that files in /etc/init.d exist that did not come from a package. These could be because a human created them. It could be because a package installed them but lost track of them. It could also be because an older version of the package used them and now they are obsolete. I have scripted up checks for the above but it is really more than I want to post here as one-liners. Start with the above and see if you make progress. Bob
Attachment:
signature.asc
Description: Digital signature