Actually, it kind of does, but heres the dirty little secret behind it.
I generally build my own stuff, then create a package based off of what
I built. Whether it be on solaris or linux (for which I choose slack).
Then I use those packages for replication, but...they're still packages
I made so I still maintain control. Before I got into making my own
packages, I would use a set of scripts to build things with little or no
interaction from me, I'd just go grab the latest of whatever, pull up my
script for it, set a couple of vars and fire it off.
My point being that building your own stuff is easily scaleable, used to
do it for a 20 solaris box environment, which isn't the biggest, but I
wouldn't call it small.
I think we all have our own styles of admin, that's just mine.
Matt Alexander wrote:
| On Tue, 6 Jul 2004, Jonathan Furrer wrote:
|
|
|>I build things by hand, that way I know where they go, exactly what
|>libraries they were compiled with and I can update things before someone
|>else releases a package for it. That way when I hear that Openssl has
|>another vulnerability, I know whether or not my mysql build is affected
|>by it, etc..Those things are very important to me on a production system.
|>
|>I'm not knocking people who use packages on a production system, just
|>providing my veiw on it.
|
|
| That sounds fine for very small sites, but I don't think it scales well...
|
|
|
| ---------------------------------------------------
| PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
| To subscribe, unsubscribe, or to change you mail settings:
| http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)