I'd stick with the 386 versions for compatability. Later on you can experiment (if you dare) with the i686 versions. Generally speaking, of the intel variety, the non-i386 directories will have far less stuff in them, you can solve the dependencies by grabbing the i386 stuff as they will run on any CPU (well, not 8086, 80286 but linux won't either). Another gotcha is I've seen stuff in the updates area that's older than what's in the CD images on occasion.
On Tue, 15 Jan 2002, Chris Rennie wrote: > Hi > I have a query about RedHat's Errata site. > > For each erratum there are typically several architectures listed > and several files within each architecture. I am running an i686 > machine (as reported by uname -a), so to update glibc I downloaded > glibc-2.2.4-19.3.i686.rpm > which was the only file listed for the i686 architecture. But running > rpm -Fvh glibc-2.2.4-19.3.i686.rpm > produced > error: failed dependencies: > glibc-common = 2.2.4-19.3 is needed by glibc-2.2.4-19.3 > > Do I complain to RedHat? > Do I download glibc-common-2.2.4-19.3.i386.rpm from the i386 section? > Do I download all packages (namely glibc glibc-common glibc-devel > glibc-profile nscd) listed under the i386 section and run > rpm -Fvh *.rpm? > > I wouldn't worry about experimenting, except that glibc is rather > vital! > -- ---<GRiP>--- Web: www.arcadia.au.com/gripz Phone/fax: 02 4950 1194 Mobile: 0408 686 201 -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
