*********************************************************************/
-This README is included with the development version of Privoxy 2.9.14, which
+This README is included with the development version of Privoxy 2.9.13, which
will eventually become Privoxy v3.0 (and soon we hope!). See http://
www.privoxy.org/ for more information. The current code level is beta, and
seems stable to us :).
To build Privoxy from source, autoconf and GNU make (gmake) are required.
Source is available as gzipped tar archives. For this, first unpack the source:
- tar xzvf privoxy-2.9.14-beta-src* [.tgz or .tar.gz]
- cd privoxy-2.9.14-beta
+ tar xzvf privoxy-2.9.13-beta-src* [.tgz or .tar.gz]
+ cd privoxy-2.9.13-beta
For retrieving the current CVS sources, you'll need the CVS package installed
* Use the Sourceforge Support Forum to get help:
- http://sourceforge.net/tracker/?group_id=11118&atid=211118
+ http://sourceforge.net/tracker/?group_id=11118&atid=211118
* Submit bugs only through our Sourceforge Bug Forum:
- http://sourceforge.net/tracker/?group_id=11118&atid=111118.
+ http://sourceforge.net/tracker/?group_id=11118&atid=111118.
Make sure that the bug has not already been submitted. Please try to verify
platform, browser, any pertinent log data, any other relevant details
(please be specific) and, if possible, some way to reproduce the bug.
- * Submit feature requests only through our Sourceforge feature request
- forum:
+ * Submit feature requests only through our Sourceforge feature request forum:
- http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse.
+ http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse.
- * We will soon have an automated way to submit advertisements, incorrectly
- blocked images, popups and the like. Check back.
+ * Submit missed ads and banners, and incorrectly blocked images, popups, etc:
+
+ http://p.p/, and select "actions file feedback system"
+ This page can also be reached from many of the internal CGI pages.
+
* For any other issues, feel free to use the mailing lists:
- http://sourceforge.net/mail/?group_id=11118.
+ http://sourceforge.net/mail/?group_id=11118.
Anyone interested in actively participating in development and related
ijbswa-developers@lists.sourceforge.net
-$Id: readme.sgml,v 1.5 2002/04/08 20:49:38 swa Exp $
+$Id: readme.sgml,v 1.6 2002/04/08 22:59:26 hal9 Exp $
Purpose : AUTHORS file for Privoxy
- $Id: authors.sgml,v 1.2 2002/04/08 20:48:37 swa Exp $
+ $Id: authors.sgml,v 1.3 2002/04/08 22:59:26 hal9 Exp $
Written by and Copyright (C) 2001 the SourceForge
Privoxy team. http://www.privoxy.org/
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [
<!entity % dummy "INCLUDE">
<!entity authors SYSTEM "p-authors.sgml">
-<!entity p-version "2.9.14">
+<!entity p-version "2.9.13">
<!entity p-status "beta">
<!entity % p-not-stable "INCLUDE">
<!entity % p-stable "IGNORE">
<!entity seealso SYSTEM "seealso.sgml">
<!entity contacting SYSTEM "contacting.sgml">
<!entity copyright SYSTEM "copyright.sgml">
-<!entity p-version "2.9.14">
+<!entity p-version "2.9.13">
<!entity p-status "beta">
<!entity % p-not-stable "INCLUDE">
<!entity % p-stable "IGNORE">
This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: developer-manual.sgml,v 1.27 2002/04/08 15:31:18 hal9 Exp $
+ $Id: developer-manual.sgml,v 1.28 2002/04/08 22:59:26 hal9 Exp $
Written by and Copyright (C) 2001 the SourceForge
Privoxy team. http://www.privoxy.org/
<artheader>
<title>Privoxy Developer Manual</title>
- <pubdate>$Id: developer-manual.sgml,v 1.27 2002/04/08 15:31:18 hal9 Exp $</pubdate>
+ <pubdate>$Id: developer-manual.sgml,v 1.28 2002/04/08 22:59:26 hal9 Exp $</pubdate>
<authorgroup>
<author>
<para><emphasis>Example for file comments:</emphasis></para>
<programlisting>
-const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.27 2002/04/08 15:31:18 hal9 Exp $";
+const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.28 2002/04/08 22:59:26 hal9 Exp $";
/*********************************************************************
*
* File : $S<!-- Break CVS Substitution -->ource$
<programlisting>
#ifndef _FILENAME_H
#define _FILENAME_H
-#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.27 2002/04/08 15:31:18 hal9 Exp $"
+#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.28 2002/04/08 22:59:26 hal9 Exp $"
/*********************************************************************
*
* File : $S<!-- Break CVS Substitution -->ource$
Temple Place - Suite 330, Boston, MA 02111-1307, USA.
$Log: developer-manual.sgml,v $
+ Revision 1.28 2002/04/08 22:59:26 hal9
+ Version update. Spell chkconfig correctly :)
+
Revision 1.27 2002/04/08 15:31:18 hal9
Touch ups to documentation section.
<!entity contacting SYSTEM "contacting.sgml">
<!entity history SYSTEM "history.sgml">
<!entity copyright SYSTEM "copyright.sgml">
-<!entity p-version "2.9.14">
+<!entity p-version "2.9.13">
<!entity p-status "beta">
<!entity % p-not-stable "INCLUDE">
<!entity % p-stable "IGNORE">
This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: faq.sgml,v 1.45 2002/04/08 22:59:26 hal9 Exp $
+ $Id: faq.sgml,v 1.47 2002/04/10 04:05:32 hal9 Exp $
Written by and Copyright (C) 2001 the SourceForge
Privoxy team. http://www.privoxy.org/
<artheader>
<title>Privoxy Frequently Asked Questions</title>
-<pubdate>$Id: faq.sgml,v 1.45 2002/04/08 22:59:26 hal9 Exp $</pubdate>
+<pubdate>$Id: faq.sgml,v 1.47 2002/04/10 04:05:32 hal9 Exp $</pubdate>
<authorgroup>
<author>
Temple Place - Suite 330, Boston, MA 02111-1307, USA.
$Log: faq.sgml,v $
+Revision 1.47 2002/04/10 04:05:32 hal9
+More on BML, etc.
+
Revision 1.45 2002/04/08 22:59:26 hal9
Version update. Spell chkconfig correctly :)
This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: privoxy-man-page.sgml,v 1.2 2002/04/08 20:49:10 swa Exp $
+ $Id: privoxy-man-page.sgml,v 1.3 2002/04/08 22:59:26 hal9 Exp $
Written by and Copyright (C) 2001 the SourceForge
Privoxy team. http://www.privoxy.org/
<!entity seealso SYSTEM "seealso.sgml">
<!entity copyright SYSTEM "copyright.sgml">
<!entity authors SYSTEM "p-authors.sgml">
-<!entity p-version "2.9.14">
+<!entity p-version "2.9.13">
<!entity p-status "beta">
<!entity % p-not-stable "INCLUDE">
<!entity % p-stable "IGNORE">
<!entity p-intro SYSTEM "privoxy.sgml">
<!entity contacting SYSTEM "contacting.sgml">
<!entity buildsource SYSTEM "buildsource.sgml">
-<!entity p-version "2.9.14">
+<!entity p-version "2.9.13">
<!entity p-status "beta">
<!entity % p-not-stable "INCLUDE">
<!entity % p-stable "IGNORE">
Purpose : README for Privoxy
- $Id: readme.sgml,v 1.5 2002/04/08 20:49:38 swa Exp $
+ $Id: readme.sgml,v 1.6 2002/04/08 22:59:26 hal9 Exp $
Written by and Copyright (C) 2001 the SourceForge
Privoxy team. http://www.privoxy.org/
</LiteralLayout>
</para>
<para>
- $Id: readme.sgml,v 1.5 2002/04/08 20:49:38 swa Exp $
+ $Id: readme.sgml,v 1.6 2002/04/08 22:59:26 hal9 Exp $
</para>
</article>
<!entity contacting SYSTEM "contacting.sgml">
<!entity history SYSTEM "history.sgml">
<!entity copyright SYSTEM "copyright.sgml">
-<!entity p-version "2.9.14">
+<!entity p-version "2.9.13">
<!entity p-status "beta">
<!entity % p-not-stable "INCLUDE">
<!entity % p-stable "IGNORE">
This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: user-manual.sgml,v 1.71 2002/04/08 22:59:26 hal9 Exp $
+ $Id: user-manual.sgml,v 1.72 2002/04/10 04:06:19 hal9 Exp $
Written by and Copyright (C) 2001 the SourceForge
Privoxy team. http://www.privoxy.org/
<artheader>
<title>Privoxy User Manual</title>
-<pubdate>$Id: user-manual.sgml,v 1.71 2002/04/08 22:59:26 hal9 Exp $</pubdate>
+<pubdate>$Id: user-manual.sgml,v 1.72 2002/04/10 04:06:19 hal9 Exp $</pubdate>
<authorgroup>
<author>
Temple Place - Suite 330, Boston, MA 02111-1307, USA.
$Log: user-manual.sgml,v $
+ Revision 1.72 2002/04/10 04:06:19 hal9
+ Added actions feedback to Bookmarklets section
+
Revision 1.71 2002/04/08 22:59:26 hal9
Version update. Spell chkconfig correctly :)
By: Privoxy Developers
-$Id: developer-manual.sgml,v 1.27 2002/04/08 15:31:18 hal9 Exp $
+$Id: developer-manual.sgml,v 1.28 2002/04/08 22:59:26 hal9 Exp $
The developer manual gives the users information on how to help the developer
team. It provides guidance on coding, testing, documentation and other issues.
Some common elements that you likely will use:
-<para></para>, paragraph delimiter. Most text needs to be within paragraph
-elements (there are some exceptions).
-<emphasis></emphasis>, the stylesheets make this italics.
-<filename></filename>, files and directories.
-<command></command>, command examples.
-<literallayout></literllayout>, like <pre>, more or less.
-<itemizedlist></itemizdelist>, list with bullets.
-<listitem></listitem>, member of the above.
-<screen></screen>, screen output, implies <literallayout>.
-<ulink url="example.com"></ulink>, like HTML <a> tag.
-<quote></quote>, for, doh, quoting text.
+, paragraph delimiter. Most text needs to be within paragraph elements (there
+are some exceptions).
+, the stylesheets make this italics.
+, files and directories.
+, command examples.
+, like
+, more or less.
+, list with bullets.
+, member of the above.
+, screen output, implies .
+, like HTML tag.
+, for, doh, quoting text.
Look at any of the existing docs for examples of all these and more.
Example:
-#include <iostream.h> /* This is not a local include */
+#include /* This is not a local include */
#include "config.h" /* This IS a local include */
Exception:
/* This is not a local include, but requires a path element. */
-#include <sys/fileName.h>
+#include
Note: Please! do not add "-I." to the Makefile without a _very_ good reason.
This duplicates the #include "file.h" behaviour.
Example for file comments:
-const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.27 2002/04/08 15:31:18 hal9 Exp $";
+const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.28 2002/04/08 22:59:26 hal9 Exp $";
/*********************************************************************
*
* File : $Source$
#ifndef _FILENAME_H
#define _FILENAME_H
-#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.27 2002/04/08 15:31:18 hal9 Exp $"
+#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.28 2002/04/08 22:59:26 hal9 Exp $"
/*********************************************************************
*
* File : $Source$
* Use the Sourceforge Support Forum to get help:
- http://sourceforge.net/tracker/?group_id=11118&atid=211118
+ http://sourceforge.net/tracker/?group_id=11118&atid=211118
* Submit bugs only through our Sourceforge Bug Forum:
- http://sourceforge.net/tracker/?group_id=11118&atid=111118.
+ http://sourceforge.net/tracker/?group_id=11118&atid=111118.
Make sure that the bug has not already been submitted. Please try to verify
platform, browser, any pertinent log data, any other relevant details
(please be specific) and, if possible, some way to reproduce the bug.
- * Submit feature requests only through our Sourceforge feature request
- forum:
+ * Submit feature requests only through our Sourceforge feature request forum:
- http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse.
+ http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse.
- * We will soon have an automated way to submit advertisements, incorrectly
- blocked images, popups and the like. Check back.
+ * Submit missed ads and banners, and incorrectly blocked images, popups, etc:
+
+ http://p.p/, and select "actions file feedback system"
+ This page can also be reached from many of the internal CGI pages.
+
* For any other issues, feel free to use the mailing lists:
- http://sourceforge.net/mail/?group_id=11118.
+ http://sourceforge.net/mail/?group_id=11118.
Anyone interested in actively participating in development and related
Privoxy is evolved, and derived from, the Internet Junkbuster, with many
improvments and enhancements over the original.
-Junkbuster was originally written by Anonymous Coders and Junkbuster's
+Junkbuster was originally written by Anonymous Coders and Junkbusters
Corporation, and was released as free open-source software under the GNU GPL.
Stefan Waldherr made many improvements, and started the SourceForge project
Privoxy to rekindle development. There are now several active developers
http://p.p/, access Privoxy from your browser. Alternately, http://
config.privoxy.org may work in some situations where the first does not.
+http://p.p/, and select "actions file feedback system" to submit "misses" to
+the developers.
+
http://www.junkbusters.com/ht/en/cookies.html
http://www.waldherr.org/junkbuster/
By: Privoxy Developers
-$Id: faq.sgml,v 1.45 2002/04/08 22:59:26 hal9 Exp $
+$Id: faq.sgml,v 1.47 2002/04/10 04:05:32 hal9 Exp $
This FAQ gives users and developers alike answers to frequently asked questions
about Privoxy .
1.1. What is this new version of Privoxy?
-The original Internet JunkbusterTM (tm) is a copyrighted product of Junkbusters
-Corporation. Development of this effort stopped some time ago as of version
-2.0.2. Stefan Waldherr started the ijbswa project on Sourceforge to rekindle
-development. Other developers subsequently joined with Stefan, and have since
-added many new features, refinements and enhancements. The result of this
-effort is Privoxy.
+The original Internet Junkbuster™ (tm) is a copyrighted product of
+Junkbusters Corporation. Development of this effort stopped some time ago as of
+version 2.0.2. Stefan Waldherr started the ijbswa project on Sourceforge to
+rekindle development. Other developers subsequently joined with Stefan, and
+have since added many new features, refinements and enhancements. The result of
+this effort is Privoxy.
Privoxy has evolved from the Junkbuster 2.0.2 code base, and has advanced
significantly at this point.
If you have version 2.0.2, then the equivalent is http://example.com/
show-proxy-args (but you get far less information, and you should really
-consider upgrading to 2.9.14).
+consider upgrading to 2.9.13).
-------------------------------------------------------------------------------
By: Privoxy Developers
-$Id: user-manual.sgml,v 1.71 2002/04/08 22:59:26 hal9 Exp $
+$Id: user-manual.sgml,v 1.72 2002/04/10 04:06:19 hal9 Exp $
The user manual gives users information on how to install, configure and use
Privoxy.
1. Introduction
This documentation is included with the current beta version of Privoxy,
-v.2.9.14, and is mostly complete at this point. The most up to date reference
+v.2.9.13, and is mostly complete at this point. The most up to date reference
for the time being is still the comments in the source files and in the
individual configuration files. Development of version 3.0 is currently nearing
completion, and includes many significant changes and enhancements over earlier
To build Privoxy from source, autoconf and GNU make (gmake) are required.
Source is available as gzipped tar archives. For this, first unpack the source:
- tar xzvf privoxy-2.9.14-beta-src* [.tgz or .tar.gz]
- cd privoxy-2.9.14-beta
+ tar xzvf privoxy-2.9.13-beta-src* [.tgz or .tar.gz]
+ cd privoxy-2.9.13-beta
For retrieving the current CVS sources, you'll need the CVS package installed
This will create both binary and src RPMs in the usual places. Example:
- /usr/src/redhat/RPMS/i686/privoxy-2.9.14-1.i686.rpm
+ /usr/src/redhat/RPMS/i686/privoxy-2.9.13-1.i686.rpm
- /usr/src/redhat/SRPMS/privoxy-2.9.14-1.src.rpm
+ /usr/src/redhat/SRPMS/privoxy-2.9.13-1.src.rpm
To install, of course:
- rpm -Uvv /usr/src/redhat/RPMS/i686/privoxy-2.9.14-1.i686.rpm
+ rpm -Uvv /usr/src/redhat/RPMS/i686/privoxy-2.9.13-1.i686.rpm
This will place the Privoxy configuration files in /etc/privoxy/, and log files
This will create both binary and src RPMs in the usual places. Example:
- /usr/src/packages/RPMS/i686/privoxy-2.9.14-1.i686.rpm
+ /usr/src/packages/RPMS/i686/privoxy-2.9.13-1.i686.rpm
- /usr/src/packages/SRPMS/privoxy-2.9.14-1.src.rpm
+ /usr/src/packages/SRPMS/privoxy-2.9.13-1.src.rpm
To install, of course:
- rpm -Uvv /usr/src/packages/RPMS/i686/privoxy-2.9.14-1.i686.rpm
+ rpm -Uvv /usr/src/packages/RPMS/i686/privoxy-2.9.13-1.i686.rpm
This will place the Privoxy configuration files in /etc/privoxy/, and log files
Privoxy is packaged in a WarpIN self- installing archive. The self-installing
program will be named depending on the release version, something like:
-privoxyos2_setup_2.9.14.exe. In order to install it, simply run this executable
+privoxyos2_setup_2.9.13.exe. 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 Privoxy executable will be placed in your startup folder so it will
start automatically whenever OS/2 starts.
config.privoxy.org/), which is an internal page. You will see the following
section:
-Please choose from the following options:
+ Please choose from the following options:
* Show information about the current configuration
* Show the source code version numbers
it does nothing. Every action is disabled. This is not particularly informative
for our purposes here. OK, next section:
- Matches for http://google.com:
+ Matches for http://google.com:
{ -add-header -block +deanimate-gifs -downgrade +fast-redirects
+filter{html-annoyances} +filter{js-annoyances} +filter{no-popups}
And now we pull it altogether in the bottom section and summarize how Privoxy
is appying all its "actions" to "google.com":
- Final results:
+ Final results:
-add-header -block -deanimate-gifs -downgrade -fast-redirects
+filter{html-annoyances} +filter{js-annoyances} +filter{no-popups}
Now another example, "ad.doubleclick.net":
- { +block +image }
+ { +block +image }
.ad.doubleclick.net
{ +block +image }
One last example. Let's try "http://www.rhapsodyk.net/adsl/HOWTO/". This one is
giving us problems. We are getting a blank page. Hmmm...
- Matches for http://www.rhapsodyk.net/adsl/HOWTO/:
+ Matches for http://www.rhapsodyk.net/adsl/HOWTO/:
{ -add-header -block +deanimate-gifs -downgrade +fast-redirects
+filter{html-annoyances} +filter{js-annoyances} +filter{no-popups}
explictly does not block (-block) pages with "adsl". There are various ways to
handle such exceptions. Example:
- { -block }
+ { -block }
/adsl
But now what about a situation where we get no explicit matches like we did
with:
- { -block }
+ { -block }
/adsl
cause would be one of the "{+filter}" actions. Try adding the URL for the site
to one of aliases that turn off "+filter":
- {shop}
+ {shop}
.quietpc.com
.worldpay.com # for quietpc.com
.jungle.com
"{shop}" is an "alias" that expands to "{ -filter -no-cookies -no-cookies-keep
}". Or you could do your own exception to negate filtering:
- {-filter}
+ {-filter}
.forbes.com
><TD
> <I
CLASS="EMPHASIS"
-><itemizedlist></itemizedlist></I
+><itemizedlist></itemizdelist></I
>, list with bullets.
</TD
></TR
>
version string, e.g. <SPAN
CLASS="QUOTE"
->"2.9.14"</SPAN
+>"2.9.13"</SPAN
>.
</TD
></TR
>: the project status, either
<SPAN
CLASS="QUOTE"
->"alpha"</SPAN
+>"ALPHA"</SPAN
>, <SPAN
CLASS="QUOTE"
->"beta"</SPAN
+>"BETA"</SPAN
>, or <SPAN
CLASS="QUOTE"
->"stable"</SPAN
+>"STABLE"</SPAN
>.
</TD
></TR
>"not stable"</SPAN
> releases (e.g. <SPAN
CLASS="QUOTE"
->"beta"</SPAN
+>"BETA"</SPAN
>).
</TD
></TR
></DIV
><P
CLASS="PUBDATE"
->$Id: faq.sgml,v 1.45 2002/04/08 22:59:26 hal9 Exp $<BR></P
+>$Id: faq.sgml,v 1.47 2002/04/10 04:05:32 hal9 Exp $<BR></P
><DIV
><DIV
CLASS="ABSTRACT"
><P
> If you have version 2.0.2, then the equivalent is
http://example.com/show-proxy-args (but you get far less information, and
- you should really consider upgrading to 2.9.14).</P
+ you should really consider upgrading to 2.9.13).</P
></DIV
><DIV
CLASS="SECT2"
></DT
><DT
><A
-HREF="#AEN90"
+HREF="#AEN94"
>Copyright</A
></DT
><DT
><A
-HREF="#AEN97"
+HREF="#AEN101"
>History</A
></DT
></DL
CLASS="LITERALLAYOUT"
> Use the Sourceforge Support Forum to get help:<br>
<br>
- <A
+
<A
HREF="http://sourceforge.net/tracker/?group_id=11118&atid=211118"
TARGET="_top"
>http://sourceforge.net/tracker/?group_id=11118&atid=211118</A
CLASS="LITERALLAYOUT"
> Submit bugs only through our Sourceforge Bug Forum:<br>
<br>
- <A
+
<A
HREF="http://sourceforge.net/tracker/?group_id=11118&atid=111118"
TARGET="_top"
>http://sourceforge.net/tracker/?group_id=11118&atid=111118</A
><LI
><P
CLASS="LITERALLAYOUT"
-> Submit feature requests only through our Sourceforge feature request <br>
- forum:<br>
+> Submit feature requests only through our Sourceforge feature request forum:<br>
<br>
- <A
+
<A
HREF="http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse"
TARGET="_top"
>http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse</A
><LI
><P
CLASS="LITERALLAYOUT"
->We will soon have an automated way to submit advertisements, incorrectly<br>
-blocked images, popups and the like. Check back.<br>
+> Submit missed ads and banners, and incorrectly blocked images, popups, etc:<br>
+ <br>
+ <A
+HREF="http://p.p/"
+TARGET="_top"
+>http://p.p/</A
+>, and select <A
+HREF="javascript:w=Math.floor(screen.width/2);h=Math.floor(screen.height*0.9);void(window.open('http://www.privoxy.org/actions','Feedback','screenx='+w+',width='+w+',height='+h+',scrollbars=yes,toolbar=no,location=no,directories=no,status=no,menubar=no,copyhistory=no').focus());"
+TARGET="_top"
+><SPAN
+CLASS="QUOTE"
+>"actions file feedback system"</SPAN
+></A
+><br>
</P
+><P
+> This page can also be reached from many of the internal CGI pages.
+ </P
></LI
><LI
><P
CLASS="LITERALLAYOUT"
> For any other issues, feel free to use the mailing lists:<br>
<br>
- <A
+
<A
HREF="http://sourceforge.net/mail/?group_id=11118"
TARGET="_top"
>http://sourceforge.net/mail/?group_id=11118</A
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN90"
+NAME="AEN94"
>Copyright</A
></H1
><P
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN97"
+NAME="AEN101"
>History</A
></H1
><P
Coders and <A
HREF="http://www.junkbusters.com"
TARGET="_top"
->Junkbuster's
+>Junkbusters
Corporation</A
>, and was released as free open-source software under the
GNU GPL. <A
></DIV
><P
CLASS="PUBDATE"
->$Id: user-manual.sgml,v 1.71 2002/04/08 22:59:26 hal9 Exp $<BR></P
+>$Id: user-manual.sgml,v 1.72 2002/04/10 04:06:19 hal9 Exp $<BR></P
><DIV
><DIV
CLASS="ABSTRACT"
><TD
><PRE
CLASS="SCREEN"
-> tar xzvf privoxy-2.9.14-beta-src* [.tgz or .tar.gz]
- cd privoxy-2.9.14-beta
+> tar xzvf privoxy-2.9.13-beta-src* [.tgz or .tar.gz]
+ cd privoxy-2.9.13-beta
</PRE
></TD
></TR
><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
+> /usr/src/redhat/RPMS/i686/privoxy-2.9.13-1.i686.rpm</P
><P
-> /usr/src/redhat/SRPMS/privoxy-2.9.14-1.src.rpm</P
+> /usr/src/redhat/SRPMS/privoxy-2.9.13-1.src.rpm</P
><P
> To install, of course:</P
><P
><TD
><PRE
CLASS="SCREEN"
-> rpm -Uvv /usr/src/redhat/RPMS/i686/privoxy-2.9.14-1.i686.rpm
+> rpm -Uvv /usr/src/redhat/RPMS/i686/privoxy-2.9.13-1.i686.rpm
</PRE
></TD
></TR
><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
+> /usr/src/packages/RPMS/i686/privoxy-2.9.13-1.i686.rpm</P
><P
-> /usr/src/packages/SRPMS/privoxy-2.9.14-1.src.rpm</P
+> /usr/src/packages/SRPMS/privoxy-2.9.13-1.src.rpm</P
><P
> To install, of course:</P
><P
><TD
><PRE
CLASS="SCREEN"
-> rpm -Uvv /usr/src/packages/RPMS/i686/privoxy-2.9.14-1.i686.rpm
+> rpm -Uvv /usr/src/packages/RPMS/i686/privoxy-2.9.13-1.i686.rpm
</PRE
></TD
></TR
on the release version, something like:
<TT
CLASS="FILENAME"
->privoxyos2_setup_2.9.14.exe</TT
+>privoxyos2_setup_2.9.13.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
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->, v.2.9.14,
+>, v.2.9.13,
and is mostly complete at this point. The most up to date reference for the
time being is still the comments in the source files and in the individual
configuration files. Development of version 3.0 is currently nearing
projects / privoxy.git / commitdiff