Groups | Search | Server Info | Keyboard shortcuts | Login | Register


Groups > comp.databases.mysql > #7632

Re: Cannot remove MySQL completely

From pinnerite <pinnerite@gmail.com>
Newsgroups comp.databases.mysql
Subject Re: Cannot remove MySQL completely
Date 2022-01-18 12:48 +0000
Organization A noiseless patient Spider
Message-ID <20220118124859.8f1c20b86f5722837b1a9d5f@gmail.com> (permalink)
References <20220117114805.c031fa47fced17cde62197b8@gmail.com> <4789f309-afb4-6231-cadc-2d1a524eee3a@gmx.de> <20220117165750.f8dc48ba66e8fc7513db85f0@gmail.com> <340e9e53-3beb-1f86-531c-27904f871ed1@gmx.de>

Show all headers | View raw


On Tue, 18 Jan 2022 10:44:47 +0100
Axel Schwenke <axel.schwenke@gmx.de> wrote:

> On 17.01.2022 17:57, pinnerite wrote:
> > At the moment I can only get int MySQL from a root prompt. 
> > Otherwise it asks for the root password which I have not set(?).
> 
> This is on purpose. Again: RTFM!
> 
> Read also the Debian README. Package maintainers often add extra $FOO to
> packages. In the past Debian used to ask for a password for account name
> 'root' (which is traditionally the Superuser account). Now this is no longer
> neccessary because socket authentication helps with identification of users.
> 
> Normally the first thing you do is create an account for yourself. If you
> are connecting remotely (that means: the client is not running on the same
> machines than the server) it includes setting a password.
> 
> And if you are running an application using the database (i.e. MythTV) then
> it's highly recommended to create a MySQL account that is restricted to the
> tables for that application.
> 
> 
> XL

I appreciate you taking the trouble to reply in detail but you must understand thast I am not a regular user of MySQL and have only ever used it when employing MythTV.

This means that I only have to engage with it once every two or three years. 
Although I have textbooks on the subject, they are all obsolete because of the changes that are made between versions. 

Changing distros can even mean having to deploy MariaDB, which I did for a few years. 

Although I try to resolve my problems without recourse to bothering others, there comes a point when frustration takes over. I had reached that point.

If i had known where the database was held (/var/lib/mysql) earlier, I might have saved myself and others some trouble.

I always record the process of overcoming problems and the related advice in the hope of not making the same mistake more than once but sadly, the ground shifts. It is never exactly the same.

Thanks again,  Alan

-- 
Mint 20.3, kernel 5.4.0-95-generic, Cinnamon 5.2.7
running on an AMD Phenom II X4 Black edition processor with 16GB of DRAM.

Back to comp.databases.mysql | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Cannot remove MySQL completely pinnerite <pinnerite@gmail.com> - 2022-01-17 11:48 +0000
  Re: Cannot remove MySQL completely Bit Twister <BitTwister@mouse-potato.com> - 2022-01-17 06:26 -0600
    Re: Cannot remove MySQL completely The Natural Philosopher <tnp@invalid.invalid> - 2022-01-17 13:22 +0000
  Re: Cannot remove MySQL completely Axel Schwenke <axel.schwenke@gmx.de> - 2022-01-17 15:03 +0100
    Re: Cannot remove MySQL completely pinnerite <pinnerite@gmail.com> - 2022-01-17 16:57 +0000
      Re: Cannot remove MySQL completely Axel Schwenke <axel.schwenke@gmx.de> - 2022-01-18 10:44 +0100
        Re: Cannot remove MySQL completely pinnerite <pinnerite@gmail.com> - 2022-01-18 12:48 +0000
          Re: Cannot remove MySQL completely Axel Schwenke <axel.schwenke@gmx.de> - 2022-01-18 15:26 +0100
            Re: Cannot remove MySQL completely pinnerite <pinnerite@gmail.com> - 2022-01-18 16:40 +0000
              Re: Cannot remove MySQL completely Axel Schwenke <axel.schwenke@gmx.de> - 2022-01-19 17:43 +0100
                Re: Cannot remove MySQL completely pinnerite <pinnerite@gmail.com> - 2022-01-20 12:44 +0000
                Re: Cannot remove MySQL completely Axel Schwenke <axel.schwenke@gmx.de> - 2022-01-20 16:50 +0100
          Re: Cannot remove MySQL completely Jerry Stuckle <jstucklex@attglobal.net> - 2022-01-18 15:49 -0500
            Re: Cannot remove MySQL completely Dr Eberhard Lisse <nospam@lisse.NA> - 2022-01-19 12:29 +0200
              Re: Cannot remove MySQL completely Jerry Stuckle <jstucklex@attglobal.net> - 2022-01-19 17:15 -0500
                Re: Cannot remove MySQL completely Dr Eberhard Lisse <nospam@lisse.NA> - 2022-01-20 15:30 +0200
                Re: Cannot remove MySQL completely Jerry Stuckle <jstucklex@attglobal.net> - 2022-01-20 13:06 -0500

csiph-web