Outdated files from doc/ folder removed

  Most of these  files were more than 15 years old, making them no
  longer valid or just simply outdated... Files removed:

   * changes.ipv6
   * ipv6-*.howto
   * sysvinitfiles

  Regarding the 'sysvinitfiles' -- the 'initscripts' package is nowadays
  intended for keeping the support for old init scripts still used
  somewhere. However, for creating new services people should use
  systemd now...

4 files changed, 0 insertions, 546 deletions

diff --git a/doc/changes.ipv6 b/doc/changes.ipv6
deleted file mode 100644
index 1970e98e..00000000
--- a/doc/changes.ipv6
+++ /dev/null
@@ -1,61 +0,0 @@
-v1.6 2nd Sep 2003, Pekka Savola <pekkas@netcore.fi>
-
-IPv6 CHANGES
-============
-
-This mentions the most important changes (visible to the administrator)
-in IPv6 initscripts.
-
-RHL9 -> CURRENT
----------------
-
- - no major functional changes, only bugfixes and cleanups
-
-RHL80 -> RHL9
--------------
-
- - 6to4 device MTU is calculated explicitly, IPV6TO4_MTU support added
- - add route6-<device> static route support
- - secondary IPv6 addresses are configurable on tunnel interfaces too
-
-RHL73 -> RHL80
---------------
-
- - no major functional changes
-
-RHL72 -> RHL73
---------------
-
- - 6to4 device changed from sit0 to tun6to4
- - 6to4 assumes the anycast (closest) 6to4 server is used (192.88.99.1)
-   unless specified with IPV6TO4_RELAY.
- - 6to4 does not support automatic tunneling *at all* anymore; use
-   IPV6_AUTOTUNNEL if you want to use it.
- - All support from NBMA tunnels as well as 6to4 using sit0 was removed
- - IPV6TO4_CONTROL_RADVD and IPV6TO4_RADVD_PIDFILE was changed to
-   IPV6_*, respectively.
- - IPV6_DEFAULTGW and IPV6_DEFAULTDEV support was introduced;
-   /etc/sysconfig/static-routes-ipv6 must not be used for them anymore.
-
-Rough guide to migration:
- - Rename IPV6TO4_CONTROL_RADVD to IPV6_CONTROL_RADVD if exists
- - Rename IPV6TO4_RADVD_PIDFILE to IPV6_RADVD_PIDFILE if exists
- - Remove "default" route from /etc/sysconfig/static-routes-ipv6 and replace
-   it with something like IPV6_DEFAULTDEV=tun6to4 in /etc/sysconfig/network
- - If you need autotunneling, use IPV6_AUTOTUNNEL in /etc/sysconfig/network
-
-RHL71 -> RHL72
---------------
-
- - 6to4 tunneling support was added using device sit0
- - Tunneling method was changed from NBMA (now obsolete) to dedicated
- - Automatic tunneling configured was moved from ifcfg-sit0 to
-   IPV6_AUTOTUNNEL at /etc/sysconfig/network
-
-
-
-Some more information
----------------------
-
-http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/scripts/current/ ,in particular:
-http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/scripts/current/index.html#migration
diff --git a/doc/ipv6-6to4.howto b/doc/ipv6-6to4.howto
deleted file mode 100644
index 131f4ce4..00000000
--- a/doc/ipv6-6to4.howto
+++ /dev/null
@@ -1,173 +0,0 @@
-v1.5 1st Sep 2003, Pekka Savola <pekkas@netcore.fi>
-
-HOW TO SET UP IPV6 WITH 6TO4
-----------------------------
-
-6TO4 IN SHORT
--------------
-
-6to4 is a method of creating automatic IPv6 tunnels.  You can connect to 
-IPv6 Internet very easily without a need for a manually configured tunnel.
-
-For every globally unique IPv4 address, there exists a mapping for a
-subnettable /48 network (2^16 for subnetting, 2^64 bits for hosts).
-
-Return route can sometimes be non-optimal, leading to higher round-trip times.
-
-See below for references and more information.
-
-ASSUMPTIONS
------------
-
-1. You're running Red Hat Linux 7.1 or later.
-   
-   This is required for correct IPv6 by default settings, and IPv6 being
-   enabled as a kernel module by default.  
-
-2. Your initscripts >= 6.02, for 6to4 support.
-
-3. You have a static, globally unique IPv4 address.  This is not an absolute
-   requirement, but the only scenario discussed here.
-
-4. Protocol 41 (IPv6-in-IPv4) is not being filtered in any IPv4 firewall.
-
-5. 'iproute' package is installed.  This is used by default for a lot 
-   more powerful tunneling capabilities.
-
-Note: even though 6to4 was supported with earlier releases of Red Hat Linux,
-below it is assumed that the initscripts package version this
-document comes with is used.
-
-INFORMATION NEEDED
-------------------
-
-Nothing :-).
-
-If you want to select a specific relay (rather than automatically
-selecting the closest one), you can define it with IPV6TO4_RELAY
-using the list below:
-
-http://www.kfu.com/~nsayer/6to4/
-
-SETTING UP THE 6TO4 CONFIGURATION
----------------------------------
-
-Now, set up the configuration as follows:
-
-1. Enable IPv6 and set 6to4 pseudo-interface as default gateway in 
-   /etc/sysconfig/network:
-
-   echo "IPV6_DEFAULTDEV=tun6to4">> /etc/sysconfig/network
-
-2. Edit your outbound (Internet) interface configuration.  This can be 
-   e.g. ippp0, ppp0, eth0, or the like. Here, eth1 is used.
-
-
-/etc/sysconfig/network-scripts/ifcfg-eth0:
----
-DEVICE=eth0
-BOOTPROTO=none
-ONBOOT=yes
-IPADDR=xx.yy.zz.ww           [Globally unique IPv4 address]
-NETMASK=aa.bb.cc.dd          [IPv4 settings up to this point]
-
-IPV6INIT=yes
-IPV6TO4INIT=yes
----
-
-   Note: [i]ppp - interfaces need to be called in /etc/ppp/ip-up|down.local;
-   if you are not using local files by yourself, this can easily be done with:
-
-    cd /etc/ppp
-    ln -s ip-up.ipv6to4 ip-up.local
-    ln -s ip-down.ipv6to4 ip-down.local
-
-
-USING 6TO4
-----------
-
-6to4 automatic tunneling is brought up when the interface is brought up.
-
-You will see your 6to4 address prefix in device tun6to4 when done:
-
-	inet6 addr: 2002:c15e:a001::1/16 Scope:Global
-
-Note that 'c15e:a001' is the hexadecimal representation of dotted-quad IPv4
-address (IPADDR= above), here '193.94.160.1'.
-
-NOTE: iproute tools give more reliable data, try e.g. '/sbin/ip addr ls'.
-
-PROVIDING IPV6 TO YOUR LAN
---------------------------
-
-If you want to provide IPv6 for your LAN (e.g. connected on eth1)
-using your Linux system as a router, this can be done rather easily with 6to4.
-
-You will need to enable IPv6 forwarding (IPV6FORWARDING=yes in
-/etc/sysconfig/network) and install a router advertisement daemon.  One such,
-'radvd' is available in the distribution.  
-
-You must configure the prefix your IPv4 maps to (see tun6to4 above) in 
-/etc/radvd.conf or use certain automatic hooks.  This is not covered here 
-in detail; see radvd.conf(5) and /etc/sysconfig/network-scripts/ifup-ipv6 
-for details.
-
-Usually the following is enough:
-
-1. Make sure that radvd package is installed.
-
-2. Configure radvd as outlined in radvd.conf(5); the file could
-   be something like:
-
-   interface eth1
-   {
-	AdvSendAdvert on;
-	MinRtrAdvInterval 3;
-	MaxRtrAdvInterval 10;
-	prefix 0:0:0:1::/64
-	{
-		Base6to4Interface eth0;
-		AdvPreferredLifetime 120;
-		AdvValidLifetime 300;
-	};
-   };
-
-3. Make sure radvd starts at boot and start it now:
-
-   /sbin/chkconfig radvd on
-   /sbin/service radvd start 
-
-4. Make the initscripts signal radvd to recalculate the prefix when it
-   changes:
-
-  /etc/sysconfig/network-scripts/ifcfg-eth0:
-
-  IPV6_CONTROL_RADVD=yes
-
-5. Configure the associated routes to other 6to4 subnets to point at 
-   your LAN interfaces; this can be done automatically with 
-   IPV6TO4_ROUTING variable; please refer sysconfig.txt for details.
-   In the particular example, above, this would be like:
-
-  /etc/sysconfig/network-scripts/ifcfg-eth0:
-
-  IPV6TO4_ROUTING="eth1-:1::0/64"
-
-   However, please note that no global address is configured on the
-   interface, just a route!
-
-MORE INFORMATION
-----------------
-
-http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO.html is a good
-source of IPv6 related Linux-information.
-
-ftp://ftp.isi.edu/in-notes/rfc3056.txt ("Connection of IPv6 Domains via IPv4
-Clouds") is the RFC about 6to4.
-
-ftp://ftp.isi.edu/in-notes/rfc3068.txt ("An Anycast Prefix for 6to4 Relay
-Routers") is the RFC about finding a close 6to4 relay automatically.
-
-http://www.ietf.org/internet-drafts/draft-savola-v6ops-6to4-security-02.txt
-("Security Considerations and Enhancements for 6to4") explains some
-security considerations in 6to4.
diff --git a/doc/ipv6-tunnel.howto b/doc/ipv6-tunnel.howto
deleted file mode 100644
index ac5de0dc..00000000
--- a/doc/ipv6-tunnel.howto
+++ /dev/null
@@ -1,100 +0,0 @@
-v1.4 10th Jan 2002, Pekka Savola <pekkas@netcore.fi>
-
-HOW TO SET UP AN IPV6 TUNNEL
-----------------------------
-
-ASSUMPTIONS
------------
-
-1. You're running Red Hat Linux 7.1 or later.
-   
-   This is required for correct IPv6 by default settings, and IPv6 being
-   enabled as a kernel module by default.  You also need recent enough
-   initscripts, provided in RHL71.
-
-2. You have a static, globally unique IPv4 address.
-
-3. Protocol 41 (IPv6-in-IPv4) is not being filtered in any IPv4 firewall.
-
-4. 'iproute' package is installed.  This is used by default for a lot 
-   more powerful tunneling capabilities.
-
-INFORMATION NEEDED
-------------------
-
-You need to know:
-
-1. The IPv4 address of your tunnel end point
-2. The IPv6 address used in your tunnel
-
-The other end needs to know the same things about your setup.
-
-NOTE: It is also possible to set up unnumbered tunnels (no global IPv6
-addresses).
-
-You must get these from a party (tunnel broker) who's assigning IPv6 tunnels.  See:
-http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO-1.html#joinIPv6backbone
-
-Example from http://old.freenet6.net:
----
-This script will create a tunnel between this computer
-and the Freenet6 server (tunnels server)
-Your IPv6 address (your tunnel end point) is
-3ffe:b00:c18:1fff:0:0:0:7f5 
-We establish a tunnel to the Freenet6 server at
-3ffe:b00:c18:1fff:0:0:0:7f4 
-Your IPv4 address is : 193.xxx.yyy.zzz 
-The IPv4 address of the Freenet6 server is : 206.123.31.102 
----
-
-With this information, a tunnel can be set up:
-
-SETTING UP THE TUNNEL CONFIGURATION
------------------------------------
-
-Now, set up the configuration as follows:
-
-1. Enable IPv6 and set tunnel as default gateway in /etc/sysconfig/network:
-
-   echo "IPV6_DEFAULTDEV=sit1">> /etc/sysconfig/network
-
-2. Create /etc/sysconfig/network-scripts/ifcfg-sit1, with the following:
-
----
-DEVICE=sit1
-BOOTPROTO=none
-ONBOOT=yes
-IPV6INIT=yes
-IPV6TUNNELIPV4=206.123.31.102
-IPV6ADDR=3ffe:b00:c18:1fff:0:0:0:7f5/128
----
-
-NOTE: You must use _sit1_ (or sit2,...).  sit0 cannot be used, this is a
-special device.
-
-NOTE: Some tunnel endpoints might require a different kind of prefix length;
-for example, Cisco's usually favour /126.  Using /0 creates a default route 
-through that interface.
-
-NOTE: If you're not directly connected to the Internet, you may want to use
-ONBOOT=no instead.
-
-TUNNELING
----------
-
-Tunnel can be brought up and down with:
-
-   ifup sit1
-   ifdown sit1
-
-NOTE: In initscripts < 6.02 (ie. IPV6_TUNNELMODE=NBMA), even though sit1 is used, 
-'ip' sees the tunnel as sit0.  This is due to an "interesting" implementation 
-of tunneling -- else multiple tunnels couldn't be used extensibly.
-
-NOTE: iproute tools give more reliable data, try e.g. '/sbin/ip addr ls'.
-
-MORE INFORMATION
-----------------
-
-http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO.html is a good
-source of IPv6 related Linux-information.
diff --git a/doc/sysvinitfiles b/doc/sysvinitfiles
deleted file mode 100644
index fcc90b5e..00000000
--- a/doc/sysvinitfiles
+++ /dev/null
@@ -1,212 +0,0 @@
-Writing System V init scripts for Red Hat Linux
-===============================================
-
-All System V init scripts are named /etc/rc.d/init.d/<servicename>
-where <servicename> is the name of the service.  There must be no
-".init" suffix.
-
-This path will very likely be moved to /etc/init.d in the future.
-Once Red Hat Linux 7.0 is installed, you can access scripts as
-/etc/init.d/<servicename>, via symlinks.
-
-Sample Script
-=============
-
-#!/bin/bash
-#
-#	/etc/rc.d/init.d/<servicename>
-#
-#	<description of the *service*>
-#	<any general comments about this init script>
-#
-# <tags -- see below for tag definitions.  *Every line* from the top
-#  of the file to the end of the tags section must begin with a #
-#  character.  After the tags section, there should be a blank line.
-#  This keeps normal comments in the rest of the file from being
-#  mistaken for tags, should they happen to fit the pattern.>
-
-# Source function library.
-. /etc/init.d/functions
-
-<define any local shell functions used by the code that follows>
-
-start() {
-	echo -n "Starting <servicename>: "
-	<start daemons, perhaps with the daemon function>
-	touch /var/lock/subsys/<servicename>
-	return <return code of starting daemon>
-}	
-
-stop() {
-	echo -n "Shutting down <servicename>: "
-	<stop daemons, perhaps with the killproc function>
-	rm -f /var/lock/subsys/<servicename>
-	return <return code of stopping daemon>
-}
-
-case "$1" in
-    start)
-	start
-	;;
-    stop)
-	stop
-	;;
-    status)
-	<report the status of the daemons in free-form format,
-	perhaps with the status function>
-	;;
-    restart)
-    	stop
-	start
-	;;
-    reload)
-	<cause the service configuration to be reread, either with
-	kill -HUP or by restarting the daemons, in a manner similar
-	to restart above>
-	;;
-    condrestart)
-    	<Restarts the servce if it is already running. For example:>
-	[ -f /var/lock/subsys/<service> ] && restart || :
-    probe)
-	<optional.  If it exists, then it should determine whether
-	or not the service needs to be restarted or reloaded (or
-	whatever) in order to activate any changes in the configuration
-	scripts.  It should print out a list of commands to give to
-	$0; see the description under the probe tag below.>
-	;;
-    *)
-	echo "Usage: <servicename> {start|stop|status|reload|restart[|probe]"
-	exit 1
-	;;
-esac
-exit $?
-
-Notes: 
-
-- The restart and reload functions may be (and commonly are)
-  combined into one test, vis:
-    restart|reload)
-- You are not prohibited from adding other commands; list all commands
-  which you intend to be used interactively to the usage message.
-- Notice the change in that stop() and start() are now shell functions.
-  This means that restart can be implemented as
-     stop
-     start
-  instead of
-     $0 stop
-     $0 start
-  This saves a few shell invocations.
-
-Functions in /etc/init.d/functions
-=======================================
-
-daemon  [ --check <name> ] [ --user <username>] 
-	[+/-nicelevel] program [arguments] [&]
-
-	Starts a daemon, if it is not already running.  Does
-	other useful things like keeping the daemon from dumping
-	core if it terminates unexpectedly.
-	
-	--check <name>:
-	   Check that <name> is running, as opposed to simply the
-	   first argument passed to daemon().
-	--user <username>:
-	   Run command as user <username>
-
-killproc program [signal]
-
-	Sends a signal to the program; by default it sends a SIGTERM,
-	and if the process doesn't die, it sends a SIGKILL a few
-	seconds later.
-
-	It also tries to remove the pidfile, if it finds one.
-
-pidofproc program
-
-	Tries to find the pid of a program; checking likely pidfiles,
-	and using the pidof program.  Used mainly from within other
-	functions in this file, but also available to scripts.
-
-status program
-
-	Prints status information.  Assumes that the program name is
-	the same as the servicename.
-
-
-Tags
-====
-
-# chkconfig: <startlevellist> <startpriority> <endpriority>
-
-	Required.  <startlevellist> is a list of levels in which
-	the service should be started by default.  <startpriority>
-	and <endpriority> are priority numbers.  For example:
-	# chkconfig: 2345 20 80
-	Read 'man chkconfig' for more information.
-
-	Unless there is a VERY GOOD, EXPLICIT reason to the
-	contrary, the <endpriority> should be equal to
-	100 - <startpriority>
-	
-# description: <multi-line description of service>
-
-	Required.  Several lines of description, continued with '\'
-	characters.  The initial comment and following whitespace
-	on the following lines is ignored.
-
-# description[ln]: <multi-line description of service in the language \
-#                  ln, whatever that is>
-
-	Optional.  Should be the description translated into the
-	specified language.
-
-# processname:
-
-	Optional, multiple entries allowed.  For each process name
-	started by the script, there should be a processname entry.
-	For example, the samba service starts two daemons:
-	# processname: smdb
-	# processname: nmdb
-
-# config:
-
-	Optional, multiple entries allowed.  For each static config
-	file used by the daemon, use a single entry.  For example:
-	# config: /etc/httpd/conf/httpd.conf
-	# config: /etc/httpd/conf/srm.conf
-
-	Optionally, if the server will automatically reload the config
-	file if it is changed, you can append the word "autoreload" to
-	the line:
-	# config: /etc/foobar.conf autoreload
-
-# pidfile:
-
-	Optional, multiple entries allowed.  Use just like the config
-	entry, except that it points at pidfiles.  It is assumed that
-	the pidfiles are only updated at process creation time, and
-	not later.  The first line of this file should be the ASCII
-	representation of the PID; a terminating newline is optional.
-	Any lines other than the first line are not examined.
-
-# probe: true
-
-	Optional, used IN PLACE of processname, config, and pidfile.
-	If it exists, then a proper reload-if-necessary cycle may be
-	achieved by running these commands:
-
-	command=$(/etc/rc.d/init.d/SCRIPT probe)
-	[ -n "$command" ] && /etc/rc.d/init.d/SCRIPT $command
-
-	where SCRIPT is the name of the service's sysv init script.
-
-	Scripts that need to do complex processing could, as an
-	example, return "run /var/tmp/<servicename.probe.$$"
-	and implement a "run" command which would execute the
-	named script and then remove it.
-
-	Note that the probe command should simply "exit 0" if nothing
-	needs to be done to bring the service into sync with its
-	configuration files.
-
-Copyright (c) 2000 Red Hat Software, Inc.