7 CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
9 TITLE="Privoxy User Manual"
10 HREF="index.html"><LINK
13 HREF="introduction.html"><LINK
15 TITLE="Note to Upgraders"
16 HREF="upgradersnote.html"><LINK
19 HREF="../p_doc.css"></HEAD
38 >Privoxy User Manual</TH
46 HREF="introduction.html"
59 HREF="upgradersnote.html"
79 > is available both in convenient pre-compiled
80 packages for a wide range of operating systems, and as raw source code.
81 For most users, we recommend using the packages, which can be downloaded from our
83 HREF="http://sourceforge.net/projects/ijbswa/"
89 > Note: If you have a previous <SPAN
96 > installation on your system, you
97 will need to remove it. On some platforms, this may be done for you as part
98 of their installation procedure. (See below for your platform). In any case
101 >be sure to backup your old configuration if it is valuable to
104 HREF="upgradersnote.html"
113 NAME="INSTALLATION-PACKAGES"
114 >2.1. Binary Packages</A
117 >How to install the binary packages depends on your operating system:</P
123 NAME="INSTALLATION-PACK-RPM"
124 >2.1.1. Red Hat, SuSE RPMs and Conectiva</A
127 > RPMs can be installed with <TT
129 >rpm -Uvh privoxy-2.9.15-1.rpm</TT
135 of configuration files.</P
137 > Note that on Red Hat, <SPAN
144 > be automatically started on system boot. You will
145 need to enable that using <B
152 >, or similar methods. Note that SuSE will
153 automatically start Privoxy in the boot process.</P
155 > If you have problems with failed dependencies, try rebuilding the SRC RPM:
158 >rpm --rebuild privoxy-2.9.15-1.src.rpm;</TT
160 will use your locally installed libraries and RPM version. </P
162 > Also note that if you have a <SPAN
166 on your system, you need to remove it first, because the packages conflict.
167 Otherwise, RPM will try to remove <SPAN
171 automatically, before installing <SPAN
181 NAME="INSTALLATION-DEB"
192 NAME="INSTALLATION-PACK-WIN"
196 > Just double-click the installer, which will guide you through
197 the installation process. You will find the configuration files
198 in the same directory as you installed Privoxy in. We do not
199 use the registry of Windows. </P
206 NAME="INSTALLATION-PACK-BINTGZ"
207 >2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</A
210 > Create a new directory, <TT
213 > to it, then unzip and
214 untar the archive. For the most part, you'll have to figure out where
222 NAME="INSTALLATION-OS2"
226 > First, make sure that no previous installations of
235 system. You can do this by </P
237 > Then, just double-click the WarpIN self-installing archive, which will
238 guide you through the installation process. A shadow of the
242 > executable will be placed in your
243 startup folder so it will start automatically whenever OS/2 starts.</P
245 > The directory you choose to install <SPAN
249 into will contain all of the configuration files.</P
256 NAME="INSTALLATION-MAC"
260 > Unzip the downloaded package (you can either double-click on the file
261 in the finder, or on the desktop if you downloaded it there). Then,
262 double-click on the package installer icon and follow the installation
267 > will be installed in the subdirectory
270 >/Applications/Privoxy.app</TT
275 > will set itself up to start
276 automatically on system bring-up via
279 >/System/Library/StartupItems/Privoxy</TT
287 NAME="INSTALLATION-AMIGA"
291 > Copy and then unpack the <TT
294 > archive to a suitable location.
295 All necessary files will be installed into <SPAN
299 directory, including all configuration and log files. To uninstall, just
300 remove this directory.</P
305 > (with RUN <>NIL:) in your
309 > script (AmiTCP), in
313 > (RoadShow), as startup program in your
314 startup script (Genesis), or as startup action (Miami and MiamiDx).
318 > will automatically quit when you quit your
319 TCP/IP stack (just ignore the harmless warning your TCP/IP stack may display that
323 > is still running).</P
331 NAME="INSTALLATION-SOURCE"
332 >2.2. Building from Source</A
335 > The most convenient way to obtain the <SPAN
339 is to download the source tarball from our <A
340 HREF="http://sf.net/projects/ijbswa/"
346 > If you like to live on the bleeding edge and are not afraid of using
347 possibly unstable development versions, you can check out the up-to-the-minute
348 version directly from <A
349 HREF="http://sourceforge.net/cvs/?group_id=11118"
353 > or simply download <A
354 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
365 HREF="http://www.gnu.org/software/autoconf/autoconf.html"
370 HREF="http://www.gnu.org/software/make/make.html"
374 >, and, of course, a C compiler like <A
375 HREF="http://www.gnu.org/software/gcc/gcc.html"
380 > When building from a source tarball (either release version or
382 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
386 >), first unpack the source: </P
396 > tar xzvf privoxy-2.9.15-beta-src* [.tgz or .tar.gz]
397 cd privoxy-2.9.15-beta</PRE
403 > For retrieving the current CVS sources, you'll need CVS installed.
404 Note that sources from CVS are development quality, and may not be
405 stable, or well tested. To download CVS source:</P
415 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
416 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
423 > This will create a directory named <TT
427 contain the source tree.</P
429 > Then, in either case, to build from unpacked tarball or CVS source:</P
441 ./configure # (--help to see options)
442 make # (the make from gnu, gmake for *BSD)
444 make -n install # (to see where all the files will go)
445 make install # (to really install)</PRE
451 > If you have gnu make, you can have the first four steps
452 automatically done for you by just typing:</P
468 > in the freshly downloaded or unpacked source directory.</P
470 > For more detailed instructions on how to build Redhat and SuSE RPMs,
471 Windows self-extracting installers, building on platforms with
472 special requirements etc, please consult the <A
473 HREF="../developer-manual/newrelease.html"
494 HREF="introduction.html"
510 HREF="upgradersnote.html"
529 >Note to Upgraders</TD