Could someone give me a short course on why it is one executes these steps:
./configure as root
makeas a user
make installas root
I'm confused...
Howard
--
--
You received this message because you are subscribed to the Google Groups
NLUG group.
To post to this
The only one I would do as root would be the make install.
On Fri, May 16, 2014 at 10:07 AM, Howard White hwh...@vcch.com wrote:
Could someone give me a short course on why it is one executes these steps:
./configure as root
makeas a user
make installas root
On Fri, May 16, 2014 at 10:07 AM, Howard White hwh...@vcch.com wrote:
Could someone give me a short course on why it is one executes these steps:
./configure as root
makeas a user
make installas root
From what I understand, configure is a cross platform tool. It creates
On Fri, May 16, 2014 at 10:07 AM, Howard White hwh...@vcch.com wrote:
Could someone give me a short course on why it is one executes these steps:
./configure as root
makeas a user
make installas root
I'm confused...
Howard
You don't necessarily need to run
On 05/16/2014 11:30 AM, Tilghman Lesher wrote:
You don't necessarily need to run configure as root, but there are
some tests, especially for daemons which start as root, which need the
additional privileges to execute. For example, in Asterisk, I've
written a test to check whether one may
On May 16, 2014, at 11:29 AM, Kent Perrier kent.perr...@gmail.com wrote:
The only one I would do as root would be the make install.
We have a winner.
The only exception is if the env isn't configured correctly and root has the
dependencies the project needs
On Fri, May 16, 2014 at
On Fri, May 16, 2014 at 1:54 PM, Will Drewry w...@gmail.com wrote:
(diverging slightly)
On Fri, May 16, 2014 at 11:30 AM, Tilghman Lesher tilgh...@meg.abyt.es
wrote:
On Fri, May 16, 2014 at 10:07 AM, Howard White hwh...@vcch.com wrote:
Could someone give me a short course on why it is one
However, many environments include limitations enforced via resource
limits [ulimit(3)/*rlimits] for an interactive user process tree.
Bash (and pretty much every shell) can help check those with a simple:
ulimit -nS # soft limit
1024
ulimit -nH # hard limit
4096
What
On Fri, May 16, 2014 at 3:19 PM, Tilghman Lesher tilgh...@meg.abyt.es wrote:
On Fri, May 16, 2014 at 1:54 PM, Will Drewry w...@gmail.com wrote:
(diverging slightly)
On Fri, May 16, 2014 at 11:30 AM, Tilghman Lesher tilgh...@meg.abyt.es
wrote:
On Fri, May 16, 2014 at 10:07 AM, Howard White
This would presumably be because the permissions on the configuration file and
the eventual binary location are more restrictive, since they potentially
affect everyone who uses the program, but a local build directory only affects
the user doing the compiling.
On May 16, 2014 10:07:42 AM
10 matches
Mail list logo