Thanks for responding Iain, Yes, there were problems with the up2date. I updated everything, about 60 some RPMS - took forever to download. The Perl RPM downloaded with a checksum error. Up2date asked if I wanted to continue - Yes, everything else downloaded successfully. During the automated install, it failed on the bad Perl RPM. It continued to do things for awhile then said it failed. I don't know what happened or where to look for status of the up2date. Thanks, Brian Below is the list of RPMs downloaded, sorry for the length: bash-2.05b-20.1.i386.rpm cdda2wav-2.0-11.9.1.i386.rpm cdrecord-2.0-11.9.1.i386.rpm cups-1.1.17-13.3.i386.rpm cups-libs-1.1.17-13.3.i386.rpm eog-2.2.0-2.i386.rpm ethereal-0.9.13-1.90.1.i386.rpm evolution-1.2.2-5.i386.rpm foomatic-2.0.2-15.1.i386.rpm gdm-2.4.1.3-5.1.i386.rpm ghostscript-7.05-32.1.i386.rpm glibc-2.3.2-27.9.i386.rpm glibc-common-2.3.2-27.9.i386.rpm glibc-devel-2.3.2-27.9.i386.rpm gnupg-1.2.1-4.i386.rpm gtkhtml-1.1.9-0.9.1.i386.rpm gtkhtml-devel-1.1.9-0.9.1.i386.rpm hpijs-1.3-32.1.i386.rpm httpd-2.0.40-21.5.i386.rpm httpd-manual-2.0.40-21.5.i386.rpm kdebase-3.1-15.i386.rpm kdegraphics-3.1-5.i386.rpm kdelibs-3.1-12.i386.rpm kernel-2.4.20-20.9.i586.rpm krb5-devel-1.2.7-14.i386.rpm krb5-libs-1.2.7-14.i386.rpm mkisofs-2.0-11.9.1.i386.rpm mod_ssl-2.0.40-21.5.i386.rpm mutt-1.4.1-1.i386.rpm mysql-3.23.56-1.9.i386.rpm mysql-server-3.23.56-1.9.i386.rpm nfs-utils-1.0.1-3.9.i386.rpm nscd-2.3.2-27.9.i386.rpm openssh-3.5p1-11.i386.rpm openssh-askpass-3.5p1-11.i386.rpm openssh-askpass-gnome-3.5p1-11.i386.rpm openssh-clients-3.5p1-11.i386.rpm openssh-server-3.5p1-11.i386.rpm openssl-0.9.7a-20.i386.rpm openssl-devel-0.9.7a-20.i386.rpm pam_smb-1.1.6-9.9.i386.rpm perl-5.8.0-88.3.i386.rpm perl-CGI-2.81-88.3.i386.rpm perl-CPAN-1.61-88.3.i386.rpm perl-DB_File-1.804-88.3.i386.rpm php-4.2.2-17.2.i386.rpm php-imap-4.2.2-17.2.i386.rpm php-ldap-4.2.2-17.2.i386.rpm php-mysql-4.2.2-17.2.i386.rpm printman-0.0.1-0.20021202.12.1.i386.rpm redhat-config-date-1.5.15-1.noarch.rpm redhat-config-network-1.2.15-1.noarch.rpm redhat-config-network-tui-1.2.15-1.noarch.rpm redhat-config-printer-0.6.47.11-1.i386.rpm redhat-config-printer-gui-0.6.47.11-1.i386.rpm rhpl-0.93.4-1.i386.rpm samba-2.2.7a-8.9.0.i386.rpm samba-client-2.2.7a-8.9.0.i386.rpm samba-common-2.2.7a-8.9.0.i386.rpm sendmail-8.12.8-9.90.i386.rpm tcpdump-3.7.2-1.9.1.i386.rpm unzip-5.50-33.i386.rpm xinetd-2.3.11-1.9.0.i386.rpm Subject: Re: network config problem From: Iain Buchanan <iain@xxxxxxxxxxxx> To: shrike-list@xxxxxxxxxx Date: Fri, 17 Oct 2003 13:35:26 +0930 On Fri, 2003-10-17 at 13:29, Brian Scudder wrote: > Y'all, > After I preformed an "up2date" many things are a miss on my system. I'll > work through these one at a time. > > While starting the network config gui to 'activate' my modem I receive an > error message stating I should open a problem report. I've checked bugzilla > and did not see anything exactly like this. [snip] Did everything update to 100%? Were there any checksum or sig errors? Did you have to kill rpm or anything else while in the update process? Any of these things could point to a corrupt rpm, which is a good thing to rule out first. It might also help to know what rpms you updated. HTH, -- Iain Buchanan <iain@xxxxxxxxxxxx> -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
