<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Craig White wrote:
<blockquote
cite="mid:1231865487.32737.2435.camel@lin-workstation.azapple.com"
type="cite">
<pre wrap="">On Tue, 2009-01-13 at 11:46 -0500, John Dennis wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Brian Ertel wrote:
</pre>
<blockquote type="cite">
<pre wrap="">John,
You are right, but the dir where the old radius was "make installed" is
gone. That is the original folder that was created after unzipping and
installing the old ver. Of radius is gone. Is there anything else I can do?
</pre>
</blockquote>
<pre wrap="">You can recreate the tree, follow the same steps you did the first time
which was probably something like this:
% tar xf freeradius-server.tar
% cd freeradius-server
% ./configure #passing the exact same parameters you used the first time
% make
Now instead of "make install" run make "make uninstall"
Then you can delete the source tree.
BTW, all this is basic Linux/Unix administration, the freeradius-users
list is not an appropriate place to learn these topics.
</pre>
</blockquote>
<pre wrap=""><!---->----
seems to me that it attempts to load the files he installed from tarball
that are in /usr/local/[bin|sbin] and that is what he needs to clean out
before he ever attempts to use anything installed from rpm
</pre>
</blockquote>
Exactly. FWIW the paths are embedded as a consequence of parameters
passed to configure. When you build from an SRPM the spec file passes
different parameters to configure than the default configure
parameters, thus the two installs will not likely conflict, but it's
possible. Therefore the best course of action, to assure there are no
conflicts and to reduce the inevitable confusion of having multiple
copies installed in various locations is to remove the first
installation and then do an RPM install.<br>
<br>
An install copies many files into a variety of locations, the only way
to assure you've removed all the files to use the same code to
uninstall as was used to perform the install in the first place.<br>
<br>
BTW, this is one reason why using the package manager on the target
system (e.g. rpm, apt, dpkg, etc.) is always preferred because they
know how to install and uninstall and keep a system consistent. When
you go behind the back of these package managers by installing things
manually (e.g. make install) you run the risk of screwing your system
up unless you have advanced skills and know exactly what you're doing.<br>
<pre class="moz-signature" cols="72">--
John Dennis <a class="moz-txt-link-rfc2396E" href="mailto:jdennis@redhat.com"><jdennis@redhat.com></a>
</pre>
</body>
</html>