1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
10 TITLE="Privoxy 3.0.3 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
31 SUMMARY="Header navigation table"
40 >Privoxy 3.0.3 User Manual</TH
48 HREF="introduction.html"
62 HREF="upgradersnote.html"
83 > is available both in convenient pre-compiled
84 packages for a wide range of operating systems, and as raw source code.
85 For most users, we recommend using the packages, which can be downloaded from our
87 HREF="http://sourceforge.net/projects/ijbswa/"
93 > Note: If you have a previous <SPAN
100 > installation on your system, you
101 will need to remove it. On some platforms, this may be done for you as part
102 of their installation procedure. (See below for your platform). In any case
107 >be sure to backup your old configuration if it is valuable to
111 HREF="upgradersnote.html"
120 NAME="INSTALLATION-PACKAGES"
121 >2.1. Binary Packages</A
124 >How to install the binary packages depends on your operating system:</P
130 NAME="INSTALLATION-PACK-RPM"
131 >2.1.1. Red Hat, SuSE and Conectiva RPMs</A
134 > RPMs can be installed with <VAR
136 >rpm -Uvh privoxy-3.0.3-1.rpm</VAR
142 of configuration files.</P
144 > Note that on Red Hat, <SPAN
154 > be automatically started on system boot. You will
155 need to enable that using <B
162 >, or similar methods. Note that SuSE will
163 automatically start Privoxy in the boot process.</P
165 > If you have problems with failed dependencies, try rebuilding the SRC RPM:
168 >rpm --rebuild privoxy-3.0.3-1.src.rpm</VAR
170 will use your locally installed libraries and RPM version. </P
172 > Also note that if you have a <SPAN
176 on your system, you need to remove it first, because the packages conflict.
177 Otherwise, RPM will try to remove <SPAN
181 automatically, before installing <SPAN
191 NAME="INSTALLATION-DEB"
195 > DEBs can be installed with <VAR
197 >apt-get install privoxy</VAR
202 > for the location of
203 configuration files.</P
210 NAME="INSTALLATION-PACK-WIN"
214 > Just double-click the installer, which will guide you through
215 the installation process. You will find the configuration files
216 in the same directory as you installed Privoxy in. We do not
217 use the registry of Windows. </P
224 NAME="INSTALLATION-PACK-BINTGZ"
225 >2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</A
228 > Create a new directory, <VAR
231 > to it, then unzip and
232 untar the archive. For the most part, you'll have to figure out where
240 NAME="INSTALLATION-OS2"
244 > First, make sure that no previous installations of
253 system. Check that no <SPAN
261 your startup folder. </P
263 > Then, just double-click the WarpIN self-installing archive, which will
264 guide you through the installation process. A shadow of the
268 > executable will be placed in your
269 startup folder so it will start automatically whenever OS/2 starts.</P
271 > The directory you choose to install <SPAN
275 into will contain all of the configuration files.</P
282 NAME="INSTALLATION-MAC"
286 > Unzip the downloaded file (you can either double-click on the file
287 from the finder, or from the desktop if you downloaded it there).
288 Then, double-click on the package installer icon named
293 and follow the installation process.
297 > will be installed in the folder
300 >/Library/Privoxy</VAR
302 It will start automatically whenever you start up. To prevent it from
303 starting automatically, remove or rename the folder
306 >/Library/StartupItems/Privoxy</VAR
309 > To start Privoxy by hand, double-click on
312 >StartPrivoxy.command</VAR
316 >/Library/Privoxy</VAR
318 Or, type this command in the Terminal:</P
328 > /Library/Privoxy/StartPrivoxy.command
335 > You will be prompted for the administrator password.</P
342 NAME="INSTALLATION-AMIGA"
346 > Copy and then unpack the <TT
349 > archive to a suitable location.
350 All necessary files will be installed into <SPAN
354 directory, including all configuration and log files. To uninstall, just
355 remove this directory.</P
362 NAME="INSTALLATTION-GENTOO"
366 > Gentoo source packages (Ebuilds) for <SPAN
370 contained in the Gentoo Portage Tree (they are not on the download page,
371 but there is a Gentoo section, where you can see when a new
375 > Version is added to the Portage Tree).</P
377 > Before installing <SPAN
380 > under Gentoo just do
384 > to get the latest changes from the
385 Portage tree. With <VAR
388 > you install the latest
391 > Configuration files are in <TT
395 documentation is in <TT
397 >/usr/share/doc/privoxy-3.0.3</TT
399 and the Log directory is in <TT
401 >/var/log/privoxy</TT
410 NAME="INSTALLATION-SOURCE"
411 >2.2. Building from Source</A
414 > The most convenient way to obtain the <SPAN
418 is to download the source tarball from our <A
419 HREF="http://sf.net/projects/ijbswa/"
425 > If you like to live on the bleeding edge and are not afraid of using
426 possibly unstable development versions, you can check out the up-to-the-minute
427 version directly from <A
428 HREF="http://sourceforge.net/cvs/?group_id=11118"
432 > or simply download <A
433 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.bz2"
444 HREF="http://www.gnu.org/software/autoconf/autoconf.html"
449 HREF="http://www.gnu.org/software/make/make.html"
453 >, and, of course, a C compiler like <A
454 HREF="http://www.gnu.org/software/gcc/gcc.html"
459 > When building from a source tarball (either release version or
461 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.bz2"
465 >), first unpack the source: </P
475 > tar xzvf privoxy-3.0.3-src* [.tgz or .tar.gz]
476 cd privoxy-3.0.3</PRE
482 > For retrieving the current CVS sources, you'll need CVS installed.
483 Note that sources from CVS are development quality, and may not be
484 stable, or well tested. To download CVS source:</P
494 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
495 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
502 > This will create a directory named <TT
506 contain the source tree.</P
508 > Then, in either case, to build from unpacked tarball or CVS source:</P
520 ./configure # (--help to see options)
521 make # (the make from gnu, gmake for *BSD)
523 make -n install # (to see where all the files will go)
524 make install # (to really install)</PRE
530 > If you have gnu make, you can have the first four steps
531 automatically done for you by just typing:</P
547 > in the freshly downloaded or unpacked source directory.</P
549 > For more detailed instructions on how to build Redhat and SuSE RPMs,
550 Windows self-extracting installers, building on platforms with
551 special requirements etc, please consult the <A
552 HREF="../developer-manual/newrelease.html"
562 NAME="INSTALLATION-KEEPUPDATED"
563 >2.3. Keeping your Installation Up-to-Date</A
566 > As user feedback comes in and development continues, we will make updated versions
568 HREF="actions-file.html"
571 HREF="http://sourceforge.net/project/showfiles.php?group_id=11118&release_id=103670"
575 >) and the software itself (including the actions file) available for
578 > If you wish to receive an email notification whenever we release updates of
582 > or the actions file, <A
583 HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/"
586 to our announce mailing list</A
587 >, ijbswa-announce@lists.sourceforge.net.</P
589 > In order not to loose your personal changes and adjustments when updating
604 customization of <SPAN
608 HREF="actions-file.html"
609 >Chapter on actions files</A
618 SUMMARY="Footer navigation table"
629 HREF="introduction.html"
647 HREF="upgradersnote.html"
667 >Note to Upgraders</TD