+<!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.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
-TITLE="Privoxy 3.1.1 User Manual"
+TITLE="Privoxy 3.0.17 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Introduction"
HREF="introduction.html"><LINK
REL="NEXT"
-TITLE="Note to Upgraders"
-HREF="upgradersnote.html"><LINK
+TITLE="What's New in this Release"
+HREF="whatsnew.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
-HREF="../p_doc.css"></HEAD
+HREF="../p_doc.css"><META
+HTTP-EQUIV="Content-Type"
+CONTENT="text/html;
+charset=ISO-8859-1">
+<LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css">
+</head
><BODY
CLASS="SECT1"
BGCOLOR="#EEEEEE"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.1.1 User Manual</TH
+>Privoxy 3.0.17 User Manual</TH
></TR
><TR
><TD
ALIGN="right"
VALIGN="bottom"
><A
-HREF="upgradersnote.html"
+HREF="whatsnew.html"
ACCESSKEY="N"
>Next</A
></TD
><H1
CLASS="SECT1"
><A
-NAME="INSTALLATION">2. Installation</H1
+NAME="INSTALLATION"
+>2. Installation</A
+></H1
><P
> <SPAN
CLASS="APPLICATION"
Page</A
>.</P
><P
-> Note: If you have a previous <SPAN
-CLASS="APPLICATION"
->Junkbuster</SPAN
-> or
- <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> installation on your system, you
- will need to remove it. On some platforms, this may be done for you as part
- of their installation procedure. (See below for your platform). In any case
- <SPAN
+> 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
+>be sure to backup
+ your old configuration if it is valuable to you.</I
></SPAN
> See the <A
-HREF="upgradersnote.html"
->note to
- upgraders</A
+HREF="whatsnew.html#UPGRADERSNOTE"
+>note to upgraders</A
> section below.</P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="INSTALLATION-PACKAGES">2.1. Binary Packages</H2
+NAME="INSTALLATION-PACKAGES"
+>2.1. Binary Packages</A
+></H2
><P
>How to install the binary packages depends on your operating system:</P
><DIV
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-PACK-RPM">2.1.1. Red Hat, SuSE and Conectiva RPMs</H3
+NAME="INSTALLATION-PACK-RPM"
+>2.1.1. Red Hat and Fedora RPMs</A
+></H3
><P
> RPMs can be installed with <TT
CLASS="LITERAL"
->rpm -Uvh privoxy-3.1.1-1.rpm</TT
+>rpm -Uvh privoxy-3.0.17-1.rpm</TT
>,
and will use <TT
CLASS="FILENAME"
<B
CLASS="COMMAND"
>ntsysv</B
->, or similar methods. Note that SuSE will
-automatically start Privoxy in the boot process.</P
+>, or similar methods. </P
><P
> If you have problems with failed dependencies, try rebuilding the SRC RPM:
<TT
CLASS="LITERAL"
->rpm --rebuild privoxy-3.1.1-1.src.rpm</TT
+>rpm --rebuild privoxy-3.0.17-1.src.rpm</TT
>. This
will use your locally installed libraries and RPM version. </P
><P
CLASS="APPLICATION"
>Junkbuster</SPAN
>
- automatically, before installing <SPAN
+ automatically if found, before installing <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>.</P
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-DEB">2.1.2. Debian</H3
+NAME="INSTALLATION-DEB"
+>2.1.2. Debian and Ubuntu</A
+></H3
><P
> DEBs can be installed with <TT
CLASS="LITERAL"
->dpkg -i
- privoxy_3.1.1-1.deb</TT
->, and will use
- <TT
+>apt-get install privoxy</TT
+>,
+ and will use <TT
CLASS="FILENAME"
>/etc/privoxy</TT
-> for the location of configuration
- files.</P
+> for the location of
+ configuration files.</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-PACK-WIN">2.1.3. Windows</H3
+NAME="INSTALLATION-PACK-WIN"
+>2.1.3. 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 Privoxy in. We do not
- use the registry of Windows. </P
+ 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
+><P
+></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-PACK-BINTGZ">2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</H3
+NAME="INSTALLATION-PACK-BINTGZ"
+>2.1.4. Solaris</A
+></H3
><P
> Create a new directory, <TT
CLASS="LITERAL"
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-OS2">2.1.5. OS/2</H3
+NAME="INSTALLATION-OS2"
+>2.1.5. OS/2</A
+></H3
><P
> First, make sure that no previous installations of
<SPAN
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-MAC">2.1.6. Mac OSX</H3
+NAME="INSTALLATION-MAC"
+>2.1.6. Mac OS X</A
+></H3
><P
-> Unzip the downloaded file (you can either double-click on the file
- from the finder, or from the desktop if you downloaded it there).
- Then, double-click on the package installer icon named
- <TT
-CLASS="LITERAL"
->Privoxy.pkg</TT
->
- and follow the installation process.
- <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> will be installed in the folder
- <TT
-CLASS="LITERAL"
->/Library/Privoxy</TT
->.
- It will start automatically whenever you start up. To prevent it from
- starting automatically, remove or rename the folder
+> Unzip the downloaded file (you can either double-click on the zip file
+ icon from the Finder, or from the desktop if you downloaded it there).
+ Then, double-click on the package installer icon and follow the
+ installation process.</P
+><P
+> The privoxy service will automatically start after a successful
+ installation (in addition to every time your computer starts up). To
+ prevent the privoxy service from automatically starting when your
+ computer starts up, remove or rename the folder named
<TT
CLASS="LITERAL"
>/Library/StartupItems/Privoxy</TT
>. </P
><P
-> To start Privoxy by hand, double-click on
- <TT
-CLASS="LITERAL"
->StartPrivoxy.command</TT
-> in the
- <TT
-CLASS="LITERAL"
->/Library/Privoxy</TT
-> folder.
- Or, type this command in the Terminal:</P
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> /Library/Privoxy/StartPrivoxy.command
- </PRE
-></TD
-></TR
-></TABLE
-></P
-><P
-> You will be prompted for the administrator password.</P
+> To manually start or stop the privoxy service, use the Privoxy Utility
+ for Mac OS X. This application controls the privoxy service (e.g.
+ starting and stopping the service as well as uninstalling the software).</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATION-AMIGA">2.1.7. AmigaOS</H3
+NAME="INSTALLATION-AMIGA"
+>2.1.7. AmigaOS</A
+></H3
><P
> Copy and then unpack the <TT
CLASS="FILENAME"
><H3
CLASS="SECT3"
><A
-NAME="INSTALLATTION-GENTOO">2.1.8. Gentoo</H3
+NAME="INSTALLATION-TBZ"
+>2.1.8. 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
+><P
+> If you don't use the ports, you can fetch and install
+ the package with <TT
+CLASS="LITERAL"
+>pkg_add -r privoxy</TT
+>.</P
+><P
+> The port skeleton and the package can also be downloaded from the
+ <A
+HREF="https://sourceforge.net/project/showfiles.php?group_id=11118"
+TARGET="_top"
+>File Release
+ Page</A
+>, but there's no reason to use them unless you're interested in the
+ beta releases which are only available there.</P
+></DIV
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="INSTALLATTION-GENTOO"
+>2.1.9. Gentoo</A
+></H3
><P
> Gentoo source packages (Ebuilds) for <SPAN
CLASS="APPLICATION"
> under Gentoo just do
first <TT
CLASS="LITERAL"
->emerge rsync</TT
+>emerge --sync</TT
> to get the latest changes from the
Portage tree. With <TT
CLASS="LITERAL"
>, the
documentation is in <TT
CLASS="FILENAME"
->/usr/share/doc/privoxy-3.1.1</TT
+>/usr/share/doc/privoxy-3.0.17</TT
>
and the Log directory is in <TT
CLASS="FILENAME"
><H2
CLASS="SECT2"
><A
-NAME="INSTALLATION-SOURCE">2.2. Building from Source</H2
+NAME="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://sf.net/projects/ijbswa/"
+ 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
+>project download
page</A
>.</P
><P
TARGET="_top"
>the
CVS repository</A
-> or simply download <A
-HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
-TARGET="_top"
->the nightly CVS
- tarball.</A
-></P
+>. </P
><P
> To build <SPAN
CLASS="APPLICATION"
>gcc</A
> are required.</P
><P
-> When building from a source tarball (either release version or
- <A
-HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
-TARGET="_top"
->nightly CVS
- tarball</A
->), first unpack the source: </P
+> When building from a source tarball,
+ first unpack the source: </P
><P
> <TABLE
BORDER="0"
><TD
><PRE
CLASS="SCREEN"
-> tar xzvf privoxy-3.1.1-beta-src* [.tgz or .tar.gz]
- cd privoxy-3.1.1-beta</PRE
+> tar xzvf privoxy-3.0.17-stable-src.tar.gz
+ cd privoxy-3.0.17-stable</PRE
></TD
></TR
></TABLE
></P
><P
-> For retrieving the current CVS sources, you'll need CVS installed.
- Note that sources from CVS are development quality, and may not be
- stable, or well tested. To download CVS source:</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
><P
> <TABLE
BORDER="0"
><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
+> 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
>, which will
contain the source tree.</P
><P
-> Then, in either case, to build from unpacked tarball or CVS source:</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
+><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
+><P
+> And then <TT
+CLASS="FILENAME"
+>/etc/group</TT
+>, like:</P
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> privoxy:*:7777:</PRE
+></TD
+></TR
+></TABLE
+></P
+><P
+> Some binary packages may do this for you.</P
+><P
+> Then, to build from either unpacked tarball or CVS source:</P
><P
> <TABLE
BORDER="0"
> autoheader
autoconf
./configure # (--help to see options)
- make # (the make from gnu, gmake for *BSD)
- su
+ make # (the make from GNU, sometimes called gmake)
+ su # Possibly required
make -n install # (to see where all the files will go)
- make install # (to really install)</PRE
+ make -s install # (to really install, -s to silence output)</PRE
></TD
></TR
></TABLE
></P
-><DIV
-CLASS="WARNING"
><P
-></P
-><TABLE
-CLASS="WARNING"
-BORDER="1"
+> Using GNU <B
+CLASS="COMMAND"
+>make</B
+>, you can have the first four steps
+ automatically done for you by just typing:</P
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
-ALIGN="CENTER"
-><B
->Warning</B
+><PRE
+CLASS="SCREEN"
+> make</PRE
></TD
></TR
-><TR
-><TD
-ALIGN="LEFT"
+></TABLE
+></P
+><P
+> in the freshly downloaded or unpacked source directory.</P
><P
->
- The <SPAN
+> To build an executable with security enhanced features so that
+ users cannot easily bypass the proxy (e.g. <SPAN
CLASS="QUOTE"
->"make install"</SPAN
-> target is temporary quite broken! It is
- recommended to use a binary package, or do a source build, and manually
- install the components. Sorry.
- </P
+>"Go There Anyway"</SPAN
+>), or
+ alter their own configurations, <B
+CLASS="COMMAND"
+>configure</B
+> like this:</P
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> ./configure --disable-toggle --disable-editor --disable-force</PRE
></TD
></TR
></TABLE
-></DIV
+></P
><P
-> If you have gnu make, you can have the first four steps
- automatically done for you by just typing:</P
+>Then build as above. In Privoxy 3.0.7 and later, 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
><P
> <TABLE
BORDER="0"
><TD
><PRE
CLASS="SCREEN"
-> make</PRE
+> make -s install USER=privoxy GROUP=privoxy</PRE
></TD
></TR
></TABLE
></P
><P
-> in the freshly downloaded or unpacked source directory.</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
-> For more detailed instructions on how to build Redhat and SuSE RPMs,
+> <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="../developer-manual/newrelease.html"
+HREF="http://www.privoxy.org/developer-manual/newrelease.html"
TARGET="_top"
>developer manual</A
>.</P
><H2
CLASS="SECT2"
><A
-NAME="INSTALLATION-KEEPUPDATED">2.3. Keeping your Installation Up-to-Date</H2
+NAME="INSTALLATION-KEEPUPDATED"
+>2.3. Keeping your Installation Up-to-Date</A
+></H2
><P
> As user feedback comes in and development continues, we will make updated versions
of both the main <A
HREF="actions-file.html"
>actions file</A
> (as a <A
-HREF="http://sourceforge.net/project/showfiles.php?group_id=11118&release_id=103670"
+HREF="http://sourceforge.net/project/showfiles.php?group_id=11118&release_id=103670"
TARGET="_top"
>separate
package</A
to our announce mailing list</A
>, ijbswa-announce@lists.sourceforge.net.</P
><P
-> In order not to loose your personal changes and adjustments when updating
+> In order not to lose your personal changes and adjustments when updating
to the latest <TT
CLASS="LITERAL"
>default.action</TT
> that you use <TT
CLASS="LITERAL"
>user.action</TT
-> for your
- customization of <SPAN
+> and
+ <TT
+CLASS="LITERAL"
+>user.filter</TT
+> for your local
+ customizations of <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>. See the <A
ALIGN="right"
VALIGN="top"
><A
-HREF="upgradersnote.html"
+HREF="whatsnew.html"
ACCESSKEY="N"
>Next</A
></TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Note to Upgraders</TD
+>What's New in this Release</TD
></TR
></TABLE
></DIV
></BODY
></HTML
->
\ No newline at end of file
+>
projects / privoxy.git / blobdiff