| 1 |
On Tue, Apr 1, 2008 at 4:48 PM, Johann Schmitz <johann@×××××××××.net> wrote: |
| 2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 3 |
> Hash: SHA1 |
| 4 |
> |
| 5 |
> Hi! |
| 6 |
> |
| 7 |
> About several month ago I got 2 mysql instances (4.xx and 5.xx) running on |
| 8 |
> the same machine. |
| 9 |
> |
| 10 |
> The (very) quick guide: |
| 11 |
> |
| 12 |
> * Emerge, setup, etc mysql in the outer system |
| 13 |
> * setup a chroot with an complete stage3 |
| 14 |
> * chroot into the new one |
| 15 |
> ** emerge mysql |
| 16 |
> ** setup mysql (use a different ip or at least a different port then the |
| 17 |
> outer system!) |
| 18 |
> ** Note: You have to uncomment the "need net" line in the mysql init |
| 19 |
> script, cause the network is already up |
| 20 |
> * Mount /usr/portage/, /dev/, /proc/ with bind in the chroot |
| 21 |
> * Create a fake initscript wich simply invokes the mysql initscript in the |
| 22 |
> chroot |
| 23 |
> ** Add this one to the default runlevel |
| 24 |
> |
| 25 |
> I wrote a step-by-step guide, but: Its in german ;) |
| 26 |
> Maybe i find some time to translate it into englisch... |
| 27 |
> |
| 28 |
> |
| 29 |
|
| 30 |
I don't understand why use a chroot to simply run another instance of |
| 31 |
MySQL. Is there any good reason? |
| 32 |
All you gotta do is create a new configuration file that points to a |
| 33 |
different database location and uses a different port, and clone and |
| 34 |
edit another /etc/init.d/mysql script to point to the new config file. |
| 35 |
|
| 36 |
A chroot would be just a waste of space, since you can use the same |
| 37 |
binary for multiple instances. |
| 38 |
-- |
| 39 |
gentoo-user@l.g.o mailing list |
Archives