head	1.14;
access;
symbols;
locks
	alexis:1.14; strict;
comment	@# @;


1.14
date	98.10.07.16.44.36;	author alexis;	state Exp;
branches;
next	1.13;

1.13
date	98.08.29.16.45.45;	author alexis;	state Exp;
branches;
next	1.12;

1.12
date	98.08.28.17.42.33;	author alexis;	state Exp;
branches;
next	1.11;

1.11
date	98.08.28.13.22.17;	author alexis;	state Exp;
branches;
next	;


desc
@SHPP PORT OF INSTALL.in VER 1.10
@


1.14
log
@documented necessary changes to /etc/named.conf
@
text
@------------------------------------------------------------------------------
Title:   INSTALLATION INSTRUCTIONS FOR FAD RELEASE PATCHLEVEL_MARKER
Version: $Id: INSTALL.shpp,v 1.13 1998/08/29 16:45:45 alexis Exp alexis $
------------------------------------------------------------------------------

0a.	These instructions contain absolute and relative pathnames. The
	relative pathnames are relative with respect to the subdirectory
	created by the unpacking process (i.e. cd to where this INSTALL file
	is and then cd up one. View this file as doc/INSTALL.

0b.	If you are a source distribution of ppplc, then don't 
	bother printing these instructions yet. The first couple of 
	instructions actually modify this file!

0c.	If you have a binary distribution of ppplc, then go straight to
	step 3b.

1.	Work your way through ./Makefile.defs changing things as instructed
	there.

2.	As non-root run:

	make

	If you are viewing file ./doc/INSTALL.in, then at this point, quit
	out of your viewer and view ./doc/INSTALL instead, continuing at
	instruction 3a.
	
	(this 'make' instruction actually alters *this* file!)

3a.	As root run:

	make install

3b.	As root run:

        mv /etc/ppp /etc/ppp.old
        mkdir /etc/ppp
	ln -s PRGLIBDIR_MARKER/misc/ip-up /etc/ppp/ip-up
	ln -s PRGLIBDIR_MARKER/misc/ip-down /etc/ppp/ip-down
	ln -s PRGLIBDIR_MARKER/misc/options /etc/ppp/options
	cp doc/examples/ppplcd.conf PRGCFGDIR_MARKER

4.	If you run a System V style 'init' (does /etc/init.d exist?) then:

		you may run the following as root 
	
			cp doc/examples/local-ppplc /etc/init.d
			ln -s /etc/init.d/local-ppplc /etc/rc0.d/K01local-ppplc
			ln -s /etc/init.d/local-ppplc /etc/rc6.d/K01local-ppplc

		As root run the following commands (if the runlevels to invoke 
		the daemon on are not '2' and '3' then modify) :

			ln -s /etc/init.d/local-ppplc /etc/rc2.d/S99local-ppplc
			ln -s /etc/init.d/local-ppplc /etc/rc3.d/S99local-ppplc

5.	If you are running a 'simple style 'init' (does /etc/rc.local or
	/etc/rc.d/rc.local exist?) then:

		Add the following lines to that file:

			PPPLCD=LCLSBINDIR_MARKER/ppplcd
			CONFIG=PRGCFGDIR_MARKER/ppplcd.conf
        		echo "Starting ppplcd"
                        rm -f LOCK_DIR_MARKER/ppplcd.*
			if [ ! -x $PPPLCD ]; then
            		    echo "$PPPLCD: not found"
        		elif [ ! -r $CONFIG ]; then
            		    echo "$CONFIG: not found"
        		else
            		    $PPPLCD $CONFIG > /dev/null 2>&1
        		fi

6a.	After that there is only one more step, and that is review the 
	configuration file - PRGCFGDIR_MARKER/ppplcd.conf - checking and
	possibly changing certain parts. Consult the manual pages for
	ppplcd.conf(5) for further information.

	Note that if your modem is *NOT* a US Robotics Courier or your
	ISP is *NOT* Demon, then this configuration will require you to
	write chat scripts for your modem or ISP, but that will become
	clearer as you work through the config file. (Please please
	please send any new modem or ISP configuration files you write
	to the author for inclusion in the next release.)

6b.	If you intend to make use of the name service switcher then you will 	
	need to make two copies of /etc/named.conf - calling them
	/etc/named.conf.local and /etc/named.conf.inet and then remove
	the original /etc/named.conf.  It is entirely up to you what
	goes into each version. Bear in mind that the .inet one is
	symlinked to /etc/named.conf when the ppp connection comes up
	and the other one is symlinked when the ppp connection comes
	down. In both cases named is restarted afterwards.

7.	Consult the manual page for ppplcc(1) for further information on 
	actually connecting.

8.	An example crontab entry you may wish to add to root's crontab can be 
	found in ./doc/examples.

------------------------------------------------------------------------------
@


1.13
log
@corrected paths in documenting installating of /etc/ppp/ip-*
	(the real scripts moved from ./lib to ./lib/misc
@
text
@d3 1
a3 1
Version: $Id: INSTALL.shpp,v 1.12 1998/08/28 17:42:33 alexis Exp alexis $
d75 1
a75 1
6.	After that there is only one more step, and that is review the 
d83 12
a94 3
	clearer as you work through the config file. (Please please please
	send any new modem or ISP configuration files you write to the
	author for inclusion in the next release.)
@


1.12
log
@FSSTND'd
@
text
@d3 1
a3 1
Version: $Id: INSTALL.shpp,v 1.11 1998/08/28 13:22:17 alexis Exp alexis $
d39 3
a41 3
	ln -s PRGLIBDIR_MARKER/ip-up /etc/ppp/ip-up
	ln -s PRGLIBDIR_MARKER/ip-down /etc/ppp/ip-down
	ln -s PRGLIBDIR_MARKER/options /etc/ppp/options
@


1.11
log
@milestone
@
text
@d3 1
a3 1
Version: $Id: INSTALL.in,v 1.10 1998/08/27 15:22:16 alexis Exp $
d42 1
a42 1
	cp doc/examples/ppplc.cfg /usr/local/etc
d64 1
a64 1
			CONFIG=PRGCFGDIR_MARKER/ppplc.cfg
d66 1
a66 1
                        rm -f LOCKDIR_MARKER/ppplcd.*
d76 1
a76 1
	configuration file - PRGCFGDIR_MARKER/ppplc.cfg - checking and
d78 1
a78 1
	ppplc.cfg(4) for further information.
@