It is different from upstream MySQL in many ways as that page explains. 

On Wed, Apr 5, 2017 at 8:03 AM, Reindl Harald <h.reindl@thelounge.net> wrote:

and why?

it is and where it isn't unintentional report it and help to get it fixed, that said from a admin which dozens of MariaDB servers where the datadir was originally created on Windows under MySQL 3.x, got moved in prduction for some years to MacOS, later to Linux and now is running MariaDB 10.1 just fine with the same datadirs and the help of "mysql_upgrade" over the years


Am 05.04.2017 um 16:50 schrieb MARK CALLAGHAN:
Maybe someone should edit the too strong claims on https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-compatibility/

In bold at the top of the page...

MariaDB is a binary drop in replacement for MySQL


On Tue, Apr 4, 2017 at 9:58 PM, Sergei Golubchik <serg@mariadb.org> wrote:
Hi, Mark!

On Apr 04, Mark Callaghan wrote:
> With upstream (5.6 and 5.7) MySQL when I use cmake
> -DCMAKE_INSTALL_PREFIX=$X, then after I install the build, mysqld searches
> in $X/etc for my.cnf. That is not true for MariaDB Server 10.2. Why can't
> this match upstream?


It certainly can. It just doesn't. Because we merge from 5.6 into
MariaDB feature by feature, and nobody has requested this particular
feature so far. At least I couldn't find it in Jira.

Regards,
Sergei
Chief Architect MariaDB
and security@mariadb.org



--
Mark Callaghan
mdcallag@gmail.com


_______________________________________________
Mailing list: https://launchpad.net/~maria-discuss
Post to     : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp




--
Mark Callaghan
mdcallag@gmail.com