12.3 patch over wrote my /etc/init/d/mysql script

English Applications
#1

/etc/init/d/mysql script was over written by the mariadb patch. Was this my fault? I guess I should have read the patch list better. I had to restore from tape the old script file.

mysqld.log

nnoDB: Last MySQL binlog file position 0 3601430, file name mysql-bin.000009
130817 21:05:59 InnoDB: Waiting for the background threads to start
130817 21:05:59 InnoDB: Warning: table ‘bw/Pages’
InnoDB: in InnoDB data dictionary has unknown flags 10.
130817 21:05:59 InnoDB: Warning: table ‘bw/FileSearchIndexAttributes’
InnoDB: in InnoDB data dictionary has unknown flags 10.
130817 21:05:59 InnoDB: Warning: table ‘bw/CollectionVersionBlocks’
InnoDB: in InnoDB data dictionary has unknown flags 10.
130817 21:05:59 InnoDB: Warning: table ‘bw/PageWorkflowProgress’
InnoDB: in InnoDB data dictionary has unknown flags 10.
130817 21:05:59 InnoDB: Warning: table ‘bw/CollectionSearchIndexAttributes’
InnoDB: in InnoDB data dictionary has unknown flags 10.

#2

I guess that any of the files provided by an RPM ca be overwritten when a security update or newer version is installed over the old one. This with the exception of what are clearly configuration files (IMHO they must be created with a default configuration on first install and from then on left untouched). I don’t think that /etc/init.d (if that is what you mean by /etc/init**/**d) files come into the category of configuration files.