> $ perl Makefile.PL && make && make test && sudo make install
> # if each step is successful, it succeeds automagically,
> # otherwise it fails. also more importantly, it wraps
> # 'make install' in a sudo call, so the work gets logged
> # and you only get to do that one command as root. if
> # your system supports it, sudo is often safer than su.
sudo for a make is no safer than su, after all, any vaild shell command
(including creation and compilation of files) can be put in a makefile.
Also, people often say that it's not safe to untar and compile programs
as root. Well, unless they are *really* paranoic and check *every* file
in the tar, it just doesn't make sense (to me) to don't trust the
tar but trust the executable generated by the files in it...
It would make more sense to untar, compile, and execute the program
under the same uid, and just give it capabilities to bind to lower ports.
hugs
Luciano Rocha
--
Luciano Rocha, [EMAIL PROTECTED]
The trouble with computers is that they do what you tell them, not what
you want.
-- D. Cohen
