7 CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
9 TITLE="Privoxy 2.9.20 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 2.9.20 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 and Conectiva RPMs</A
127 > RPMs can be installed with <TT
129 >rpm -Uvh privoxy-2.9.20-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.20-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"
185 > DEBs can be installed with <TT
188 privoxy_2.9.20-1.deb</TT
193 > for the location of configuration
201 NAME="INSTALLATION-PACK-WIN"
205 > Just double-click the installer, which will guide you through
206 the installation process. You will find the configuration files
207 in the same directory as you installed Privoxy in. We do not
208 use the registry of Windows. </P
215 NAME="INSTALLATION-PACK-BINTGZ"
216 >2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</A
219 > Create a new directory, <TT
222 > to it, then unzip and
223 untar the archive. For the most part, you'll have to figure out where
231 NAME="INSTALLATION-OS2"
235 > First, make sure that no previous installations of
244 system. Check that no <SPAN
252 your startup folder. </P
254 > Then, just double-click the WarpIN self-installing archive, which will
255 guide you through the installation process. A shadow of the
259 > executable will be placed in your
260 startup folder so it will start automatically whenever OS/2 starts.</P
262 > The directory you choose to install <SPAN
266 into will contain all of the configuration files.</P
273 NAME="INSTALLATION-MAC"
277 > Unzip the downloaded file (you can either double-click on the file
278 from the finder, or from the desktop if you downloaded it there).
279 Then, double-click on the package installer icon named
284 and follow the installation process.
288 > will be installed in the folder
291 >/Library/Privoxy</TT
293 It will start automatically whenever you start up. To prevent it from
294 starting automatically, remove or rename the folder
297 >/Library/StartupItems/Privoxy</TT
300 > To start Privoxy by hand, double-click on
303 >StartPrivoxy.command</TT
307 >/Library/Privoxy</TT
309 Or, type this command in the Terminal:</P
319 > /Library/Privoxy/StartPrivoxy.command
326 > You will be prompted for the administrator password.</P
333 NAME="INSTALLATION-AMIGA"
337 > Copy and then unpack the <TT
340 > archive to a suitable location.
341 All necessary files will be installed into <SPAN
345 directory, including all configuration and log files. To uninstall, just
346 remove this directory.</P
353 NAME="INSTALLATTION-GENTOO"
357 > Gentoo source packages (Ebuilds) for <SPAN
361 contained in the Gentoo Portage Tree (they are not on the download page,
362 but there is a Gentoo section, where you can see when a new
366 > Version is added to the Portage Tree).</P
368 > Before installing <SPAN
371 > under Gentoo just do
375 > to get the latest changes from the
376 Portage tree. With <TT
379 > you install the latest
382 > Configuration files are in <TT
386 documentation is in <TT
388 >/usr/share/doc/privoxy-2.9.20</TT
390 and the Log directory is in <TT
392 >/var/log/privoxy</TT
401 NAME="INSTALLATION-SOURCE"
402 >2.2. Building from Source</A
405 > The most convenient way to obtain the <SPAN
409 is to download the source tarball from our <A
410 HREF="http://sf.net/projects/ijbswa/"
416 > If you like to live on the bleeding edge and are not afraid of using
417 possibly unstable development versions, you can check out the up-to-the-minute
418 version directly from <A
419 HREF="http://sourceforge.net/cvs/?group_id=11118"
423 > or simply download <A
424 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
435 HREF="http://www.gnu.org/software/autoconf/autoconf.html"
440 HREF="http://www.gnu.org/software/make/make.html"
444 >, and, of course, a C compiler like <A
445 HREF="http://www.gnu.org/software/gcc/gcc.html"
450 > When building from a source tarball (either release version or
452 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
456 >), first unpack the source: </P
466 > tar xzvf privoxy-2.9.20-beta-src* [.tgz or .tar.gz]
467 cd privoxy-2.9.20-beta</PRE
473 > For retrieving the current CVS sources, you'll need CVS installed.
474 Note that sources from CVS are development quality, and may not be
475 stable, or well tested. To download CVS source:</P
485 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
486 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
493 > This will create a directory named <TT
497 contain the source tree.</P
499 > Then, in either case, to build from unpacked tarball or CVS source:</P
511 ./configure # (--help to see options)
512 make # (the make from gnu, gmake for *BSD)
514 make -n install # (to see where all the files will go)
515 make install # (to really install)</PRE
521 > If you have gnu make, you can have the first four steps
522 automatically done for you by just typing:</P
538 > in the freshly downloaded or unpacked source directory.</P
540 > For more detailed instructions on how to build Redhat and SuSE RPMs,
541 Windows self-extracting installers, building on platforms with
542 special requirements etc, please consult the <A
543 HREF="../developer-manual/newrelease.html"
553 NAME="INSTALLATION-KEEPUPDATED"
554 >2.3. Keeping your Installation Up-to-Date</A
557 > As user feedback comes in and development continues, we will make updated versions
559 HREF="actions-file.html"
562 HREF="http://sourceforge.net/project/showfiles.php?group_id=11118&release_id=103670"
566 >) and the software itself (including the actions file) available for
569 > If you wish to receive an email notification whenever we release updates of
573 > or the actions file, <A
574 HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/"
577 to our announce mailing list</A
578 >, ijbswa-announce@lists.sourceforge.net.</P
580 > In order not to loose your personal changes and adjustments when updating
592 customization of <SPAN
596 HREF="actions-file.html"
597 >Chapter on actions files</A
616 HREF="introduction.html"
632 HREF="upgradersnote.html"
651 >Note to Upgraders</TD