I was messing with /etc/rc.d/init.d/network tonight trying to help out
another user to get aliased interfaces to work correctly. I had hacked
the file to bits without creating a backup (shame on me, I know).
I used 'rpm -e --nodeps' to remove the initscripts package thinking I
could easily reinstall it from the CD. How wrong I was.
I used 'rpm -i --nodeps --force' to install the package but
/etc/rc.d/init.d/network didn't reappear. Actually _NONE_ of the files
contained in the package got installed (rc.local, for instance, didn't
get replaced -- my changes were still at the bottom of the file).
The --nodeps in both of the above lines are necessary because RPM
(rightly) believes that the package is necessary. The --force is
necessary upon reinstallation because RPM (wrongly) still believes the
package is installed.
Thinking it might have been a bad package, I installed the source
package and rebuilt it with 'rpm -bb' then reinstalled it. Still no
change. RPM thinks it installed the package!
Finally, I ended up just going into the BUILD/ directory and hand
copying the files I needed back into their directories.
Is something horribly broken with the RPM database that it's not getting
updated when packages are removed? I previously reported a bug with
portmap in which it's entry didn't get removed from the database when
the package was removed -- any progress on that one?
So, the question is -- How did initscripts files get installed in the
first place if they won't install now? How do I GET that package to
reinstall correctly?? I can provide 'rpm -Uvvvvvh --nodeps --force'
output if necessary...
--
Steve Philp
Network Administrator
Advance Packaging Corporation
[EMAIL PROTECTED]
