LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 04-14-2014, 01:40 AM   #1
kikinovak
Senior Member
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, Slackware64
Posts: 1,960

Rep: Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976
Setting up MySQL/MariaDB under Slackware 14.1


Hi,

All my servers are running Slackware 14.0 (or 13.37) for now. I'm considering migrating them to Slackware 14.1. I know MySQL has been replaced by MariaDB, which is supposed to be compatible. But as far as I can tell, the initialization routine has changed.

Here's my documentation for MySQL under 14.0:

http://www.microlinux.fr/slackware/L...ySQL-HOWTO.txt

This doesn't seem to work anymore. Anybody knows where I can find a reliable quick-and-dirty (or thorough-the-hard-way) HOWTO to setup MariaDB under Slackware 14.1 ?

Cheers,

Niki
 
Old 04-14-2014, 01:48 AM   #2
kikinovak
Senior Member
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, Slackware64
Posts: 1,960

Original Poster
Rep: Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976
OK, here's what I could figure out for now.

1. All the my-small.cnf, my-medium.cnf, ... files in /etc/mysql have gone. Apparently there's no replacement for these. Correct me if I'm wrong.

2. Everything else seems to work as before.

3. When I log in to the database monitor using mysql -u root -p, I get the following console:

Code:
MariaDB [(none)]>
If I understand this right, MariaDB shows me the currently selected database.

4. Any other surprises to be expected?
 
1 members found this post helpful.
Old 04-14-2014, 03:15 AM   #3
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,390

Rep: Reputation: Disabled
Note that there will now be a "/etc/my.cnf" file which includes all the configuration files in a directory "/etc/my.cnf.d/" which contains different server- and client-focused configurations (by default, they are empty as far as I know).

Eric
 
1 members found this post helpful.
Old 04-15-2014, 03:49 AM   #4
ppr:kut
Slackware Contributor
 
Registered: Aug 2006
Location: Netherlands
Distribution: Slackware
Posts: 369

Rep: Reputation: 98
Quote:
Originally Posted by kikinovak View Post
3. When I log in to the database monitor using mysql -u root -p, I get the following console:

Code:
MariaDB [(none)]>
If I understand this right, MariaDB shows me the currently selected database.
That's just the prompt, which is pretty much as configurable as your shell prompt. MariaDB just changed the default to, as you correctly stated, show the name of the database you are currently using.
 
Old 04-15-2014, 04:44 AM   #5
ppr:kut
Slackware Contributor
 
Registered: Aug 2006
Location: Netherlands
Distribution: Slackware
Posts: 369

Rep: Reputation: 98
Most of the incompatibilities should be listed at https://mariadb.com/kb/en/mariadb-ve...compatibility/.
New features only available in MariaDB are listed at https://mariadb.com/kb/en/mariadb-ve...ysql-features/

Note that the configuration file changes are just structural. Nothing prevents you from copying your old my.cnf file over and completely ignoring /etc/my.cnf.d.
 
Old 04-15-2014, 07:59 AM   #6
piacentini
LQ Newbie
 
Registered: May 2013
Posts: 12

Rep: Reputation: Disabled
My experience here with several php-based applications is that the switch is really transparent. All tools and scripts continue to work as they did with MySQL 5.5. YMMV, of course, but I would not expect problems.
 
Old 04-15-2014, 09:06 AM   #7
tronayne
Senior Member
 
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,121

Rep: Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819
When I installed 14.1, there were no problems with existing MySQL data bases (or LAMP applications), everything "just works." I was busy with other stuff and didn't even look at the .cnf files. Did have to fiddle with HTTP (a little, it changed) but, so far, no problems.

Hm; maybe I've got to get on the stick and see if I can break something, eh?
 
Old 10-17-2014, 03:25 AM   #8
rdx
Member
 
Registered: Apr 2007
Location: Dallas
Distribution: Slackware 11, 14.1 :: Slackware64 14.1
Posts: 127

Rep: Reputation: 22
Setting up users under MariaDB on Slackware64 14.1

