From: Ferris McCormick <fmccor@gentoo.org>
To: Matthew Marlowe <mattm@gentoo.org>
Cc: wolf31o2@gentoo.org, gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Creating a dedicated gentoo profile for commercial mysql support
Date: Fri, 22 Apr 2005 22:52:12 +0000 (UTC) [thread overview]
Message-ID: <Pine.LNX.4.62.0504222246080.31970@terciopelo.krait.us> (raw)
In-Reply-To: <20050422221735.263CBF5944@mail.deploylinux.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 22 Apr 2005, Matthew Marlowe wrote:
> I dont know whether this should be a GLEP or just a simple email,
> but I'll start as an email....
>
> GENERAL BACKGROUND:
> --------------------------------------------
> Gentoo is being increasingly deployed in datacenter environments, especially
> in multilayered apache/tomcat/mysql configurations. Many clients in the 10-25
> box range have decided to switch their infrastructure entirely to gentoo due to
> satisfaction with gentoo's ease of configuration and overall lifetime flexibility with
> key applications (no need to reinstall/make a major upgrade of the OS - and
> no RPM hell).
>
> Recently, Mysql AB has released two new features/products: cluster support
> and mysql network (a commercial support offering). As a consultant, I have
> several clients looking to deploy both. However, the clients are worried that
> they are going to be forced to switch their DB layers to redhat to ensure stability
> and support. Mysql also participates in TSA Network such that any mysql server
> issues could be reported to them and multiple vendors including dell, redhat, and mysql
> would all work together to resolve problems. Dell has just launched a mysql support
> program at http://www.dell.com/mysql.
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Lots of stuff snipped
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I like the concept. In this particular case, it looks to me like everyone
comes out ahead, and as a test case, MySQL is better than anything else
that comes immediately to mind. (As you see from my signature, what you
are proposing doesn't affect me much, but I've used MySQL for a long time,
I like it, this supports them, and done right, gives everyone involved
some good publicity.)
Regards,
Ferris
- --
Ferris McCormick (P44646, MI) <fmccor@gentoo.org>
Developer, Gentoo Linux (sparc)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCaYAgQa6M3+I///cRAtlQAKDSLWr/C9XXWUa0X3k9Ow+hoG570gCguiqX
AURA4G9Bw9EwegmG8KlXJlU=
=DZBL
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-04-22 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 22:18 [gentoo-dev] Creating a dedicated gentoo profile for commercial mysql support Matthew Marlowe
2005-04-22 22:52 ` Ferris McCormick [this message]
2005-04-23 0:11 ` Francesco Riosa
2005-05-17 0:45 ` [gentoo-dev] Re: Creating a dedicated gentoo profile for commercial SW support Kurt Albershardt
2005-04-23 0:57 ` [gentoo-dev] Creating a dedicated gentoo profile for commercial mysql support Donnie Berkholz
2005-04-23 3:37 ` Georgi Georgiev
2005-04-23 3:54 ` Donnie Berkholz
2005-04-23 3:58 ` Georgi Georgiev
2005-04-23 6:15 ` Sebastian Bergmann
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=Pine.LNX.4.62.0504222246080.31970@terciopelo.krait.us \
--to=fmccor@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mattm@gentoo.org \
--cc=wolf31o2@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