As I said, I am not sure at what point this issue occurred. I've been running hardy (32-bit) for some time now. I only happened to notice the broken symlink by running a find over /etc. It doesn't actually cause any problems, since broken symlinks in /etc/rc*.d are just ignored.
I'm a bit confused as to what possible difference my hardware would make, but this machine is a Compaq M2105US. I haven't investigated re- creating the bug, and I can't even verify that the problem is still present in the current version. I realise that this is of almost no help at all in identifying the issue, I just wanted to get it documented. I'm sorry I don't have more information. >From /var/log/dist-upgrade/apt-term.log (and term.log): Preparing to replace procps 1:3.2.7-3ubuntu5 (using .../procps_1%3a3.2.7-5ubuntu1_i386.deb) ... Preparing to remove obsolete, unmodified conffile: /etc/init.d/procps.sh `/etc/init.d/procps.sh' -> `/etc/init.d/procps.sh.from-preinst' Unpacking replacement procps ... Indeed, the /etc/init.d/procps.sh was removed, it's just the symlink in rcS.d that was not. -- /etc/rcS.d/S17procps.sh left after upgrade https://bugs.launchpad.net/bugs/228406 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
