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. On some platforms, this may be done for you as part
99 of their installation procedure. (See below for your platform). In any case
102 >be sure to backup your old configuration if it is valuable to
105 HREF="upgradersnote.html"
114 NAME="INSTALLATION-PACKAGES"
115 >2.1. Binary Packages</A
118 >How to install the binary packages depends on your operating system:</P
124 NAME="INSTALLATION-PACK-RPM"
125 >2.1.1. Red Hat, SuSE and Conectiva RPMs</A
128 > RPMs can be installed with <TT
130 >rpm -Uvh privoxy-2.9.15-1.rpm</TT
136 of configuration files.</P
138 > Note that on Red Hat, <SPAN
145 > be automatically started on system boot. You will
146 need to enable that using <B
153 >, or similar methods. Note that SuSE will
154 automatically start Privoxy in the boot process.</P
156 > If you have problems with failed dependencies, try rebuilding the SRC RPM:
159 >rpm --rebuild privoxy-2.9.15-1.src.rpm</TT
161 will use your locally installed libraries and RPM version. </P
163 > Also note that if you have a <SPAN
167 on your system, you need to remove it first, because the packages conflict.
168 Otherwise, RPM will try to remove <SPAN
172 automatically, before installing <SPAN
182 NAME="INSTALLATION-DEB"
193 NAME="INSTALLATION-PACK-WIN"
197 > Just double-click the installer, which will guide you through
198 the installation process. You will find the configuration files
199 in the same directory as you installed Privoxy in. We do not
200 use the registry of Windows. </P
207 NAME="INSTALLATION-PACK-BINTGZ"
208 >2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</A
211 > Create a new directory, <TT
214 > to it, then unzip and
215 untar the archive. For the most part, you'll have to figure out where
223 NAME="INSTALLATION-OS2"
227 > First, make sure that no previous installations of
236 system. You can do this by </P
238 > Then, just double-click the WarpIN self-installing archive, which will
239 guide you through the installation process. A shadow of the
243 > executable will be placed in your
244 startup folder so it will start automatically whenever OS/2 starts.</P
246 > The directory you choose to install <SPAN
250 into will contain all of the configuration files.</P
257 NAME="INSTALLATION-MAC"
261 > Unzip the downloaded package (you can either double-click on the file
262 in the finder, or on the desktop if you downloaded it there). Then,
263 double-click on the package installer icon and follow the installation
268 > will be installed in the subdirectory
271 >/Applications/Privoxy.app</TT
276 > will set itself up to start
277 automatically on system bring-up via
280 >/System/Library/StartupItems/Privoxy</TT
288 NAME="INSTALLATION-AMIGA"
292 > Copy and then unpack the <TT
295 > archive to a suitable location.
296 All necessary files will be installed into <SPAN
300 directory, including all configuration and log files. To uninstall, just
301 remove this directory.</P
306 > (with RUN <>NIL:) in your
310 > script (AmiTCP), in
314 > (RoadShow), as startup program in your
315 startup script (Genesis), or as startup action (Miami and MiamiDx).
319 > will automatically quit when you quit your
320 TCP/IP stack (just ignore the harmless warning your TCP/IP stack may display that
324 > is still running).</P
332 NAME="INSTALLATION-SOURCE"
333 >2.2. Building from Source</A
336 > The most convenient way to obtain the <SPAN
340 is to download the source tarball from our <A
341 HREF="http://sf.net/projects/ijbswa/"
347 > If you like to live on the bleeding edge and are not afraid of using
348 possibly unstable development versions, you can check out the up-to-the-minute
349 version directly from <A
350 HREF="http://sourceforge.net/cvs/?group_id=11118"
354 > or simply download <A
355 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
366 HREF="http://www.gnu.org/software/autoconf/autoconf.html"
371 HREF="http://www.gnu.org/software/make/make.html"
375 >, and, of course, a C compiler like <A
376 HREF="http://www.gnu.org/software/gcc/gcc.html"
381 > When building from a source tarball (either release version or
383 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
387 >), first unpack the source: </P
397 > tar xzvf privoxy-2.9.15-beta-src* [.tgz or .tar.gz]
398 cd privoxy-2.9.15-beta</PRE
404 > For retrieving the current CVS sources, you'll need CVS installed.
405 Note that sources from CVS are development quality, and may not be
406 stable, or well tested. To download CVS source:</P
416 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
417 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
424 > This will create a directory named <TT
428 contain the source tree.</P
430 > Then, in either case, to build from unpacked tarball or CVS source:</P
442 ./configure # (--help to see options)
443 make # (the make from gnu, gmake for *BSD)
445 make -n install # (to see where all the files will go)
446 make install # (to really install)</PRE
452 > If you have gnu make, you can have the first four steps
453 automatically done for you by just typing:</P
469 > in the freshly downloaded or unpacked source directory.</P
471 > For more detailed instructions on how to build Redhat and SuSE RPMs,
472 Windows self-extracting installers, building on platforms with
473 special requirements etc, please consult the <A
474 HREF="../developer-manual/newrelease.html"
495 HREF="introduction.html"
511 HREF="upgradersnote.html"
530 >Note to Upgraders</TD