<!entity p-intro SYSTEM "privoxy.sgml">
<!entity contacting SYSTEM "contacting.sgml">
<!entity buildsource SYSTEM "buildsource.sgml">
-<!entity p-version "3.0.4">
-<!entity p-status "beta">
-<!entity % p-not-stable "INCLUDE">
-<!entity % p-stable "IGNORE">
+<!entity p-version "3.0.11">
+<!entity p-status "stable">
+<!entity % p-not-stable "IGNORE">
+<!entity % p-stable "INCLUDE">
<!entity % p-text "INCLUDE"> <!-- define we are a text only doc -->
<!entity % p-doc "IGNORE"> <!-- and never a text doc -->
<!entity % p-readme "INCLUDE"> <!-- all your README belong to us -->
Purpose : README for Privoxy
- $Id: readme.sgml,v 2.5 2006/07/18 14:48:51 david__schmidt Exp $
+ $Id: readme.sgml,v 2.23 2009/02/16 03:22:01 hal9 Exp $
- Copyright (C) 2001 - 2006 Privoxy Developers <developers@privoxy.org>
+ Copyright (C) 2001-2009 Privoxy Developers http://www.privoxy.org/
See LICENSE.
========================================================================
*
* Purpose : README file to give a short intro.
*
- * Copyright : Written by and Copyright (C) 2001 - 2006 the SourceForge
+ * Copyright : Written by and Copyright (C) 2001-2009 the SourceForge
* Privoxy team. http://www.privoxy.org/
*
* Based on the Internet Junkbuster originally written
* The GNU General Public License should be included with
* this file. If not, you can view it at
* http://www.gnu.org/copyleft/gpl.html
- * or write to the Free Software Foundation, Inc., 59
- * Temple Place - Suite 330, Boston, MA 02111-1307, USA.
+ * or write to the Free Software Foundation, Inc.,
+ * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
+ * USA
*
*********************************************************************/
</literallayout>
<!-- ~~~~~ New section ~~~~~ -->
<sect1 id="importantchanges" ><title>IMPORTANT CHANGES</title>
<para>
- BIG NEWS! 2006, Privoxy 3.0.4 is released. This is a significant upgrade
- with many new and enhanced features, and many bugs fixed. There
- are fifteen new actions available, and several actions have enhanced
- capabilites. Multiple filter files are now supported as well. See the "What's
- New" section and the "Upgrader's Notes" in <citetitle>the User
- Manual</citetitle> for details and specifics.
+ February 2009, Privoxy 3.0.11 is released.
</para>
<para>
- NEWS! January 2004, Privoxy 3.0.3 is released. This is the another
- maintenance release of Privoxy which fixes more bugs, further refines
- the configuration and works around some known third-party problems. See the
- ChangeLog for complete details. Upgrading from 3.0.2 is recommended.
+ As usual there are changes that effect the configuration. See the "ChangeLog",
+ and the "What's New" section and the "Upgrader's Notes" in
+ <citetitle>the User Manual</citetitle> for details and specifics.
</para>
<para>
- NEWS! March 2003, Privoxy 3.0.2 is released. This is the first maintenance
- release of Privoxy. There are no significant new features in this release.
- Some bugs are fixed, and some existing features have been enhanced. See
- ChangeLog for details. Upgrading from 3.0.0 is recommended.
+ This is a stable release, and marks a departure for Privoxy development.
</para>
<para>
- REALLY BIG NEWS! August 2002: The long-awaited, oft-delayed stable version
- of Privoxy 3.0 is finally released! This is way behind schedule, but better
- late than never. The developers all hope the wait was worth it.
-</para>
-<para>
- NEWS! As of 03/24/02, the name of this project has been changed from
- ijbswa/Junkbuster to Privoxy. This is reflected in many of the included
- files.
-</para>
-<para>
- IMPORTANT! READ! Configuration Change as of 17 Mar 2002: The default listening
- port is now 8118 due to conflicts with port 8000 assignment. You will need to
- change your browser if upgrading!!! And maybe firewall, etc.
+ Previously, odd numbered releases were considered beta versions and
+ were only released at the end of the development cycle when the code
+ was already believed to be stable. Usually it was, so the stable release
+ contained pretty much the same code, but got a higher version number.
+ In the future we intend to release several snapshots between stable releases.
+ There will probably still be about two stable releases per year,
+ but hopefully about six snapshots instead of the two betas we have now.
+ The intentions is to make testing without CVS access easier.
</para>
</sect1>
<!-- ~~~~~ New section ~~~~~ -->
<sect1 id="run"><title>RUN</title>
<para>
- privoxy [——help] [——version]
- [——no-daemon] [——pidfile PIDFILE] [——user
- USER[.GROUP]] [——chroot] [config_file]
+ privoxy [--help] [--version]
+ [--no-daemon] [--pidfile PIDFILE] [--user USER[.GROUP]] [--chroot] [--pre-chroot-nslookup
+ HOSTNAME ][config_file]
</para>
<para>
See the man page or <citetitle>User Manual</citetitle> for an explanation of each option, and
for 'config.txt'). If no config_file is found, Privoxy will fail to start.
</para>
<para>
- Or for Red Hat based distributions: /etc/rc.d/init.d/privoxy start
-</para>
-<para>
- Or for SuSE: /etc/rc.d/privoxy start
+ Or for Red Hat and Fedora based distributions: /etc/rc.d/init.d/privoxy start
</para>
<para>
- Or Debian: /etc/init.d/privoxy start
+ Or Debian and Ubuntu: /etc/init.d/privoxy start
</para>
</sect1>
'user.filter'. 'user.action' and 'user.filter' are for personal and local
configuration preferences. These are all well commented. Most of the magic is
in '*.action' files. 'user.action' should be used for any actions
- customizations. On Unix-like systems, these files are installed in
+ customizations. On Unix-like systems, these files are typically installed in
/etc/privoxy. On Windows, then wherever the executable itself is installed.
There are many significant changes and advances from earlier versions. The
<citetitle>User Manual</citetitle> has an explanation of all configuration
may still be either comments in the source code, or the included
configuration files. ]]>The source and configuration files are all well
commented. The main configuration files are: 'config', 'default.action', and
- 'default.filter'<![%p-not-stable;[ in the toplevel source directory]]>.
+ 'default.filter'<![%p-not-stable;[ in the top-level source directory]]>.
</para>
<para>
<!-- </LiteralLayout> -->
<!-- </para> -->
<!-- <para> -->
-<!-- $Id: readme.sgml,v 2.5 2006/07/18 14:48:51 david__schmidt Exp $ -->
+<!-- $Id: readme.sgml,v 2.23 2009/02/16 03:22:01 hal9 Exp $ -->
<!-- </para> -->
</article>