7 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
10 TITLE="Privoxy 3.1.1 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.1.1 User Manual</TH
48 HREF="introduction.html"
62 HREF="upgradersnote.html"
76 NAME="INSTALLATION">2. Installation</H1
81 > is available both in convenient pre-compiled
82 packages for a wide range of operating systems, and as raw source code.
83 For most users, we recommend using the packages, which can be downloaded from our
85 HREF="http://sourceforge.net/projects/ijbswa/"
91 > Note: If you have a previous <SPAN
98 > installation on your system, you
99 will need to remove it. On some platforms, this may be done for you as part
100 of their installation procedure. (See below for your platform). In any case
105 >be sure to backup your old configuration if it is valuable to
109 HREF="upgradersnote.html"
118 NAME="INSTALLATION-PACKAGES">2.1. Binary Packages</H2
120 >How to install the binary packages depends on your operating system:</P
126 NAME="INSTALLATION-PACK-RPM">2.1.1. Red Hat, SuSE and Conectiva RPMs</H3
128 > RPMs can be installed with <TT
130 >rpm -Uvh privoxy-3.1.1-1.rpm</TT
136 of configuration files.</P
138 > Note that on Red Hat, <SPAN
148 > be automatically started on system boot. You will
149 need to enable that using <B
156 >, or similar methods. Note that SuSE will
157 automatically start Privoxy in the boot process.</P
159 > If you have problems with failed dependencies, try rebuilding the SRC RPM:
162 >rpm --rebuild privoxy-3.1.1-1.src.rpm</TT
164 will use your locally installed libraries and RPM version. </P
166 > Also note that if you have a <SPAN
170 on your system, you need to remove it first, because the packages conflict.
171 Otherwise, RPM will try to remove <SPAN
175 automatically, before installing <SPAN
185 NAME="INSTALLATION-DEB">2.1.2. Debian</H3
187 > DEBs can be installed with <TT
190 privoxy_3.1.1-1.deb</TT
195 > for the location of configuration
203 NAME="INSTALLATION-PACK-WIN">2.1.3. Windows</H3
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">2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</H3
217 > Create a new directory, <TT
220 > to it, then unzip and
221 untar the archive. For the most part, you'll have to figure out where
229 NAME="INSTALLATION-OS2">2.1.5. OS/2</H3
231 > First, make sure that no previous installations of
240 system. Check that no <SPAN
248 your startup folder. </P
250 > Then, just double-click the WarpIN self-installing archive, which will
251 guide you through the installation process. A shadow of the
255 > executable will be placed in your
256 startup folder so it will start automatically whenever OS/2 starts.</P
258 > The directory you choose to install <SPAN
262 into will contain all of the configuration files.</P
269 NAME="INSTALLATION-MAC">2.1.6. Mac OSX</H3
271 > Unzip the downloaded file (you can either double-click on the file
272 from the finder, or from the desktop if you downloaded it there).
273 Then, double-click on the package installer icon named
278 and follow the installation process.
282 > will be installed in the folder
285 >/Library/Privoxy</TT
287 It will start automatically whenever you start up. To prevent it from
288 starting automatically, remove or rename the folder
291 >/Library/StartupItems/Privoxy</TT
294 > To start Privoxy by hand, double-click on
297 >StartPrivoxy.command</TT
301 >/Library/Privoxy</TT
303 Or, type this command in the Terminal:</P
313 > /Library/Privoxy/StartPrivoxy.command
320 > You will be prompted for the administrator password.</P
327 NAME="INSTALLATION-AMIGA">2.1.7. AmigaOS</H3
329 > Copy and then unpack the <TT
332 > archive to a suitable location.
333 All necessary files will be installed into <SPAN
337 directory, including all configuration and log files. To uninstall, just
338 remove this directory.</P
345 NAME="INSTALLATTION-GENTOO">2.1.8. Gentoo</H3
347 > Gentoo source packages (Ebuilds) for <SPAN
351 contained in the Gentoo Portage Tree (they are not on the download page,
352 but there is a Gentoo section, where you can see when a new
356 > Version is added to the Portage Tree).</P
358 > Before installing <SPAN
361 > under Gentoo just do
365 > to get the latest changes from the
366 Portage tree. With <TT
369 > you install the latest
372 > Configuration files are in <TT
376 documentation is in <TT
378 >/usr/share/doc/privoxy-3.1.1</TT
380 and the Log directory is in <TT
382 >/var/log/privoxy</TT
391 NAME="INSTALLATION-SOURCE">2.2. Building from Source</H2
393 > The most convenient way to obtain the <SPAN
397 is to download the source tarball from our <A
398 HREF="http://sf.net/projects/ijbswa/"
404 > If you like to live on the bleeding edge and are not afraid of using
405 possibly unstable development versions, you can check out the up-to-the-minute
406 version directly from <A
407 HREF="http://sourceforge.net/cvs/?group_id=11118"
411 > or simply download <A
412 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
423 HREF="http://www.gnu.org/software/autoconf/autoconf.html"
428 HREF="http://www.gnu.org/software/make/make.html"
432 >, and, of course, a C compiler like <A
433 HREF="http://www.gnu.org/software/gcc/gcc.html"
438 > When building from a source tarball (either release version or
440 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
444 >), first unpack the source: </P
454 > tar xzvf privoxy-3.1.1-beta-src* [.tgz or .tar.gz]
455 cd privoxy-3.1.1-beta</PRE
461 > For retrieving the current CVS sources, you'll need CVS installed.
462 Note that sources from CVS are development quality, and may not be
463 stable, or well tested. To download CVS source:</P
473 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
474 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
481 > This will create a directory named <TT
485 contain the source tree.</P
487 > Then, in either case, to build from unpacked tarball or CVS source:</P
499 ./configure # (--help to see options)
500 make # (the make from gnu, gmake for *BSD)
502 make -n install # (to see where all the files will go)
503 make install # (to really install)</PRE
530 >"make install"</SPAN
531 > target is temporary quite broken! It is
532 recommended to use a binary package, or do a source build, and manually
533 install the components. Sorry.
540 > If you have gnu make, you can have the first four steps
541 automatically done for you by just typing:</P
557 > in the freshly downloaded or unpacked source directory.</P
559 > For more detailed instructions on how to build Redhat and SuSE RPMs,
560 Windows self-extracting installers, building on platforms with
561 special requirements etc, please consult the <A
562 HREF="../developer-manual/newrelease.html"
572 NAME="INSTALLATION-KEEPUPDATED">2.3. Keeping your Installation Up-to-Date</H2
574 > As user feedback comes in and development continues, we will make updated versions
576 HREF="actions-file.html"
579 HREF="http://sourceforge.net/project/showfiles.php?group_id=11118&release_id=103670"
583 >) and the software itself (including the actions file) available for
586 > If you wish to receive an email notification whenever we release updates of
590 > or the actions file, <A
591 HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/"
594 to our announce mailing list</A
595 >, ijbswa-announce@lists.sourceforge.net.</P
597 > In order not to loose your personal changes and adjustments when updating
612 customization of <SPAN
616 HREF="actions-file.html"
617 >Chapter on actions files</A
626 SUMMARY="Footer navigation table"
637 HREF="introduction.html"
655 HREF="upgradersnote.html"
675 >Note to Upgraders</TD