X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Finstallation.html;h=0f2682ab8d1ff1c3ac4e89cbeb005f8814f4ed55;hb=661f2e8546ef7c92b6ff51cf44116af9d40c1265;hp=a2c87ff50d48519e2d2ab1d1c413fe788cab2dec;hpb=2d6b5d2e894f920d7e376a9dc4fa436a8dbefcec;p=privoxy.git diff --git a/doc/webserver/user-manual/installation.html b/doc/webserver/user-manual/installation.html index a2c87ff5..0f2682ab 100644 --- a/doc/webserver/user-manual/installation.html +++ b/doc/webserver/user-manual/installation.html @@ -1,536 +1,520 @@ -
Privoxy 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 - Privoxy Project - Page.
Note: If you have a previous Junkbuster or - Privoxy 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 - be sure to backup your old configuration if it is valuable to - you. See the note to - upgraders section below.
How to install the binary packages depends on your operating system:
RPMs can be installed with rpm -Uvh privoxy-2.9.15-1.rpm, - and will use /etc/privoxy for the location - of configuration files.
Note that on Red Hat, Privoxy will - not be automatically started on system boot. You will - need to enable that using chkconfig, - ntsysv, or similar methods. Note that SuSE will -automatically start Privoxy in the boot process.
If you have problems with failed dependencies, try rebuilding the SRC RPM: - rpm --rebuild privoxy-2.9.15-1.src.rpm. This - will use your locally installed libraries and RPM version.
Also note that if you have a Junkbuster RPM installed - on your system, you need to remove it first, because the packages conflict. - Otherwise, RPM will try to remove Junkbuster - automatically, before installing Privoxy.
FIXME.
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.
Create a new directory, cd to it, then unzip and - untar the archive. For the most part, you'll have to figure out where - things go. FIXME.
First, make sure that no previous installations of - Junkbuster and / or - Privoxy are left on your - system. You can do this by
Then, just double-click the WarpIN self-installing archive, which will - guide you through the installation process. A shadow of the - Privoxy executable will be placed in your - startup folder so it will start automatically whenever OS/2 starts.
The directory you choose to install Privoxy - into will contain all of the configuration files.
Unzip the downloaded package (you can either double-click on the file - in the finder, or on the desktop if you downloaded it there). Then, - double-click on the package installer icon and follow the installation - process. - Privoxy will be installed in the subdirectory - /Applications/Privoxy.app. - Privoxy will set itself up to start - automatically on system bring-up via - /System/Library/StartupItems/Privoxy.
Copy and then unpack the lha archive to a suitable location. - All necessary files will be installed into Privoxy - directory, including all configuration and log files. To uninstall, just - remove this directory.
Start Privoxy (with RUN <>NIL:) in your - startnet script (AmiTCP), in - s:user-startup (RoadShow), as startup program in your - startup script (Genesis), or as startup action (Miami and MiamiDx). - Privoxy will automatically quit when you quit your - TCP/IP stack (just ignore the harmless warning your TCP/IP stack may display that - Privoxy is still running).
The most convenient way to obtain the Privoxy sources - is to download the source tarball from our project - page.
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 the - CVS repository or simply download the nightly CVS - tarball.
To build Privoxy from source, - autoconf, - GNU make - (gmake), and, of course, a C compiler like gcc are required.
When building from a source tarball (either release version or - nightly CVS - tarball), first unpack the source:
tar xzvf privoxy-2.9.15-beta-src* [.tgz or .tar.gz] - cd privoxy-2.9.15-beta |
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:
cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login - cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current - cd current |
This will create a directory named current/, which will - contain the source tree.
Then, in either case, to build from unpacked tarball or CVS source:
autoheader + + + + ++ |
+
Using GNU make, you can have the first four + steps automatically done for you by just typing:
+ +
+ + make ++ |
+
in the freshly downloaded or unpacked source directory.
+ +To build an executable with security enhanced features so that users + cannot easily bypass the proxy (e.g. "Go There + Anyway"), or alter their own configurations, configure like this:
+ +
+ + ./configure --disable-toggle --disable-editor --disable-force ++ |
+
Note that all of these options can also be disabled through the + configuration file.
+ +WARNING: If + installing as root, the install will fail unless a non-root user or + group is specified, or a privoxy 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 "user". 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.
+ +configure accepts --with-user and --with-group + options for setting user and group ownership of the configuration files + (which need to be writable by the daemon). The specified user must already exist. When + starting Privoxy, it must be run as + this same user to insure write access to configuration and log + files!
+ +Alternately, you can specify user and + group on the make + command line, but be sure both already exist:
+ +
+ + make -s install USER=privoxy GROUP=privoxy ++ |
+
The default installation path for make + install is /usr/local. This may of course + be customized with the various ./configure path + options. If you are doing an install to anywhere besides /usr/local, be sure to set the appropriate paths with + the correct configure options (./configure + --help). Non-privileged users must of course have write access + permissions to wherever the target installation is going.
+ +If you do install to /usr/local, the + install will use sysconfdir=$prefix/etc/privoxy by default. All other + destinations, and the direct usage of --sysconfdir flag behave like normal, i.e. will not add + the extra privoxy directory. This is for a + safer install, as there may already exist another program that uses a + file with the "config" name, and thus makes + /usr/local/etc cleaner.
+ +If installing to /usr/local, the + documentation will go by default to $prefix/share/doc. But if this directory doesn't exist, + it will then try $prefix/doc and install + there before creating a new $prefix/share/doc + just for Privoxy.
+ +Again, if the installs goes to /usr/local, + the localstatedir (ie: var/) will default to /var + instead of $prefix/var so the logs will go to + /var/log/privoxy/, and the pid file will be + created in /var/run/privoxy.pid.
+ +make install will attempt to set the correct + values in config (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 Privoxy. The init script should be checked for + correct paths and values, if anything other than a default install is + done.
+ +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 "new" extension. + default.action and default.filter will be overwritten. You will then need to + manually update the other installed configuration files as needed. The + default template files will be overwritten. If you have customized, + local templates, these should be stored safely in a separate directory + and defined in config by the "templdir" directive. It is of course wise to always + back-up any important configuration files "just in + case". If a previous version of Privoxy is already running, you will have to + restart it manually.
+ +For more detailed instructions on how to build Redhat RPMs, Windows + self-extracting installers, building on platforms with special + requirements etc, please consult the developer manual.
+If you wish to receive an email notification whenever we release + updates of Privoxy or the actions + file, subscribe to our announce mailing list, + ijbswa-announce@lists.sourceforge.net.
+ +In order not to lose your personal changes and adjustments when + updating to the latest default.action file we + strongly + recommend that you use user.action + and user.filter for your local customizations + of Privoxy. See the Chapter on actions files for details.
+