-<HTML
-><HEAD
-><TITLE
->Installation</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.64
-"><LINK
-REL="HOME"
-TITLE="Privoxy User Manual"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Introduction"
-HREF="introduction.html"><LINK
-REL="NEXT"
-TITLE="Quickstart to Using Privoxy"
-HREF="quickstart.html"><LINK
-REL="STYLESHEET"
-TYPE="text/css"
-HREF="../p_doc.css"></HEAD
-><BODY
-CLASS="SECT1"
-BGCOLOR="#EEEEEE"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Privoxy User Manual</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="introduction.html"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="quickstart.html"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="INSTALLATION"
->3. Installation</A
-></H1
-><P
-> <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> is available as raw source code (tarball
- or via CVS), or pre-compiled binaries for various platforms. See the <A
-HREF="http://sourceforge.net/projects/ijbswa/"
-TARGET="_top"
->Privoxy Project Page</A
-> for
- the most up to date release information.
- <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> is also available via <A
-HREF="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ijbswa/current/"
-TARGET="_top"
->CVS</A
->.
- This is the recommended approach at this time. But
- please be aware that CVS is constantly changing, and it may break in
- mysterious ways.</P
-><P
-> At present, <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> is known to run on Win32, Mac
- OSX, OS/2, AmigaOS, Linux (RedHat, Suse, Debian), FreeBSD, and many flavors
- of Unix. There are source and binary releases for these available for
- download at <A
-HREF="http://sourceforge.net/project/showfiles.php?group_id=11118"
-TARGET="_top"
->http://sourceforge.net/project/showfiles.php?group_id=11118</A
->.</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="INSTALLATION-SOURCE"
->3.1. Source</A
-></H2
-><P
-> There are several ways to install <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->.</P
-><P
-> To build <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> from source,
- autoconf and GNU make (gmake) are required. Source is available as gzipped
- tar archives. For this, first unpack the source: </P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> tar xzvf privoxy-2.9.14-beta-src* [.tgz or .tar.gz]
- cd privoxy-2.9.14-beta
- </PRE
-></TD
-></TR
-></TABLE
-></P
-><P
-> For retrieving the current CVS sources, you'll need the CVS
- package installed first. Note CVS source is development quality,
- and may not be stable, or well tested. To download CVS source:</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
- cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+
+<html>
+<head>
+ <title>Installation</title>
+ <meta name="GENERATOR" content=
+ "Modular DocBook HTML Stylesheet Version 1.79">
+ <link rel="HOME" title="Privoxy 3.0.25 User Manual" href="index.html">
+ <link rel="PREVIOUS" title="Introduction" href="introduction.html">
+ <link rel="NEXT" title="What's New in this Release" href="whatsnew.html">
+ <link rel="STYLESHEET" type="text/css" href="../p_doc.css">
+ <meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <link rel="STYLESHEET" type="text/css" href="p_doc.css">
+</head>
+
+<body class="SECT1" bgcolor="#EEEEEE" text="#000000" link="#0000FF" vlink=
+"#840084" alink="#0000FF">
+ <div class="NAVHEADER">
+ <table summary="Header navigation table" width="100%" border="0"
+ cellpadding="0" cellspacing="0">
+ <tr>
+ <th colspan="3" align="center">Privoxy 3.0.25 User Manual</th>
+ </tr>
+
+ <tr>
+ <td width="10%" align="left" valign="bottom"><a href=
+ "introduction.html" accesskey="P">Prev</a></td>
+
+ <td width="80%" align="center" valign="bottom"></td>
+
+ <td width="10%" align="right" valign="bottom"><a href="whatsnew.html"
+ accesskey="N">Next</a></td>
+ </tr>
+ </table>
+ <hr align="left" width="100%">
+ </div>
+
+ <div class="SECT1">
+ <h1 class="SECT1"><a name="INSTALLATION" id="INSTALLATION">2.
+ Installation</a></h1>
+
+ <p><span class="APPLICATION">Privoxy</span> is available both in
+ convenient pre-compiled packages for a wide range of operating systems,
+ and as raw source code. For most users, we recommend using the packages,
+ which can be downloaded from our <a href=
+ "http://sourceforge.net/projects/ijbswa/" target="_top">Privoxy Project
+ Page</a>.</p>
+
+ <p>Note: On some platforms, the installer may remove previously installed
+ versions, if found. (See below for your platform). In any case
+ <span class="emphasis"><i class="EMPHASIS">be sure to backup your old
+ configuration if it is valuable to you.</i></span> See the <a href=
+ "whatsnew.html#UPGRADERSNOTE">note to upgraders</a> section below.</p>
+
+ <div class="SECT2">
+ <h2 class="SECT2"><a name="INSTALLATION-PACKAGES" id=
+ "INSTALLATION-PACKAGES">2.1. Binary Packages</a></h2>
+
+ <p>How to install the binary packages depends on your operating
+ system:</p>
+
+ <div class="SECT3">
+ <h3 class="SECT3"><a name="INSTALLATION-DEB" id=
+ "INSTALLATION-DEB">2.1.1. Debian and Ubuntu</a></h3>
+
+ <p>DEBs can be installed with <tt class="LITERAL">apt-get install
+ privoxy</tt>, and will use <tt class="FILENAME">/etc/privoxy</tt> for
+ the location of configuration files.</p>
+ </div>
+
+ <div class="SECT3">
+ <h3 class="SECT3"><a name="INSTALLATION-PACK-WIN" id=
+ "INSTALLATION-PACK-WIN">2.1.2. Windows</a></h3>
+
+ <p>Just double-click the installer, which will guide you through the
+ installation process. You will find the configuration files in the
+ same directory as you installed <span class=
+ "APPLICATION">Privoxy</span> in.</p>
+
+ <p>Version 3.0.5 beta introduced full <span class=
+ "APPLICATION">Windows</span> service functionality. On Windows only,
+ the <span class="APPLICATION">Privoxy</span> program has two new
+ command line arguments to install and uninstall <span class=
+ "APPLICATION">Privoxy</span> as a <span class="emphasis"><i class=
+ "EMPHASIS">service</i></span>.</p>
+
+ <div class="VARIABLELIST">
+ <dl>
+ <dt>Arguments:</dt>
+
+ <dd>
+ <p><tt class="REPLACEABLE"><i>--install</i></tt>[:<tt class=
+ "REPLACEABLE"><i>service_name</i></tt>]</p>
+
+ <p><tt class="REPLACEABLE"><i>--uninstall</i></tt>[:<tt class=
+ "REPLACEABLE"><i>service_name</i></tt>]</p>
+ </dd>
+ </dl>
+ </div>
+
+ <p>After invoking <span class="APPLICATION">Privoxy</span> with
+ <b class="COMMAND">--install</b>, you will need to bring up the
+ <span class="APPLICATION">Windows</span> service console to assign
+ the user you want <span class="APPLICATION">Privoxy</span> to run
+ under, and whether or not you want it to run whenever the system
+ starts. You can start the <span class="APPLICATION">Windows</span>
+ services console with the following command: <b class=
+ "COMMAND">services.msc</b>. If you do not take the manual step of
+ modifying <span class="APPLICATION">Privoxy's</span> service
+ settings, it will not start. Note too that you will need to give
+ Privoxy a user account that actually exists, or it will not be
+ permitted to write to its log and configuration files.</p>
+ </div>
+
+ <div class="SECT3">
+ <h3 class="SECT3"><a name="INSTALLATION-OS2" id=
+ "INSTALLATION-OS2">2.1.3. OS/2</a></h3>
+
+ <p>First, make sure that no previous installations of <span class=
+ "APPLICATION">Junkbuster</span> and / or <span class=
+ "APPLICATION">Privoxy</span> are left on your system. Check that no
+ <span class="APPLICATION">Junkbuster</span> or <span class=
+ "APPLICATION">Privoxy</span> objects are in your startup folder.</p>
+
+ <p>Then, just double-click the WarpIN self-installing archive, which
+ will guide you through the installation process. A shadow of the
+ <span class="APPLICATION">Privoxy</span> executable will be placed in
+ your startup folder so it will start automatically whenever OS/2
+ starts.</p>
+
+ <p>The directory you choose to install <span class=
+ "APPLICATION">Privoxy</span> into will contain all of the
+ configuration files.</p>
+ </div>
+
+ <div class="SECT3">
+ <h3 class="SECT3"><a name="INSTALLATION-MAC" id=
+ "INSTALLATION-MAC">2.1.4. Mac OS X</a></h3>
+
+ <p>Installation instructions for the OS X platform depend upon
+ whether you downloaded a ready-built installation package (.pkg or
+ .mpkg) or have downloaded the source code.</p>
+ </div>
+
+ <div class="SECT3">
+ <h4 class="SECT3"><a name="OS-X-INSTALL-FROM-PACKAGE" id=
+ "OS-X-INSTALL-FROM-PACKAGE">2.1.5. Installation from ready-built
+ package</a></h4>
+
+ <p>The downloaded file will either be a .pkg (for OS X 10.5 upwards)
+ or a bzipped .mpkg file (for OS X 10.4). The former can be
+ double-clicked as is and the installation will start; double-clicking
+ the latter will unzip the .mpkg file which can then be double-clicked
+ to commence the installation.</p>
+
+ <p>The privoxy service will automatically start after a successful
+ installation (and thereafter every time your computer starts up)
+ however you will need to configure your web browser(s) to use it. To
+ do so, configure them to use a proxy for HTTP and HTTPS at the
+ address 127.0.0.1:8118.</p>
+
+ <p>To prevent the privoxy service from automatically starting when
+ your computer starts up, remove or rename the file <tt class=
+ "LITERAL">/Library/LaunchDaemons/org.ijbswa.privoxy.plist</tt> (on OS
+ X 10.5 and higher) or the folder named <tt class=
+ "LITERAL">/Library/StartupItems/Privoxy</tt> (on OS X 10.4
+ 'Tiger').</p>
+
+ <p>To manually start or stop the privoxy service, use the scripts
+ startPrivoxy.sh and stopPrivoxy.sh supplied in /Applications/Privoxy.
+ They must be run from an administrator account, using sudo.</p>
+
+ <p>To uninstall, run /Applications/Privoxy/uninstall.command as sudo
+ from an administrator account.</p>
+ </div>
+
+ <div class="SECT3">
+ <h4 class="SECT3"><a name="OS-X-INSTALL-FROM-SOURCE" id=
+ "OS-X-INSTALL-FROM-SOURCE">2.1.6. Installation from source</a></h4>
+
+ <p>To build and install the Privoxy source code on OS X you will need
+ to obtain the macsetup module from the Privoxy Sourceforge CVS
+ repository (refer to Sourceforge help for details of how to set up a
+ CVS client to have read-only access to the repository). This module
+ contains scripts that leverage the usual open-source tools (available
+ as part of Apple's free of charge Xcode distribution or via the usual
+ open-source software package managers for OS X (MacPorts, Homebrew,
+ Fink etc.) to build and then install the privoxy binary and
+ associated files. The macsetup module's README file contains complete
+ instructions for its use.</p>
+
+ <p>The privoxy service will automatically start after a successful
+ installation (and thereafter every time your computer starts up)
+ however you will need to configure your web browser(s) to use it. To
+ do so, configure them to use a proxy for HTTP and HTTPS at the
+ address 127.0.0.1:8118.</p>
+
+ <p>To prevent the privoxy service from automatically starting when
+ your computer starts up, remove or rename the file <tt class=
+ "LITERAL">/Library/LaunchDaemons/org.ijbswa.privoxy.plist</tt> (on OS
+ X 10.5 and higher) or the folder named <tt class=
+ "LITERAL">/Library/StartupItems/Privoxy</tt> (on OS X 10.4
+ 'Tiger').</p>
+
+ <p>To manually start or stop the privoxy service, use the Privoxy
+ Utility for Mac OS X (also part of the macsetup module). This
+ application can start and stop the privoxy service and display its
+ log and configuration files.</p>
+
+ <p>To uninstall, run the macsetup module's uninstall.sh as sudo from
+ an administrator account.</p>
+ </div>
+
+ <div class="SECT3">
+ <h3 class="SECT3"><a name="INSTALLATION-FREEBSD" id=
+ "INSTALLATION-FREEBSD">2.1.7. FreeBSD</a></h3>
+
+ <p>Privoxy is part of FreeBSD's Ports Collection, you can build and
+ install it with <tt class="LITERAL">cd /usr/ports/www/privoxy; make
+ install clean</tt>.</p>
+ </div>
+ </div>
+
+ <div class="SECT2">
+ <h2 class="SECT2"><a name="INSTALLATION-SOURCE" id=
+ "INSTALLATION-SOURCE">2.2. Building from Source</a></h2>
+
+ <p>The most convenient way to obtain the <span class=
+ "APPLICATION">Privoxy</span> sources is to download the source tarball
+ from our <a href=
+ "http://sourceforge.net/project/showfiles.php?group_id=11118&package_id=10571"
+ target="_top">project download page</a>.</p>
+
+ <p>If you like to live on the bleeding edge and are not afraid of using
+ possibly unstable development versions, you can check out the
+ up-to-the-minute version directly from <a href=
+ "http://sourceforge.net/cvs/?group_id=11118" target="_top">the CVS
+ repository</a>.</p>
+
+ <p>To build <span class="APPLICATION">Privoxy</span> from source,
+ <a href="http://www.gnu.org/software/autoconf/autoconf.html" target=
+ "_top">autoconf</a>, <a href=
+ "http://www.gnu.org/software/make/make.html" target="_top">GNU make
+ (gmake)</a>, and, of course, a C compiler like <a href=
+ "http://www.gnu.org/software/gcc/gcc.html" target="_top">gcc</a> are
+ required.</p>
+
+ <p>When building from a source tarball, first unpack the source:</p>
+
+ <table border="0" bgcolor="#E0E0E0" width="100%">
+ <tr>
+ <td>
+ <pre class="SCREEN">
+ tar xzvf privoxy-3.0.25-beta-src.tar.gz
+ cd privoxy-3.0.25-beta
+</pre>
+ </td>
+ </tr>
+ </table>
+
+ <p>For retrieving the current CVS sources, you'll need a CVS client
+ installed. Note that sources from CVS are typically development
+ quality, and may not be stable, or well tested. To download CVS source,
+ check the Sourceforge documentation, which might give commands
+ like:</p>
+
+ <table border="0" bgcolor="#E0E0E0" width="100%">
+ <tr>
+ <td>
+ <pre class="SCREEN">
+ cvs -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa login
+ cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co current
cd current
- </PRE
-></TD
-></TR
-></TABLE
-></P
-><P
-> This will create a directory named <TT
-CLASS="FILENAME"
->current/</TT
->, which will
- contain the source tree.</P
-><P
-> Then, in either case, to build from unpacked tarball or CVS source:</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> autoheader
- autoconf
- ./configure (--help to see options)
- make (the make from gnu, gmake for *BSD)
- su
- make -n install (to see where all the files will go)
- make install (to really install)
- </PRE
-></TD
-></TR
-></TABLE
-></P
-><P
-> Redhat and SuSE src and binary RPMs can be built with
- <SPAN
-CLASS="QUOTE"
->"<B
-CLASS="COMMAND"
->make redhat-dist</B
->"</SPAN
-> or
- <SPAN
-CLASS="QUOTE"
->"<B
-CLASS="COMMAND"
->make suse-dist</B
->"</SPAN
-> from unpacked sources. You
- will need to run <SPAN
-CLASS="QUOTE"
->"<B
-CLASS="COMMAND"
->autoconf; autoheader;
- ./configure</B
->"</SPAN
-> beforehand. *BSD will require gmake (from
- <A
-HREF="http://www.gnu.org"
-TARGET="_top"
->http://www.gnu.org</A
->).
- </P
-><P
-> For Redhat and SuSE Linux RPM packages, see below.</P
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="INSTALLATION-RH"
->3.1.1. Red Hat</A
-></H3
-><P
-> To build Redhat RPM packages from source, install source as above. Then:</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> autoheader
- autoconf
- ./configure
- make redhat-dist
- </PRE
-></TD
-></TR
-></TABLE
-></P
-><P
-> This will create both binary and src RPMs in the usual places. Example:</P
-><P
-> /usr/src/redhat/RPMS/i686/privoxy-2.9.14-1.i686.rpm</P
-><P
-> /usr/src/redhat/SRPMS/privoxy-2.9.14-1.src.rpm</P
-><P
-> To install, of course:</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> rpm -Uvv /usr/src/redhat/RPMS/i686/privoxy-2.9.14-1.i686.rpm
- </PRE
-></TD
-></TR
-></TABLE
-></P
-><P
-> This will place the <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> configuration
- files in <TT
-CLASS="FILENAME"
->/etc/privoxy/</TT
->, and log files in
- <TT
-CLASS="FILENAME"
->/var/log/privoxy/</TT
->. Run
- <SPAN
-CLASS="QUOTE"
->"<B
-CLASS="COMMAND"
->chkconfig privoxy on</B
->"</SPAN
-> to have
- <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> start automatically during init. </P
-></DIV
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="INSTALLATION-SUSE"
->3.1.2. SuSE</A
-></H3
-><P
-> To build SuSE RPM packages, install source as above. Then:</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> autoheader
- autoconf
- ./configure
- make suse-dist
- </PRE
-></TD
-></TR
-></TABLE
-></P
-><P
-> This will create both binary and src RPMs in the usual places. Example:</P
-><P
-> /usr/src/packages/RPMS/i686/privoxy-2.9.14-1.i686.rpm</P
-><P
-> /usr/src/packages/SRPMS/privoxy-2.9.14-1.src.rpm</P
-><P
-> To install, of course:</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> rpm -Uvv /usr/src/packages/RPMS/i686/privoxy-2.9.14-1.i686.rpm
- </PRE
-></TD
-></TR
-></TABLE
-></P
-><P
-> This will place the <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> configuration
- files in <TT
-CLASS="FILENAME"
->/etc/privoxy/</TT
->, and log files in
- <TT
-CLASS="FILENAME"
->/var/log/privoxy/</TT
->. </P
-></DIV
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="INSTALLATION-OS2"
->3.1.3. OS/2</A
-></H3
-><P
-> <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> is packaged in a WarpIN self-
- installing archive. The self-installing program will be named depending
- on the release version, something like:
- <TT
-CLASS="FILENAME"
->privoxyos2_setup_2.9.14.exe</TT
->. In order to install it, simply
- run this executable or double-click on its icon and follow the WarpIN
- installation panels. A shadow of the <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->
- executable will be placed in your startup folder so it will start
- automatically whenever OS/2 starts.</P
-><P
-> The directory you choose to install <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->
- into will contain all of the configuration files.</P
-><P
-> If you would like to build binary images on OS/2 yourself, you will need
- a few Unix-like tools: autoconf, autoheader and sh. These tools will be
- used to create the required config.h file, which is not part of the
- source distribution because it differs based on platform. You will also
- need a compiler.
- The distribution has been created using IBM VisualAge compilers, but you
- can use any compiler you like. GCC/EMX has the disadvantage of needing
- to be single-threaded due to a limitation of EMX's implementation of the
- <TT
-CLASS="FUNCTION"
->select()</TT
-> socket call.</P
-><P
-> In addition to needing the source code distribution as outlined earlier,
- you will want to extract the <TT
-CLASS="FILENAME"
->os2seutp</TT
-> directory from CVS:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
- cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co os2setup
- </PRE
-></TD
-></TR
-></TABLE
->
- This will create a directory named os2setup/, which will contain the
- <TT
-CLASS="FILENAME"
->Makefile.vac</TT
-> makefile and <TT
-CLASS="FILENAME"
->os2build.cmd</TT
->
- which is used to completely create the binary distribution. The sequence
- of events for building the executable for yourself goes something like this:
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> cd current
+</pre>
+ </td>
+ </tr>
+ </table>
+
+ <p>This will create a directory named <tt class=
+ "FILENAME">current/</tt>, which will contain the source tree.</p>
+
+ <p>You can also check out any <span class="APPLICATION">Privoxy</span>
+ <span class="QUOTE">"branch"</span>, just exchange the <span class=
+ "APPLICATION">current</span> name with the wanted branch name (Example:
+ v_3_0_branch for the 3.0 cvs tree).</p>
+
+ <p>It is also strongly recommended to not run <span class=
+ "APPLICATION">Privoxy</span> as root. You should configure/install/run
+ <span class="APPLICATION">Privoxy</span> as an unprivileged user,
+ preferably by creating a <span class="QUOTE">"privoxy"</span> user and
+ group just for this purpose. See your local documentation for the
+ correct command line to do add new users and groups (something like
+ <b class="COMMAND">adduser</b>, but the command syntax may vary from
+ platform to platform).</p>
+
+ <p><tt class="FILENAME">/etc/passwd</tt> might then look like:</p>
+
+ <table border="0" bgcolor="#E0E0E0" width="100%">
+ <tr>
+ <td>
+ <pre class="SCREEN">
+ privoxy:*:7777:7777:privoxy proxy:/no/home:/no/shell
+</pre>
+ </td>
+ </tr>
+ </table>
+
+ <p>And then <tt class="FILENAME">/etc/group</tt>, like:</p>
+
+ <table border="0" bgcolor="#E0E0E0" width="100%">
+ <tr>
+ <td>
+ <pre class="SCREEN">
+ privoxy:*:7777:
+</pre>
+ </td>
+ </tr>
+ </table>
+
+ <p>Some binary packages may do this for you.</p>
+
+ <p>Then, to build from either unpacked tarball or CVS source:</p>
+
+ <table border="0" bgcolor="#E0E0E0" width="100%">
+ <tr>
+ <td>
+ <pre class="SCREEN">
autoheader
autoconf
- sh configure
- cd ..\os2setup
- nmake -f Makefile.vac
- </PRE
-></TD
-></TR
-></TABLE
->
- You will see this sequence laid out in <TT
-CLASS="FILENAME"
->os2build.cmd</TT
->.</P
-></DIV
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="INSTALLATION-WIN"
->3.1.4. Windows</A
-></H3
-><P
->Click-click. (I need help on this. Not a clue here. Also for
-configuration section below. HB.)</P
-></DIV
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="INSTALLATION-OTHER"
->3.1.5. Other</A
-></H3
-><P
-> Some quick notes on other Operating Systems.</P
-><P
-> For FreeBSD (and other *BSDs?), the build will require <B
-CLASS="COMMAND"
->gmake</B
->
- instead of the included <B
-CLASS="COMMAND"
->make</B
->. <B
-CLASS="COMMAND"
->gmake</B
-> is
- available from <A
-HREF="http://www.gnu.org"
-TARGET="_top"
->http://www.gnu.org</A
->.
- The rest should be the same as above for Linux/Unix.</P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="introduction.html"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="quickstart.html"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Introduction</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Quickstart to Using <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-></TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+ ./configure # (--help to see options)
+ make # (the make from GNU, sometimes called gmake)
+ su # Possibly required
+ make -n install # (to see where all the files will go)
+ make -s install # (to really install, -s to silence output)
+</pre>
+ </td>
+ </tr>
+ </table>
+
+ <p>Using GNU <b class="COMMAND">make</b>, you can have the first four
+ steps automatically done for you by just typing:</p>
+
+ <table border="0" bgcolor="#E0E0E0" width="100%">
+ <tr>
+ <td>
+ <pre class="SCREEN">
+ make
+</pre>
+ </td>
+ </tr>
+ </table>
+
+ <p>in the freshly downloaded or unpacked source directory.</p>
+
+ <p>To build an executable with security enhanced features so that users
+ cannot easily bypass the proxy (e.g. <span class="QUOTE">"Go There
+ Anyway"</span>), or alter their own configurations, <b class=
+ "COMMAND">configure</b> like this:</p>
+
+ <table border="0" bgcolor="#E0E0E0" width="100%">
+ <tr>
+ <td>
+ <pre class="SCREEN">
+ ./configure --disable-toggle --disable-editor --disable-force
+</pre>
+ </td>
+ </tr>
+ </table>
+
+ <p>Note that all of these options can also be disabled through the
+ configuration file.</p>
+
+ <p><span class="emphasis"><i class="EMPHASIS">WARNING:</i></span> If
+ installing as root, the install will fail unless a non-root user or
+ group is specified, or a <tt class="LITERAL">privoxy</tt> user and
+ group already exist on the system. If a non-root user is specified, and
+ no group, then the installation will try to also use a group of the
+ same name as <span class="QUOTE">"user"</span>. If a group is specified
+ (and no user), then the support files will be installed as writable by
+ that group, and owned by the user running the installation.</p>
+
+ <p><b class="COMMAND">configure</b> accepts <tt class=
+ "LITERAL">--with-user</tt> and <tt class="LITERAL">--with-group</tt>
+ options for setting user and group ownership of the configuration files
+ (which need to be writable by the daemon). The specified <span class=
+ "emphasis"><i class="EMPHASIS">user must already exist</i></span>. When
+ starting <span class="APPLICATION">Privoxy</span>, it must be run as
+ this same user to insure write access to configuration and log
+ files!</p>
+
+ <p>Alternately, you can specify <tt class="LITERAL">user</tt> and
+ <tt class="LITERAL">group</tt> on the <b class="COMMAND">make</b>
+ command line, but be sure both already exist:</p>
+
+ <table border="0" bgcolor="#E0E0E0" width="100%">
+ <tr>
+ <td>
+ <pre class="SCREEN">
+ make -s install USER=privoxy GROUP=privoxy
+</pre>
+ </td>
+ </tr>
+ </table>
+
+ <p>The default installation path for <b class="COMMAND">make
+ install</b> is <tt class="FILENAME">/usr/local</tt>. This may of course
+ be customized with the various <b class="COMMAND">./configure</b> path
+ options. If you are doing an install to anywhere besides <tt class=
+ "FILENAME">/usr/local</tt>, be sure to set the appropriate paths with
+ the correct configure options (<b class="COMMAND">./configure
+ --help</b>). Non-privileged users must of course have write access
+ permissions to wherever the target installation is going.</p>
+
+ <p>If you do install to <tt class="FILENAME">/usr/local</tt>, the
+ install will use <tt class=
+ "LITERAL">sysconfdir=$prefix/etc/privoxy</tt> by default. All other
+ destinations, and the direct usage of <tt class=
+ "LITERAL">--sysconfdir</tt> flag behave like normal, i.e. will not add
+ the extra <tt class="FILENAME">privoxy</tt> directory. This is for a
+ safer install, as there may already exist another program that uses a
+ file with the <span class="QUOTE">"config"</span> name, and thus makes
+ <tt class="FILENAME">/usr/local/etc</tt> cleaner.</p>
+
+ <p>If installing to <tt class="FILENAME">/usr/local</tt>, the
+ documentation will go by default to <tt class=
+ "FILENAME">$prefix/share/doc</tt>. But if this directory doesn't exist,
+ it will then try <tt class="FILENAME">$prefix/doc</tt> and install
+ there before creating a new <tt class="FILENAME">$prefix/share/doc</tt>
+ just for <span class="APPLICATION">Privoxy</span>.</p>
+
+ <p>Again, if the installs goes to <tt class="FILENAME">/usr/local</tt>,
+ the <tt class="LITERAL">localstatedir</tt> (ie: <tt class=
+ "FILENAME">var/</tt>) will default to <tt class="FILENAME">/var</tt>
+ instead of <tt class="LITERAL">$prefix/var</tt> so the logs will go to
+ <tt class="FILENAME">/var/log/privoxy/</tt>, and the pid file will be
+ created in <tt class="FILENAME">/var/run/privoxy.pid</tt>.</p>
+
+ <p><b class="COMMAND">make install</b> will attempt to set the correct
+ values in <tt class="FILENAME">config</tt> (main configuration file).
+ You should check this to make sure all values are correct. If
+ appropriate, an init script will be installed, but it is up to the user
+ to determine how and where to start <span class=
+ "APPLICATION">Privoxy</span>. The init script should be checked for
+ correct paths and values, if anything other than a default install is
+ done.</p>
+
+ <p>If install finds previous versions of local configuration files,
+ most of these will not be overwritten, and the new ones will be
+ installed with a <span class="QUOTE">"new"</span> extension.
+ default.action and default.filter <span class="emphasis"><i class=
+ "EMPHASIS">will be overwritten</i></span>. You will then need to
+ manually update the other installed configuration files as needed. The
+ default template files <span class="emphasis"><i class=
+ "EMPHASIS">will</i></span> be overwritten. If you have customized,
+ local templates, these should be stored safely in a separate directory
+ and defined in <tt class="FILENAME">config</tt> by the <span class=
+ "QUOTE">"templdir"</span> directive. It is of course wise to always
+ back-up any important configuration files <span class="QUOTE">"just in
+ case"</span>. If a previous version of <span class=
+ "APPLICATION">Privoxy</span> is already running, you will have to
+ restart it manually.</p>
+
+ <p>For more detailed instructions on how to build Redhat RPMs, Windows
+ self-extracting installers, building on platforms with special
+ requirements etc, please consult the <a href=
+ "http://www.privoxy.org/developer-manual/newrelease.html" target=
+ "_top">developer manual</a>.</p>
+ </div>
+
+ <div class="SECT2">
+ <h2 class="SECT2"><a name="INSTALLATION-KEEPUPDATED" id=
+ "INSTALLATION-KEEPUPDATED">2.3. Keeping your Installation
+ Up-to-Date</a></h2>
+
+ <p>If you wish to receive an email notification whenever we release
+ updates of <span class="APPLICATION">Privoxy</span> or the actions
+ file, <a href=
+ "http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/" target=
+ "_top">subscribe to our announce mailing list</a>,
+ ijbswa-announce@lists.sourceforge.net.</p>
+
+ <p>In order not to lose your personal changes and adjustments when
+ updating to the latest <tt class="LITERAL">default.action</tt> file we
+ <span class="emphasis"><i class="EMPHASIS">strongly
+ recommend</i></span> that you use <tt class="LITERAL">user.action</tt>
+ and <tt class="LITERAL">user.filter</tt> for your local customizations
+ of <span class="APPLICATION">Privoxy</span>. See the <a href=
+ "actions-file.html">Chapter on actions files</a> for details.</p>
+ </div>
+ </div>
+
+ <div class="NAVFOOTER">
+ <hr align="left" width="100%">
+
+ <table summary="Footer navigation table" width="100%" border="0"
+ cellpadding="0" cellspacing="0">
+ <tr>
+ <td width="33%" align="left" valign="top"><a href="introduction.html"
+ accesskey="P">Prev</a></td>
+
+ <td width="34%" align="center" valign="top"><a href="index.html"
+ accesskey="H">Home</a></td>
+
+ <td width="33%" align="right" valign="top"><a href="whatsnew.html"
+ accesskey="N">Next</a></td>
+ </tr>
+
+ <tr>
+ <td width="33%" align="left" valign="top">Introduction</td>
+
+ <td width="34%" align="center" valign="top"> </td>
+
+ <td width="33%" align="right" valign="top">What's New in this
+ Release</td>
+ </tr>
+ </table>
+ </div>
+</body>
+</html>
projects / privoxy.git / blobdiff