> > something that makes it all work but obviously doesn't update the > > MySQL already on the RaQ550. > > I have upgraded MySQL on my RaQ550 to MySQL-3.23.51 a while > ago and there is a > little more to that: The 550 uses a different version of > GLIBC than the other > RaQs and the Qube use. Although one could force the RPM > installation of > MySQL-3.23.37 it sure won't do any good as 3.23.37 from > PKGmaster.com was > compiled against a different GLIBC. > > In the end, if you force the installation of a MySQL which > was compiled > against a wrong GLIBC then you'd be inviting the same memory > leakage problems > which the RaQ3, RaQ4 and XTR have after the last official > GLIBC updates. no I didn't force the update - the installed rpms were the same when the pkg had finished its something else that the pkg does that seems to kick mysql into action whether its setting the password or starting MySQL - of course the problem was that once I hacked about with it I then couldn't look to see what the problem was in the first place with doing a rebuild which I will do at the weekend and report back. Gavin
Sun Cobalt and other Linux administration by Zeffie
A Sun Cobalt and Linux Specialist Since 1999
Sun Cobalt Repairs, Development, and Maintenance.
Home of the Worlds Largest Collection of Sun Cobalt Updates!
Sun Cobalt Spam Filter, Security, Firewall, Anti Virus Products.
734-454-9117 US Toll Free 800-231-4459
Copyright 2009 by Electronic Consultants Inc.