From: "Francesco R." <vivo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] mysql update questions
Date: Sat, 19 Nov 2005 06:52:16 +0100 [thread overview]
Message-ID: <200511190652.16081.vivo@gentoo.org> (raw)
In-Reply-To: <5bdc1c8b0511181622p14077fc3i1bb2cc2799832968@mail.gmail.com>
Alle 01:22, sabato 19 novembre 2005, Mark Knecht el ga butta:
> |Hi,
> | What are my options? This mysql thing has been hanging out for a
> |long time. I was scared off by two things:
> |
> |1) I run MythTV which uses mysql. I have a database on my server
> | (this machine) that I'm worried about losing or messing up.
Backup as described in
"http://www.gentoo.org/doc/en/mysql-upgrading.xml"
replace "revdep-rebuild" with
"revdep-rebuild --soname=libmysqlclient.so.12"
grep the ebuild for "einfo" or follow them during emerge
> |
> |2) I *think* that if I update this server then I have to update all
> | of my MythTV frontend boxes also as I've heard that Myth required
> | both the frontend and the backend to run the same versions.
Maybe the following options (put them in my.cnf of the server) help
#Use old password encryption method (needed for 4.0 and
#older clients).
old-passwords
#Disallow authentication for accounts that have old
# (pre-4.1) passwords.
secure-auth
Don't switch collation and charachter set to utf8
http://forums.gentoo.org/viewtopic-t-399371-highlight-mysql.html
> |
> | Does anyone have direct experience with this? I'm sort of worried
> |about creating problems that take days (or longer) to fix.
> |
Sorry not me
[...]
A bit too short answer but it's very late in the morning here ...
good night
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-19 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-19 0:22 [gentoo-user] mysql update questions Mark Knecht
2005-11-19 5:52 ` Francesco R. [this message]
2005-11-21 18:28 ` James Ausmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200511190652.16081.vivo@gentoo.org \
--to=vivo@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox