I have recently went though a couple of days tinkering with mysql in various versions and finally decided just to compile it from scratch as there were to many other un known variables to solve the problems with making the package run. This version has been tested to the point that it does install and run. But that is about it, so if you are interested in testing it out and possibly figuring out if there are any problems.

Updated below

If you are afraid that you might make a mistake. The chances are high that you will never learn anything.

The new version of mysql can be installed without damage to the old version. The one thing that you must do is to disable the old version first. This can be done through the setup program very easy in the advanced package menu "enable/disable" section. The old version used rc_mySQL and the new version uses rc_mysql.The reason this can be done is because the new package uses a different directory than the old one. So if anything goes wrong or you have any problems you can just re enable the old version and disable the new version. The one thing that I would NOT recommend doing is to uninstall the new version if you are planning on switching back to the old version, because it could remove things that you still need.

If you are afraid that you might make a mistake. The chances are high that you will never learn anything.

Lightning wrote: The new version of mysql can be installed without damage to the old version. The one thing that you must do is to disable the old version first. This can be done through the setup program very easy in the advanced package menu "enable/disable" section. The old version used rc_mySQL and the new version uses rc_mysql.The reason this can be done is because the new package uses a different directory than the old one. So if anything goes wrong or you have any problems you can just re enable the old version and disable the new version. The one thing that I would NOT recommend doing is to uninstall the new version if you are planning on switching back to the old version, because it could remove things that you still need.

thanks, i have leeched yesterday some other files to.oh well, my freesco box is almost doing the same as a Big P4 under linux

The mysql package has been updated to resolve a missing binary "rm" and to resolve a problem with adding the "expr" binary to FREESCO which causes the "uptime" script to fail. So the scripots have been modified to use expr.mysql instead of just "expr" and the added binary has also been renamed. The rc_mysql has also bee changed a minor ammount to work more efficiently. Past that the package is identical to the previous release version, so if you are currently running mysql without any problems there is no reason to update to this version. This version is just to fix the few minor bugs in the original package that can be fixed manually and is just intended for new instalations and is not intended as an upgrade to the previous package.SPECIAL NOTE: The password hash in mysql 4.1.7 is not compatible with older data base managers, nor is it compatible with the current integration into the Apache package. So if you need those features over the new improvements of mysql 4.1.7 then you should install the older version of mysql 3.23.37 which is compatible and is available from . <a href='http://www.freescosoft.com/' target='_blank'>FREESCOsoft</a>

These errors are because those files do not exist the very first time your machine starts mysql. But they do exist now and those errors will never show again. If your machine would have been named "router" which is the default the errors don't appear as the files exist by default.

If you are afraid that you might make a mistake. The chances are high that you will never learn anything.

But after reboot mysql starts normally. It's happens just when I try to restart mysql or start it after stopping. May be someone will help me, where I must look for to solve this problem. Thanks. Sorry for my English.

p.s. Now I was playing with restarting mysql (just for experiment) on my working machine and finally I recieved the same message too. Mysql is down and my forum on local network is down too. But I know that after a little pause (5-10 minute, I have a little experience) mysql can starts normally. I hope...))