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="Quickstart to Using Privoxy"
17 HREF="quickstart.html"><LINK
20 HREF="../p_doc.css"></HEAD
39 >Privoxy User Manual</TH
47 HREF="introduction.html"
60 HREF="quickstart.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/"
86 >Privoxy Project Page</A
89 > If you like to live on the bleeding edge and are not afraid of using
90 possibly unstable development versions, you can check out the up-to-the-minute
91 version directly from <A
92 HREF="http://sourceforge.net/cvs/?group_id=11118"
96 > or simply download <A
97 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
106 > is known to run on Win32, Mac
107 OSX, OS/2, AmigaOS, Linux (RedHat, Suse, Debian), FreeBSD, NetBSD, BeOS, and
108 many flavors of Unix.</P
114 NAME="INSTALLATION-PACKAGES"
115 >3.1. Binary Packages</A
118 > Note: If you have a previous <SPAN
125 > installation on your system, you
126 will need to remove it. Some platforms do this for you as part
127 of their installation procedure. (See below for your platform).</P
131 >be sure to backup your old configuration
132 if it is valuable to you.</I
135 HREF="quickstart.html#UPGRADERSNOTE"
136 >note to upgraders</A
139 > How to install the binary packages depends on your operating system:</P
145 NAME="INSTALLATION-PACK-RPM"
146 >3.1.1. Red Hat and SuSE RPMs</A
149 > RPMs can be installed with <TT
151 >rpm -Uvh privoxy-2.9.14-1.rpm</TT
157 of configuration files.</P
159 > Note that on Red Hat, <SPAN
163 automatically started on system boot. You will need to enable that using
170 >, or similar method.</P
172 > If you have problems with failed dependencies, try rebuilding the SRC RPM:
175 >rpm --rebuild privoxy-2.9.14-1.src.rpm;</TT
177 will use your locally installed libraries and RPM version. </P
179 > Also note that if you have a <SPAN
183 on your system, you need to remove it first, because the packages conflict.
184 Otherwise, RPM will try to remove <SPAN
188 automatically, before installing <SPAN
198 NAME="INSTALLATION-DEB"
209 NAME="INSTALLATION-PACK-WIN"
213 > Just double-click the installer, which will guide you through
214 the installation process.</P
221 NAME="INSTALLATION-PACK-BINTGZ"
222 >3.1.4. Solaris, NetBSD, FreeBSD, HP-UX</A
225 > Create a new directory, <TT
228 > to it, then unzip and
229 untar the archive. For the most part, you'll have to figure out where
237 NAME="INSTALLATION-OS2"
241 > First, make sure that no previous installations of
250 system. You can do this by </P
252 > Then, just double-click the WarpIN self-installing archive, which will
253 guide you through the installation process. A shadow of the
257 > executable will be placed in your
258 startup folder so it will start automatically whenever OS/2 starts.</P
260 > The directory you choose to install <SPAN
264 into will contain all of the configuration files.</P
271 NAME="INSTALLATION-MAC"
275 > Unzip the downloaded package (you can either double-click on the file
276 in the finder, or on the desktop if you downloaded it there). Then,
277 double-click on the package installer icon and follow the installation
282 > will be installed in the subdirectory
285 >/Applications/Privoxy.app</TT
290 > will set itself up to start
291 automatically on system bringup via
294 >/System/Library/StartupItems/Privoxy</TT
302 NAME="INSTALLATION-AMIGA"
306 > Copy and then unpack the <TT
309 > archive to a suitable location.
310 All necessary files will be installed into <SPAN
314 directory, including all configuration and log files. To uninstall, just
315 remove this directory.</P
320 > (with RUN <>NIL:) in your
324 > script (AmiTCP), in
328 > (RoadShow), as startup program in your
329 startup script (Genesis), or as startup action (Miami and MiamiDx).
333 > will automatically quit when you quit your
334 TCP/IP stack (just ignore the harmless warning your TCP/IP stack may display that
338 > is still running).</P
346 NAME="INSTALLATION-SOURCE"
347 >3.2. Building from Source</A
354 autoheader, autoconf, <A
355 HREF="http://www.gnu.org/software/make/make.html"
359 >, and, of course, a C compiler are required.</P
361 > When building from a source tarball (either release version or
362 nightly CVS tarball), first unpack the source: </P
372 > tar xzvf privoxy-2.9.14-beta-src* [.tgz or .tar.gz]
373 cd privoxy-2.9.14-beta
380 > For retrieving the current CVS sources, you'll need CVS installed.
381 Note that sources from CVS are development quality, and may not be
382 stable, or well tested. To download CVS source:</P
392 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
393 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
401 > This will create a directory named <TT
405 contain the source tree.</P
407 > Then, in either case, to build from unpacked tarball or CVS source:</P
419 ./configure # (--help to see options)
420 make # (the make from gnu, gmake for *BSD)
422 make -n install # (to see where all the files will go)
423 make install # (to really install)
430 > If you have gnu make, you can have the first four steps
431 automatically done for you by just typing</P
448 > in the freshly downloaded or unpacked source directory.</P
450 > For more detailed instructions on how to build Redhat and SuSE RPMs,
451 Windows self-extracting installers, building on platforms with
452 special requirements etc, please consult the <A
453 HREF="../developer-manual/newrelease.html"
474 HREF="introduction.html"
490 HREF="quickstart.html"
509 >Quickstart to Using <SPAN