> We installed several rpm's and found our symbolic links in /etc/init.d/rc3.d > had been changed, and thus the startup re-ordered. The following is a list o > f rpm's I installed: > glib-devel-1.2.10-5.s390.rpm > glibc-20020502.rpm > glibc-devel-20020502.rpm > k_timer-20020521.rpm > rpm-20020502.rpm > fileutils-20020326.rpm > sudo-20020424.rpm > timezone-20020502.rpm > ucdsnmp-20020304.rpm > yast-20020506.rpm > yast2-config-online-update-20020508.rpm > yast2-core-pkginfo-20020508.rpm > yast2-trans-online-update-20020508.rpm > gtk+-devel-1.2.10-11.s390.rpm > > Several of the S08/9/10/11/12 * (etc. links were changed to S01/2/3/4/5/6/7/8 > * (etc. > Has anyone else experienced this problem with this or any other maintenance? > This occurred the same way on 2 different images.
I guess that since YAST2 is involved, you're using SuSE. I'm completely unfamiliar with SuSE Linux, but I guess the yast2 packages are the most likely. The standard way (on RHL) of telling what scripts a package runs at install/uninstall time is rpm -q --scripts yast2-config and so on for each package. -- Cheers John Summerfield Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Note: mail delivered to me is deemed to be intended for me, for my disposition. ============================== If you don't like being told you're wrong, be right!
