Comment 4 for bug 1382285

Potential solutions to the bug report:
(1) The lazy solution: this report will be marked as invalid, because the problem is not in the package but in the user's configuration file
(2) The smart solution: a parser to check the user's configuration file and issue warnings for deprecated configuration options
(3) The mid-way solution: catch the exit status code after starting mysqld and if it fails to start suggest to the user to investigate their configuration file
(4) An alternative solution: catch the exit status code after starting mysqld and if it fails to start, put forward the option to the user to backup the old configuration file and install a fresh one