7 CONTENT="Modular DocBook HTML Stylesheet Version 1.64
10 TITLE="Privoxy User Manual"
11 HREF="index.html"><LINK
14 HREF="introduction.html"><LINK
16 TITLE="Note to Upgraders"
17 HREF="upgradersnote.html"><LINK
20 HREF="../p_doc.css"></HEAD
39 >Privoxy User Manual</TH
47 HREF="introduction.html"
60 HREF="upgradersnote.html"
80 > is available both in convenient pre-compiled
81 packages for a wide range of operating systems, and as raw source code.
82 For most users, we recommend using the packages, which can be downloaded from our
84 HREF="http://sourceforge.net/projects/ijbswa/"
90 > Note: If you have a previous <SPAN
97 > installation on your system, you
98 will need to remove it. Some platforms do this for you as part
99 of their installation procedure. (See below for your platform).
102 >be sure to backup your old configuration
103 if it is valuable to you.</I
106 HREF="upgradersnote.html"
107 >note to upgraders</A
115 NAME="INSTALLATION-PACKAGES"
116 >2.1. Binary Packages</A
119 >How to install the binary packages depends on your operating system:</P
125 NAME="INSTALLATION-PACK-RPM"
126 >2.1.1. Red Hat and SuSE RPMs</A
129 > RPMs can be installed with <TT
131 >rpm -Uvh privoxy-2.9.15-1.rpm</TT
137 of configuration files.</P
139 > Note that on Red Hat, <SPAN
146 > be automatically started on system boot. You will
147 need to enable that using <B
154 >, or similar methods. Note that SuSE will
155 automatically start Privoxy in the boot process.</P
157 > If you have problems with failed dependencies, try rebuilding the SRC RPM:
160 >rpm --rebuild privoxy-2.9.15-1.src.rpm;</TT
162 will use your locally installed libraries and RPM version. </P
164 > Also note that if you have a <SPAN
168 on your system, you need to remove it first, because the packages conflict.
169 Otherwise, RPM will try to remove <SPAN
173 automatically, before installing <SPAN
183 NAME="INSTALLATION-DEB"
194 NAME="INSTALLATION-PACK-WIN"
198 > Just double-click the installer, which will guide you through
199 the installation process. You will find the configuration files
200 in the same directory as you installed Privoxy in. We do not
201 use the registry of Windows. </P
208 NAME="INSTALLATION-PACK-BINTGZ"
209 >2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</A
212 > Create a new directory, <TT
215 > to it, then unzip and
216 untar the archive. For the most part, you'll have to figure out where
224 NAME="INSTALLATION-OS2"
228 > First, make sure that no previous installations of
237 system. You can do this by </P
239 > Then, just double-click the WarpIN self-installing archive, which will
240 guide you through the installation process. A shadow of the
244 > executable will be placed in your
245 startup folder so it will start automatically whenever OS/2 starts.</P
247 > The directory you choose to install <SPAN
251 into will contain all of the configuration files.</P
258 NAME="INSTALLATION-MAC"
262 > Unzip the downloaded package (you can either double-click on the file
263 in the finder, or on the desktop if you downloaded it there). Then,
264 double-click on the package installer icon and follow the installation
269 > will be installed in the subdirectory
272 >/Applications/Privoxy.app</TT
277 > will set itself up to start
278 automatically on system bring-up via
281 >/System/Library/StartupItems/Privoxy</TT
289 NAME="INSTALLATION-AMIGA"
293 > Copy and then unpack the <TT
296 > archive to a suitable location.
297 All necessary files will be installed into <SPAN
301 directory, including all configuration and log files. To uninstall, just
302 remove this directory.</P
307 > (with RUN <>NIL:) in your
311 > script (AmiTCP), in
315 > (RoadShow), as startup program in your
316 startup script (Genesis), or as startup action (Miami and MiamiDx).
320 > will automatically quit when you quit your
321 TCP/IP stack (just ignore the harmless warning your TCP/IP stack may display that
325 > is still running).</P
333 NAME="INSTALLATION-SOURCE"
334 >2.2. Building from Source</A
337 > The most convenient way to obtain the <SPAN
341 is to download the source tarball from our <A
342 HREF="http://sf.net/projects/ijbswa/"
348 > If you like to live on the bleeding edge and are not afraid of using
349 possibly unstable development versions, you can check out the up-to-the-minute
350 version directly from <A
351 HREF="http://sourceforge.net/cvs/?group_id=11118"
355 > or simply download <A
356 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
367 HREF="http://www.gnu.org/software/autoconf/autoconf.html"
372 HREF="http://www.gnu.org/software/make/make.html"
376 >, and, of course, a C compiler like <A
377 HREF="http://www.gnu.org/software/gcc/gcc.html"
382 > When building from a source tarball (either release version or
384 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
388 >), first unpack the source: </P
398 > tar xzvf privoxy-2.9.15-beta-src* [.tgz or .tar.gz]
399 cd privoxy-2.9.15-beta</PRE
405 > For retrieving the current CVS sources, you'll need CVS installed.
406 Note that sources from CVS are development quality, and may not be
407 stable, or well tested. To download CVS source:</P
417 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
418 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
425 > This will create a directory named <TT
429 contain the source tree.</P
431 > Then, in either case, to build from unpacked tarball or CVS source:</P
443 ./configure # (--help to see options)
444 make # (the make from gnu, gmake for *BSD)
446 make -n install # (to see where all the files will go)
447 make install # (to really install)</PRE
453 > If you have gnu make, you can have the first four steps
454 automatically done for you by just typing:</P
470 > in the freshly downloaded or unpacked source directory.</P
472 > For more detailed instructions on how to build Redhat and SuSE RPMs,
473 Windows self-extracting installers, building on platforms with
474 special requirements etc, please consult the <A
475 HREF="../developer-manual/newrelease.html"
496 HREF="introduction.html"
512 HREF="upgradersnote.html"
531 >Note to Upgraders</TD