-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mertens Bram wrote: | Hi, | | Most rpms are build for the i386 architecture, I run my RH7.3 on an | i686, does it make much sense to rebuild rpms before installing them? | | If I understand the manual correctly I would have to download the | src.rpm then run the command rpm --rebuild xxx.src.rpm which would | install the software after optimising it for the i686 architecture. | | Or isn't it that simple?
It is that simple, however VERY time consuming. You may want to search the archives for some of my previous posts on this subject. I did this very thing for Red Hat 7.3. Did an "EVERYTHING" install on a build machine, and then built all packages using: rpmbuild --rebuild --target i686 <package>.src.rpm Took several days to say the least. The performance increase was notable, but I'm not sure it was worth 4 days of compile time (will I save 4 days over the next year? probably not). However - if you choose to do a limited amount of packages, consider doing all of the KDE and/or Gnome packages, along with the XFree86 packages. That's where I saw my biggest gains. When I upgraded my home machine to Red Hat 8.0, I didn't waste the time recompiling everything for the Athlon target, but did focus on the daemons and packages which I used the most (XFree, Gnome, apache, etc.). I've since done the same at work for our production machines. I then run the following: cd <rpm directory> for package in `rpm -qa`; do if [ -f $package.athlon.rpm ]; then rpm -Uvh - --force $package.athlon.rpm; fi; done This will reinstall the packages which you've rebuild with the recompiled packages. If you have a multitude of machines - it may be best to set up an NFS share with the Red Hat tree in there. What I did is copied all CD's into a directory, and then placed the rebuild SRPM packages (including the newer errata) into the RedHat/RPMS directory. Having a duplicate i386 and i686 is okay. Then run anaconda's genhdlist to refresh the package list. Now you can do a network install and the installer will pick the i686 packages if applicable to the machine doing the network install. Works great for me here. Only down side is that I find myself recompiling the errata to i686 as well before applying to those servers. So far no troubles for me. No need to redit the rpm macros unless you want to get more specific than i686 (i.e. -mcpu=pentiumIII or whatever). Do note, however, that some packages don't like to be rebuilt, and others behave differently if they are (i.e. perl and it's cpan modules). Unless you change some config files to match, you're going to be left scratching your head. Enjoy, - -Rick - -- Rick Johnson, RHCE - [EMAIL PROTECTED] Linux/WAN Administrator - Medata, Inc. PGP Public Key: https://mail.medata.com/pgp/rjohnson.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Signed and/or encpryted for everyone's protection. iEYEARECAAYFAj3+TcYACgkQIgQdhlSHZgMU2ACfXoB8vB229Q7QM+Bul8uZkast UWMAoLFHsPkKqu4zdWMhURxiOZ6kwsyo =a9Az -----END PGP SIGNATURE----- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
