[Chanoch (Ken) Bloom] > I'm seeing this bug too. I upgraded a about a week ago with the command > $ sudo aptitude install sysv-rc
Thank you for the feedback. I believe I understand what is going on here. file-rc fail to flag that it is using the legacy boot ordering, and as the system was convereted from sysv-rc to file-rc before sysv-rc created /etc/init.d/.legacy-bootordering before the system was switched to file-rc, the boot ordering end up wrong. I suspect the proper fix for this is for file-rc to create /etc/init.d/.legacy-bootordering when it is in use. This way sysv-rc will know what to do when switching from file-rc to sysv-rc. Another approach would be for sysv-rc to look for start symlinks in rc0.d or rc6.d, and assume legacy boot ordering is in effect if such symlinks are found. If this approach is used, we can probably also get rid of the /etc/init.d/.legacy-bootordering flag file. I welcome input on the approaches. Not sure which is best. Btw, note that because file-rc fail to remove runlevel.conf when switching from file-rc to sysv-rc, it is not safe to switch back to file-rc. Any changes to the symlinks in /etc/rc?.d/ done after switching to sysv-rc will be lost. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
