7 CONTENT="Modular DocBook HTML Stylesheet Version 1.64
10 TITLE="Privoxy 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
39 >Privoxy User Manual</TH
47 HREF="introduction.html"
60 HREF="upgradersnote.html"
80 > is available both in convenient pre-compiled
81 packages for a wide range of operating systems, and as raw source code.
82 For most users, we recommend using the packages, which can be downloaded from our
84 HREF="http://sourceforge.net/projects/ijbswa/"
88 >. For installing and compiling the source code, please look
89 into our Developer Manual.</P
91 > If you like to live on the bleeding edge and are not afraid of using
92 possibly unstable development versions, you can check out the up-to-the-minute
93 version directly from <A
94 HREF="http://sourceforge.net/cvs/?group_id=11118"
98 > or simply download <A
99 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
103 > Again, we refer you to the Developer Manual.</P
109 Windows(95, 98, ME, 2000, XP), Linux (RedHat, Suse, Debian), Mac OSX,
110 OS/2, AmigaOS, FreeBSD, NetBSD, BeOS, and many more flavors of Unix.</P
112 > Note: If you have a previous <SPAN
119 > installation on your system, you
120 will need to remove it. Some platforms do this for you as part
121 of their installation procedure. (See below for your platform).</P
125 >be sure to backup your old configuration
126 if it is valuable to you.</I
129 HREF="upgradersnote.html"
130 >note to upgraders</A
138 NAME="INSTALLATION-PACK-RPM"
139 >3.1. Red Hat and SuSE RPMs</A
142 > RPMs can be installed with <TT
144 >rpm -Uvh privoxy-2.9.14-1.rpm</TT
150 of configuration files.</P
152 > Note that on Red Hat, <SPAN
159 > be automatically started on system boot. You will
160 need to enable that using <B
167 >, or similar methods. Note that SuSE will
168 automatically start Privoxy in the boot process.</P
170 > If you have problems with failed dependencies, try rebuilding the SRC RPM:
173 >rpm --rebuild privoxy-2.9.14-1.src.rpm;</TT
175 will use your locally installed libraries and RPM version. </P
177 > Also note that if you have a <SPAN
181 on your system, you need to remove it first, because the packages conflict.
182 Otherwise, RPM will try to remove <SPAN
186 automatically, before installing <SPAN
196 NAME="INSTALLATION-DEB"
207 NAME="INSTALLATION-PACK-WIN"
211 > Just double-click the installer, which will guide you through
212 the installation process. You will find the configuration files
213 in the same directory as you installed Privoxy in. We do not
214 use the registry of Windows. </P
221 NAME="INSTALLATION-PACK-BINTGZ"
222 >3.4. Solaris, NetBSD, FreeBSD, HP-UX</A
225 > Create a new directory, <TT
228 > to it, then unzip and
229 untar the archive. For the most part, you'll have to figure out where
237 NAME="INSTALLATION-OS2"
241 > First, make sure that no previous installations of
250 system. You can do this by </P
252 > Then, just double-click the WarpIN self-installing archive, which will
253 guide you through the installation process. A shadow of the
257 > executable will be placed in your
258 startup folder so it will start automatically whenever OS/2 starts.</P
260 > The directory you choose to install <SPAN
264 into will contain all of the configuration files.</P
271 NAME="INSTALLATION-MAC"
275 > Unzip the downloaded package (you can either double-click on the file
276 in the finder, or on the desktop if you downloaded it there). Then,
277 double-click on the package installer icon and follow the installation
282 > will be installed in the subdirectory
285 >/Applications/Privoxy.app</TT
290 > will set itself up to start
291 automatically on system bring-up via
294 >/System/Library/StartupItems/Privoxy</TT
302 NAME="INSTALLATION-AMIGA"
306 > Copy and then unpack the <TT
309 > archive to a suitable location.
310 All necessary files will be installed into <SPAN
314 directory, including all configuration and log files. To uninstall, just
315 remove this directory.</P
320 > (with RUN <>NIL:) in your
324 > script (AmiTCP), in
328 > (RoadShow), as startup program in your
329 startup script (Genesis), or as startup action (Miami and MiamiDx).
333 > will automatically quit when you quit your
334 TCP/IP stack (just ignore the harmless warning your TCP/IP stack may display that
338 > is still running).</P
356 HREF="introduction.html"
372 HREF="upgradersnote.html"
391 >Note to Upgraders</TD