MySQL RPMs for RH9?
am 02.01.2007 04:35:24 von sterickson
I have a client who has a RH9 server that I'm not allowed to upgrade
to something newer. It has MySQL 3.23.58 on it and I need to replace
that with the newest I can get. The MySQL-AB site doesn't seem (unless
I missed it, which is quite possible) to have any RPMs for RH9
anymore.
Can anyone point me to where I can find this?
--
-ste
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql@m.gmane.org
Re: MySQL RPMs for RH9?
am 02.01.2007 19:52:22 von Joerg Bruehe
Hi Shaun!
Shaun T. Erickson wrote:
> I have a client who has a RH9 server that I'm not allowed to upgrade
> to something newer. It has MySQL 3.23.58 on it and I need to replace
> that with the newest I can get. The MySQL-AB site doesn't seem (unless
> I missed it, which is quite possible) to have any RPMs for RH9
> anymore.
>=20
> Can anyone point me to where I can find this?
I do not follow the RedHat version numbers, so take this with caution:
-) RedHat 9 is pretty old, I heard it is the predecessor of Fedora.
MySQL does not build packages specific for this platform.
-) RedHat 9 already uses version 2.3 of glibc (*please* check this).
Then, any "generic" RPM for glibc 2.3 and the correct CPU should fit.=
As an alternative, you can also use a tar.gz package for the proper=20
version of glibc and the CPU in that machine.
Migrating from 3.23 to current (which means 5.0) consists of several=20
steps, I read it is best done to first 4.0 and then 4.1.
The new password handling is one issue to look at, but maybe you also=20
want to use different table handlers or other new features now ?
If that server is running old software, it most likely also consists of=20
old hardware: Beware that software tends to grow in functions and=20
features, hence also in code size and (at least a bit) in execution path =
length.
It might be worthwhile *not* to install the newer MySQL on the old=20
machine but rather use a newer, current hardware and let the MySQL=20
server run there, access it remotely.
Then, again stepwise, also other services or applications could be=20
migrated to the new machine.
Regards and a Happy New Year to all of you,
Jörg
--=20
Joerg Bruehe, Senior Production Engineer
MySQL AB, www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql@m.gmane.org