Ignoring issues of familiarity---which can't be ignored, really, but
you're the only one who can judge them---I think the only issue is
that stable needs to _already have what you're going to need_, because
that's what you're going to have to work with for the next two years.
Micheal,
Ah, now that was good to know. I'll need to review the requirements for
cpanel's software since that's the reason for trying to run Debian on
Sparc, but generally I'm aiming for a base layer of Apache2 with the
prefork_mpm, a custom compile of PHP5 (for oracle 10g connectivity) and
MySQL 4.1.x. The benefit I'm looking for from cpanel is making is to be
able to centralize my deployments (versions, updates) of phpmyadmin,
awstats and related tools than trying to manage all that by hand or in
some cobbled fashion.
Searching through the debian, packages list I see apache2 and mysql4.1
are there. I'll see I'll need to spend some more time comparing the
versions of other components I'll need to compile PHP5 with what
versions of those components debian stable provides, could you give me
an overview how you blend syncs with the "testing" package tree? Do you
run say 90% of the server from stable packages and only selectively
update certain software to testing packages? On a scale from mostly
harmless to nutball crazy what's the opinion of this package tree
mixing?
- SL
--
TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