I am trying to move a DB I have running on an old computer to my new one. The old computer is running Slackware 11 and mySQL. My new computer runs Slackware64 and MariaDB. The database itself is up and running and I can log into it as root. Now I want to add users. I have some cheat sheets which I pulled out and I tried to use them. But the DB responds that I have the wrong number of columns. Clearly I need to update my cheat sheets. Can someone point me in the right directions?
 
Old 10-17-2014, 06:53 AM   #9
tronayne
Senior Member
 
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,121

Rep: Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819
Perhaps it would be useful to start at the beginning? The documentation is found at https://mariadb.com/kb/en/mariadb/do...tting-started/ with links to chapters (look down the right-hand side for User Account Management).

Hope this helps some.

Last edited by tronayne; 10-17-2014 at 06:57 AM.
 
Old 10-19-2014, 07:03 AM   #10
rdx
Member
 
Registered: Apr 2007
Location: Dallas
Distribution: Slackware 11, 14.1 :: Slackware64 14.1
Posts: 127

Rep: Reputation: 22
I did look there but ...

Of course I did try to find the answer before I posted the question here and that was one of the places I looked. The old mySQL manuals had detailed instructions and I suspect the new ones do too, if I can find the right place. Anyway I D/Ld the "refman" file and I intend to go through it soon. I'll let you know if I find what I seek. Thanks.
 
Old 10-19-2014, 08:43 AM   #11
ppr:kut
Slackware Contributor
 
Registered: Aug 2006
Location: Netherlands
Distribution: Slackware
Posts: 369

Rep: Reputation: 98
Just to be sure, you did run mysql_upgrade on the old database before trying to create users, right?
 
Old 10-19-2014, 09:01 AM   #12
tronayne
Senior Member
 
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,121

Rep: Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819
Let's see what we can do here.

Here's the SQL I use to create a data base named gnis. This particular data base gets dropped and recreated every so often (which is why the commented-out drop line is there) and grants permissions to the administrator (a user named "gnis" with a password "gnispassword") and grants permissions to a user (named "UserName" here -- you would change that to the actual name of a user -- and a password "PassWord" -- you would change that to an actual password).
Code:
#       drop    database if exists gnis;

create  database if not exists gnis;

grant   select, insert,
        update, delete, index, alter, create, lock tables,
        create temporary tables, drop, references on gnis.*
to      gnis@localhost identified by 'gnispassword';

grant   select, insert,
        update, delete, index, alter, create, lock tables,
        create temporary tables, drop, references on gnis.*
to      UserName@localhost identified by 'PassWord';

grant   select, insert,
        update, delete, index, alter, create, lock tables,
        create temporary tables, drop, references on gnis.*
to      gnis@'%' identified by 'gnispassword';

grant   select, insert,
        update, delete, index, alter, create, lock tables,
        create temporary tables, drop, references on gnis.*
to      UserName@'%' identified by 'PassWord';

flush   privileges;
then each data base schema is added the same way (I keep data base schema files that contain only the schema, index statements and the like) and I would typically load data from individual files (some are pretty big, multiple gigabyte, some are small). I prefer doing things that way, your methods will most likely be yours and not mine.

Anyway, that's pretty much what you do to create users and grant permissions.

Hope this helps some.
 
2 members found this post helpful.
  


Reply

Tags
mariadb, mysql


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Keep using MySQL instead of MariaDB kelaskakap Slackware 17 12-13-2013 07:43 PM
MariaDB/MySQL uses too much RAM martvefun Linux - Server 3 06-23-2013 09:50 AM
[SOLVED] New MariaDB as replacement for Mysql vdemuth Slackware 10 03-31-2013 10:05 AM
Replace MySQL with MariaDB in Slackware abesirovic1 Slackware 36 03-28-2013 09:53 AM
[SOLVED] Slackware: Replace MySQL with MariaDB on fresh installation. astanton Slackware 4 03-03-2012 03:37 AM


All times are GMT -5. The time now is 01:00 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration