Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Oct 2012 11:10:59 +0400
From:      Peter Vereshagin <>
Subject:   Re: Famp Server
Message-ID:  <>
In-Reply-To: <k6mos3$36g$>
References:  <> <k6mos3$36g$>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

2012/10/29 16:28:11 -0400 Michael Powell <> => To :
MP> Perhaps by way of example I can illustrate: I run Apache as FastCGI with the 
MP> event-mpm, mysql, memcached, and PHP in the FPM configuration. It is a 
MP> highly customized and tuned environment which is easily obtained utilizing 
MP> the inherent configurability of the FreeBSD ports system. 

jfmi: Which of them can not be found in a 'gentoo'?

MP> When such a meta port comes into play, there are defaults chosen which begin 
MP> to reflect the same kind of restrictions as I outlined before in my reasons 
MP> for not migrating my chosen environment to Linux.

You can configure separately each port the metaport consists of and then build
that metaport. Those "defaults chosen from begin" do not depend on if the
'nested' port is being built as a part of a metaport build process or
separately thus no restrictions observed.

MP> I suggest, instead of 
MP> leaning on the meta port approach, that the true power of FreeBSD would be 
MP> more fully realized by learning to be a proper system admin. You will also 

What if being a proper sysadm means ability to deploy a package on thousands
(tens of thaousands, etc.) of machines? In formal terms this means create a
package and install on the every machine. This cannot be a several packages
because this makes the whole task less quick and the solution less reliable.
And the creation of such a package can be a more trivial task for sysadm than
the such of a package installation or upgrade by itself.

Such a metaport can be a person-scale/company-wide solution, not a public one
so no harm for the general freebsd usage approaches/pphilosophy which is a
kind of a public stuff.

Peter Vereshagin <> ( pgp: A0E26627 

Want to link to this message? Use this URL: <>