![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to isode-gen.8 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta|
Return to isode-gen.8 CVS log | Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta |
1.1 root 1: .TH ISODE-GEN 8 "27 Jul 1990"
2: .ds VD isode\-6.6/
3: .ds VN 6.6
4: .\" $Header: /f/osi/RCS/isode-gen.8,v 7.21 90/07/27 08:52:25 mrose Exp $
5: .\"
6: .\"
7: .\" $Log: isode-gen.8,v $
8: .\" Revision 7.21 90/07/27 08:52:25 mrose
9: .\" 6.6
10: .\"
11: .\" Revision 7.20 90/07/27 08:49:45 mrose
12: .\" update
13: .\"
14: .\" Revision 7.19 90/07/09 14:42:51 mrose
15: .\" 6.5
16: .\"
17: .\" Revision 7.18 90/07/09 14:30:14 mrose
18: .\" sync
19: .\"
20: .\" Revision 7.17 90/04/18 10:23:25 mrose
21: .\" 6.2
22: .\"
23: .\" Revision 7.16 90/04/18 08:52:33 mrose
24: .\" MANDIR
25: .\"
26: .\" Revision 7.15 90/04/09 08:49:53 mrose
27: .\" update
28: .\"
29: .\" Revision 7.14 90/03/05 23:04:15 mrose
30: .\" touch-up
31: .\"
32: .\" Revision 7.13 90/02/19 13:07:36 mrose
33: .\" update
34: .\"
35: .\" Revision 7.12 90/01/27 10:27:48 mrose
36: .\" touch-up
37: .\"
38: .\" Revision 7.11 90/01/11 19:35:47 mrose
39: .\" again
40: .\"
41: .\" Revision 7.10 90/01/11 18:33:48 mrose
42: .\" real-sync
43: .\"
44: .\" Revision 7.9 89/12/19 23:40:40 mrose
45: .\" again
46: .\"
47: .\" Revision 7.8 89/12/19 23:37:41 mrose
48: .\" again
49: .\"
50: .\" Revision 7.7 89/12/19 23:36:12 mrose
51: .\" again
52: .\"
53: .\" Revision 7.6 89/12/19 23:34:33 mrose
54: .\" again
55: .\"
56: .\" Revision 7.5 89/12/19 23:32:22 mrose
57: .\" again
58: .\"
59: .\" Revision 7.4 89/12/19 09:52:43 mrose
60: .\" 5.9
61: .\"
62: .\" Revision 7.3 89/12/04 18:18:09 mrose
63: .\" 5.8b
64: .\"
65: .\" Revision 7.2 89/11/30 23:50:49 mrose
66: .\" typos
67: .\"
68: .\" Revision 7.1 89/11/24 13:33:10 mrose
69: .\" sync
70: .\"
71: .\" Revision 7.0 89/11/23 21:21:30 mrose
72: .\" Release 6.0
73: .\"
74: .SH NAME
75: isode\-gen \- generating the ISO Development Environment
76: .SH "READ THIS"
77: This documentation describes how to configure, generate, and install the
78: ISO Development Environment.
79: .PP
80: Acquisition, use, and distribution of this module and related
81: materials are subject to the restrictions of a license agreement.
82: Consult the Preface in the \fIUser's Manual\fR for the full terms of this
83: agreement.
84: .PP
85: You will probably want to read over this entire document first,
86: before typing any commands;
87: e.g., there are optional components described later on that require
88: additional settings in the configuration file.
89: .PP
90: Comments concerning this release should be directed to the authors.
91: Consult the preface in the \fIUser's Manual\fR for a current postal address.
92: Alternately,
93: if you have access to the Internet,
94: comments may be sent to the mailbox \*(lqBug\[email protected]\*(rq.
95: Do \fBnot\fR send bug reports to the ISODE discussion group.
96: If you want to subscribe to the ISODE discussion group, drop a note to
97: \*([email protected]\*(rq.
98: .SH SYNOPSIS
99: .sp
100: .in +.5i
101: .nf
102: % cd \*(VD
103: % cp config/\fIsystem\fR.h h/config.h
104: % cp config/\fIsystem\fR.make config/CONFIG.make
105: % cp config/*.local support/
106: % make everything
107: # make inst\-everything
108: .fi
109: .in -.5i
110: .sp
111: .SH DESCRIPTION
112: This is a description of how one can bring up the ISODE.
113: It is assumed that you have super\-user privileges in order to (re\-)install
114: the software.
115: Super\-user privileges are not required to configure or generate this
116: software.
117: .PP
118: The distribution tape contains the hierarchy for the \fB\*(VD\fR directory.
119: Bring the sources on\-line by changing to a directory for local sources and
120: running tar, e.g.,
121: .sp
122: .in +.5i
123: .nf
124: % cd /usr/src/local/
125: % tar x
126: % cd \*(VD
127: .fi
128: .in -.5i
129: .sp
130: .SH CONFIGURATION
131: First, go to the \fBconfig/\fR directory.
132: .sp
133: .in +.5i
134: .nf
135: % cd config
136: .fi
137: .in -.5i
138: .sp
139: .PP
140: Select the Makefile and include-file skeletons which most closely match
141: your system.
142: The current choices are:
143: .sp
144: .in +.5i
145: .nf
146: .ta \w'sys52-exos 'u
147: .ne 4
148: \fIfile\fR \fIconfiguration\fR
149: apollo Apollo
150: aux A/UX release 1.1
151: bsd42 generic 4.2BSD UNIX
152: bsd43 generic 4.3BSD UNIX
153: bsd43\-rt RT/PC with 4.3BSD
154: bsd44 4.4BSD UNIX with OSI
155: hpux HP\-UX
156: mips MIPS RISC/OS
157: osx Olivetti LSX 30xx
158: ros Ridge Operating System
159: sunlink3 SunOS release 3 with SunLink OSI release 5.2
160: sunlink4 SunOS release 4 with SunLink OSI release 6.0
161: sunos3 SunOS release 3
162: sunos4 SunOS release 4
163: sys52\-exos SVR2 UNIX with EXOS
164: sys52\-rt RT/PC with AIX
165: sys52\-sun SVR2 UNIX emulation on SunOS release 3
166: sys52\-win SVR2 UNIX with WIN/TCP
167: sys53 generic SVR3
168: ultrix Ultrix 3.1
169: .re
170: .fi
171: .in -.5i
172: .sp
173: The makefile skeleton has the extension \fB.make\fR,
174: whereas the include\-file skeleton has the extension \fB.h\fR.
175: .SS MAKEFILE
176: Copy the makefile skeleton of your choice to \fBpickle.make\fR,
177: where \*(lqpickle\*(rq is the name of your system.
178: Now edit this file to set the following \fImake\fR variables:
179: .sp
180: .in +.5i
181: .nf
182: .ta \w'MANOPTS 'u +\w'/usr/include/isode/ 'u
183: .ne 8
184: \fIvariable\fR \fIdefault\fR \fIspecifies\fR
185: OPTIONS options to \fIcc\fR and \fIlint\fR (e.g., -I../h)
186: LSOCKET libraries to link in (e.g., -lcci)
187: BINDIR /usr/local/bin/ where to install user programs
188: SBINDIR /usr/etc/ where to install administrator
189: programs
190: ETCDIR /usr/etc/ where to install administrator files
191: LOGDIR /usr/tmp/ where to install log files
192: INCDIR /usr/include/isode/ where to install include files
193: LIBDIR /usr/lib/ where to install object libraries
194: LINTDIR /usr/lib/lint/ where to install lint libraries
195: SYSTEM directs how to create loader libraries
196: MANDIR /usr/man/ where to install man pages
197: MANOPTS see compat/inst-man.sh for details
198: .re
199: .fi
200: .in -.5i
201: .sp
202: \fBNOTE THAT ALL THESE DIRECTORIES MUST BE ABSOLUTE PATH NAMES
203: (i.e., start with a `/')\fR.
204: .PP
205: Finally,
206: .sp
207: .in +.5i
208: .nf
209: ln pickle.make CONFIG.make
210: .fi
211: .in -.5i
212: .sp
213: (yes, that's \*(lqCONFIG\*(rq in uppercase and \*(lqmake\*(rq in lowercase).
214: Both of these files are in the \fB\*(VDconfig/\fR directory.
215: This latter file is the one which the software uses to configure itself
216: during generation.
217: .SS INCLUDE\-FILE
218: Copy the include\-file skeleton of your choice to \fBpickle.h\fR,
219: where \*(lqpickle\*(rq is the name of your system.
220: Now add any additional definitions you like (usually none).
221: Consult the file \fBconfig/OPTIONS\fR for a list.
222: .PP
223: Now:
224: .sp
225: .in +.5i
226: .nf
227: ln pickle.h ../h/config.h
228: .fi
229: .in -.5i
230: .sp
231: This latter file is the one which the software uses to configure itself
232: during generation.
233: .SS "ALIASES DATABASE"
234: Typically, sites run with the default aliases database used
235: by the OSI directory.
236: In this case,
237: simply copy the default local configuration file to the \fBsupport/\fR
238: directory:
239: .sp
240: .in +.5i
241: .nf
242: % cp aliases.local ../support/
243: .fi
244: .in -.4i
245: .sp
246: If you have local modifications you wish to make,
247: either copy in your own file or edit the file
248: \fBsupport/aliases.local\fR as appropriate.
249: .SS "SERVICES DATABASE"
250: Typically, sites run with the default services database.
251: In this case,
252: simply copy the default local configuration file to the \fBsupport/\fR
253: directory:
254: .sp
255: .in +.5i
256: .nf
257: % cp services.local ../support/
258: .fi
259: .in -.4i
260: .sp
261: If you have local modifications you wish to make,
262: either copy in your own file or edit the file
263: \fBsupport/services.local\fR as appropriate.
264: .SS "ENTITIES DATABASE"
265: Typically, sites run with the default application entity database used
266: by the stub\-directory service.
267: In this case,
268: simply copy the default local configuration file to the \fBsupport/\fR
269: directory:
270: .sp
271: .in +.5i
272: .nf
273: % cp entities.local ../support/
274: .fi
275: .in -.5i
276: .sp
277: If you have local modifications you wish to make,
278: either copy in your own file or edit the file
279: \fBsupport/entities.local\fR as appropriate.
280: .PP
281: In particular,
282: if you are using SunLink OSI,
283: it will be necessary to put an entry in your
284: \fBsupport/entities.local\fR file of the form:
285: .sp
286: .in +.5i
287: myhost\0default\0\01.17.4.1.0\0\0#1/NS+mynsap
288: .in -.5i
289: .sp
290: where \*(lqmyhost\*(rq is the name of the local machine,
291: and \*(lqmynsap\*(rq is the NSAP of the local machine.
292: The NSAP is most easily determined by running
293: .sp
294: .in +.5i
295: .nf
296: % cd others/osilookup
297: % ./make
298: % xosilookup localhost CLIENT
299: .fi
300: .in -.5i
301: .sp
302: providing that the SunLink OSI file \fB/etc/sunlink/osi/hosts\fR
303: has an entry defining the service for \*(lqlocalhost\*(rq called
304: \*(lqCLIENT\*(rq.
305: (Note that in releases earlier than SunLink OSI 6.0,
306: the file is called \fB/usr/etc/osi.hosts\fR)
307: Note that this entry is mandatory if you are running SunLink OSI
308: release 5.2 or greater.
309: .PP
310: One further note for users of SunLink OSI:
311: if you intend to run the standard SunLink OSI listener,
312: then you must change the TSEL used by \fItsapd\fR when it listens.
313: This is done in two steps:
314: First,
315: in \fBsupport/entities.local\fR,
316: change your entry to read as:
317: .sp
318: .in +.5i
319: myhost\0default\0\01.17.4.1.0\0\0#2/NS+mynsap
320: .in -.5i
321: .sp
322: Second,
323: in \fBsupport/services.local\fR,
324: add a line that reads as:
325: .sp
326: .in +.5i
327: tsap/session\0\0#2\0\0tsapd-bootstrap
328: .in -.5i
329: .sp
330: which overrides the default TSEL in the \fBsupport/services.db\fR file.
331: .SS "MACROS DATABASE"
332: Typically, sites run with the default macros database.
333: In this case,
334: simply copy the default local configuration file to the \fBsupport/\fR
335: directory:
336: .sp
337: .in +.5i
338: .nf
339: % cp macros.local ../support/
340: .fi
341: .in -.5i
342: .sp
343: If you have local modifications you wish to make,
344: either copy in your own file or edit the file
345: \fBsupport/macros.local\fR as appropriate.
346: .SS "OBJECTS DATABASE"
347: Typically, sites run with the default objects database.
348: In this case,
349: simply copy the default local configuration file to the \fBsupport/\fR
350: directory:
351: .sp
352: .in +.5i
353: .nf
354: % cp objects.local ../support/
355: .fi
356: .in -.4i
357: .sp
358: If you have local modifications you wish to make,
359: either copy in your own file or edit the file
360: \fBsupport/objects.local\fR as appropriate.
361: .SH GENERATION
362: Go to the \fB\*(VD\fR directory
363: .sp
364: .in +.5i
365: .nf
366: % cd ..
367: .fi
368: .in -.5i
369: .sp
370: Now reset the dates of the
371: configuration files for the system.
372: This is done only once per source-tree:
373: .sp
374: .in +.5i
375: .nf
376: % ./make once-only
377: .fi
378: .in -.5i
379: .sp
380: then generate the basic system.
381: .sp
382: .in +.5i
383: .nf
384: % ./make
385: .fi
386: .in -.5i
387: .sp
388: If you are using SunOS,
389: do not use the \fImake\fR program supplied with the SunPro package.
390: It is not, contrary to any claims, compatible with the standard
391: \fImake\fR facility.
392: Further,
393: note that if you are running a version of SunOS 4.0 prior to release 4.0.3,
394: then you may need to use the \fImake\fR program found in \fB/usr/old/\fR,
395: if the standard \fImake\fR your are using is the SunPro \fImake\fR.
396: In this case,
397: you will need to put the old, standard \fImake\fR in \fB/usr/bin/\fR,
398: and you can keep the SunPro \fImake\fR in \fB/bin/\fR.
399: .PP
400: If you are using SVR3,
401: then you will probably have to type this command before starting the
402: compilation:
403: .sp
404: .in +.5i
405: .nf
406: % ulimit 32768
407: .fi
408: .in -.5i
409: .sp
410: Similarly,
411: you may need to increase the stacksize limitation on other systems.
412: For example,
413: some users of the RT, report needing to use
414: .sp
415: .in +.5i
416: .nf
417: % limit stacksize 16m
418: .fi
419: .in -.5i
420: .sp
421: in order to get FTAM to fully compile.
422: .PP
423: The \fImake\fR command from the top-level directory
424: will cause a complete generation of the system.
425: If all goes well, proceed with the installation.
426: If not, complain, as there \*(lqshould be no problems\*(rq at this step.
427: Some files while compiling may produce a
428: .sp
429: .in +.5i
430: .nf
431: warning: statement not reached
432: .fi
433: .in -.5i
434: .sp
435: or a
436: .sp
437: .in +.5i
438: .nf
439: type ObjectDescriptor: Warning: Can't find file DSE.ph failed
440: .fi
441: .in -.5i
442: .sp
443: message.
444: This is normal.
445: Sometimes when building a loader library, you might see several
446: .sp
447: .in +.5i
448: .nf
449: ranlib: warning: ../libisode.a(aetdbm.o): no symbol table
450: .fi
451: .in -.5i
452: .sp
453: messages.
454: This is also normal.
455: You might also see a few messages like:
456: .sp
457: .in +.5i
458: .nf
459: *** Error code 1 (ignored)
460: .fi
461: .in -.5i
462: .sp
463: This is also normal.
464: As a rule, unless \fImake\fR says something like
465: .sp
466: .in +.5i
467: .nf
468: *** Error code 1
469: .fi
470: .in -.5i
471: .sp
472: or perhaps
473: .sp
474: .in +.5i
475: .nf
476: Exit
477: .fi
478: .in -.5i
479: .sp
480: then everything is going just fine!
481: .SH TESTING
482: Some directories may have a resident test program,
483: e.g., in the \fBpsap/\fR directory, there is a program called \fIpsaptest\fR.
484: These programs are for internal testing only,
485: and are not for use by \*(lqmere mortals\*(rq.
486: If you want to test things,
487: after installation run \fIisode\-test\fR (see the \fBUSER PROGRAMS\fR section).
488: .SH INSTALLATION
489: You will need to be the super\-user to install the software.
490: Note that installing the software from an NFS-mounted partition
491: requires that you perform the installation as the super-user on the
492: \fItarget\fR system after changing to the source directory on the
493: \fIsource\fR system.
494: .PP
495: In the directions that follow,
496: reference is made to some of the directories defined in the
497: \fBCONFIG.make\fR file.
498: You should substitute in the correct value,
499: for example,
500: if the expression
501: .sp
502: .in +.5i
503: .nf
504: $(SBINDIR)tsapd
505: .fi
506: .in -.5i
507: .sp
508: and if SBINDIR is defined as \fB/usr/etc/\fR in the \fBCONFIG.make\fR
509: file,
510: then you should type
511: .sp
512: .in +.5i
513: .nf
514: /usr/etc/tsapd
515: .fi
516: .in -.5i
517: .sp
518: instead.
519: .PP
520: There are two kinds of activities:
521: once\-only activities that you perform the first time the software is
522: installed;
523: and each\-time activities that you perform every time the software is
524: installed.
525: .PP
526: The first once\-only activity is to verify that the \fItsapd\fR daemon will be
527: run when the machine goes multi\-user.
528: On Berkeley UNIX systems, add these lines to the \fB/etc/rc.local\fR file:
529: .sp
530: .in +.5i
531: .nf
532: if [ \-f $(SBINDIR)tsapd ]; then
533: $(SBINDIR)tsapd & (echo \-n ' tsap') > /dev/console
534: fi
535: .fi
536: .in -.5i
537: .sp
538: On other systems, a similar procedure is followed.
539: For example,
540: on systems derived from AT&T UNIX,
541: the file \fB/etc/rc2\fR script might be edited.
542: .PP
543: The next once\-only activity is to verify that systems with a native
544: \fB/etc/services\fR file contain an entry for the tsap service
545: (if you have configured the ISODE to run over TCP).
546: If not,
547: add the line:
548: .sp
549: .in +.5i
550: .nf
551: tsap 102/tcp
552: .fi
553: .in -.5i
554: .sp
555: to the \fB/etc/services\fR file.
556: If your system does not have such a file,
557: the software automatically compensates for this.
558: .PP
559: Next,
560: on Berkeley UNIX systems,
561: add a line to the \fB/usr/lib/crontab\fR file to invoke a
562: shell-script that will re-cycle the log files.
563: Usually, the line you add looks something like this:
564: .sp
565: .in +.5i
566: .nf
567: 0 4 * * * su daemon < $(SBINDIR)isologs
568: .fi
569: .in -.5i
570: .sp
571: which says that the shell-script $(SBINDIR)isologs should be invoked at 4am
572: each morning.
573: On other systems, a similar procedure is fllowed.
574: For example,
575: on systems derived from AT&T UNIX,
576: the file \fB/usr/spool/cron/crontabs/root\fR might be edited followed
577: by the command
578: .sp
579: .in +.5i
580: .nf
581: % crontab root
582: .fi
583: .in -.5i
584: .sp
585: .PP
586: Finally,
587: create the BINDIR, SBINDIR, ETCDIR, and LOGDIR directories as they
588: appear in your \fBCONFIG.make\fR file, if they do not already exist.
589: The mode of the LOGDIR directory should be 777,
590: the other directories should be mode 755.
591: .PP
592: There are two each\-time activities:
593: .sp
594: .in +.5i
595: .nf
596: # ./make inst\-all
597: .fi
598: .in -.5i
599: .sp
600: which does the installation.
601: .PP
602: The second each\-time activity,
603: is that if you are already running the ISODE,
604: then you will need to kill and restart the \fItsapd\fR\0(8c) daemon,
605: otherwise incoming connections will not be initialized correctly.
606: Otherwise, start the daemon now.
607: From the \fICShell\fR, the command might be:
608: .sp
609: .in +.5i
610: .nf
611: # $(SBINDIR)tsapd >& /dev/null
612: .fi
613: .in -.5i
614: .sp
615: The daemon will automatically detach.
616: If you do not redirect the daemon's standard\-error,
617: then it will not detach, instead printing messages as to what actions it
618: is taking.
619: .PP
620: That's about it. This will install everything.
621: To clean-up the source tree as well,
622: then use:
623: .sp
624: .in +.5i
625: .nf
626: % ./make clean
627: .fi
628: .in -.5i
629: .sp
630: at this point.
631: Note that if you are planning on generating or installing FTAM or VT
632: or QUIPU (described below),
633: then you should not clean-up the source tree until after you are
634: finished dealing with these.
635: .PP
636: If your system is configured for TCP/IP,
637: and you are not already running an SNMP agent,
638: then you are \fBURGED\fR to immediately install the SNMP agent
639: distributed with the ISODE.
640: Consult the \fBNETWORK MANAGEMENT\fR section below.
641: .PP
642: Finally,
643: if you are interested in discussing the ISODE with others running the software,
644: drop a note to the Internet mailbox
645: \*(lqISODE\[email protected]\*(rq,
646: and ask to be added to the \*([email protected]\*(rq list.
647: .SH TAILORING
648: If you create a file called \fB$(ETCDIR)isotailor\fR,
649: then you can customize the behavior of the programs which use the
650: ISODE when they start.
651: Consult the \fBsupport/isotailor.5\fR file for further information.
652: .SH "USER PROGRAMS"
653: By default,
654: two services are installed.
655: .PP
656: The first service,
657: having programs \fIisoc\fR and \fIisod\fR,
658: is used to test out the installation of the ISODE on your system:
659: .sp
660: .in +.5i
661: .nf
662: % ./make test
663: .fi
664: .in -.5i
665: which runs the \fIisode\-test\fR script.
666: .PP
667: The second service,
668: having programs \fIimisc\fR and \fIros.imisc\fR,
669: is a small demo service supporting things like \fIfinger\fR, \fIwho\fR and
670: so forth.
671: .PP
672: There are additional programs in the \fBothers/\fR directory.
673: These aren't integral parts of the system and assume that the ISODE is already
674: installed.
675: Use at your own discretion.
676: .SH "FILE TRANSER, ACCESS AND MANAGEMENT"
677: In addition,
678: if you are running the ISODE on a Berkeley or AT&T System V UNIX system,
679: then there is also an implementation of the ISO FTAM.
680: FTAM, which stands for File Transfer, Access and Management,
681: is the OSI file service.
682: The implementation provided is fairly complete in the context of
683: the particular file services it offers.
684: It is a minimal implementation in as much as it offers only four core
685: services: transfer of text files,
686: transfer of binary files,
687: directory listings,
688: and file management.
689: .PP
690: To generate FTAM, go to the \fB\*(VD\fR directory and type:
691: .sp
692: .in +.5i
693: .nf
694: % ./make all-ftam
695: .fi
696: .in -.5i
697: .sp
698: .PP
699: This will cause a complete generation of the FTAM libraries and programs.
700: If all goes well, proceed with the installation.
701: If not, complain as there \*(lqshould be no problems\*(rq at this step.
702: .PP
703: You will need to be the super-user to install FTAM:
704: .sp
705: .in +.5i
706: .nf
707: # ./make install\-ftam
708: .fi
709: .in -.5i
710: .sp
711: That's about it.
712: This will install everything and then clean\-up the source tree.
713: Note that if you are planning on generating or installing the FTAM/FTP
714: gateway (described below),
715: then you should not clean-up the source tree until after you are
716: finished dealing with the gateway.
717: In this case,
718: or if you just want an installation and no clean\-up, then use:
719: .sp
720: .in +.5i
721: .nf
722: # ./make inst\-ftam
723: .fi
724: .in -.5i
725: .sp
726: instead.
727: .SH "FTAM/FTP GATEWAY"
728: In addition,
729: if you are running the ISODE on a Berkeley UNIX system,
730: there is also an implementation of an FTAM/FTP application gateway.
731: The gateway is actually two programs:
732: one which acts as an ftam responder and an ftp client,
733: and the other which acts as an ftp server and an ftam initiator.
734: Note that the gateway currently resides on a different location
735: than the standard FTAM responder and FTP server.
736: (This may be corrected in a future release.)
737: Read the manual entries for \fIftamd-ftp\fR\0(8c) and
738: \fIftpd-ftam\fR\0(8c) for the details.
739: .PP
740: To generate the FTAM/FTAP gateway, go to the \fB\*(VD\fR directory and type:
741: .sp
742: .in +.5i
743: .nf
744: % ./make all-ftam-ftp
745: .fi
746: .in -.5i
747: .sp
748: .PP
749: This will cause a complete generation of the gateway.
750: If all goes well, proceed with the installation.
751: If not, complain as there \*(lqshould be no problems\*(rq at this step.
752: .PP
753: You will need to be the super-user to install the FTAM/FTP gateway:
754: .sp
755: .in +.5i
756: .nf
757: # ./make install\-ftam-ftp
758: .fi
759: .in -.5i
760: .sp
761: This will install everything and then clean\-up the source tree.
762: If you just want an installation and no clean\-up, then use:
763: .sp
764: .in +.5i
765: .nf
766: # ./make inst\-ftam-ftp
767: .fi
768: .in -.5i
769: .sp
770: instead.
771: .PP
772: Regardless of the command you use,
773: on 4.2BSD-derived systems, add this line to your \fB/etc/servers\fR file:
774: .sp
775: .in +.5i
776: .nf
777: ftp-ftam\0\0tcp\0\0$(SBINDIR)in.ftpd-ftam
778: .fi
779: .in -.5i
780: .sp
781: On 4.3BSD-derived systems, add this line to your \fB/etc/inetd.conf\fR file:
782: .sp
783: .in +.5i
784: .nf
785: ftp-ftam\0\0stream\0\0tcp\0\0nowait\0\0root\0\0$(SBINDIR)in.ftpd-ftam\0\0in.ftpd-ftam
786: .fi
787: .in -.5i
788: .sp
789: .PP
790: Finally,
791: add this line to your \fB/etc/services\fR file:
792: .sp
793: .in +.5i
794: .nf
795: ftp-ftam 531/tcp
796: .fi
797: .in -.5i
798: .SH "VIRTUAL TERMINAL"
799: In addition,
800: if you are running the ISODE on a Berkeley UNIX system,
801: there is also an implementation of the ISO VT.
802: VT is the OSI terminal service.
803: The implementation provided is roughly comparable to an average telnet
804: implementation.
805: .PP
806: To generate the VT system, go to the \fB\*(VD\fR directory and type:
807: .sp
808: .in +.5i
809: .nf
810: % ./make all-vt
811: .fi
812: .in -.5i
813: .sp
814: .PP
815: This will cause a complete generation of the VT initiator and
816: responder programs.
817: If all goes well, proceed with the installation.
818: If not, complain as there \*(lqshould be no problems\*(rq at this step.
819: .PP
820: You will need to be the super-user to install VT:
821: .sp
822: .in +.5i
823: .nf
824: # ./make install\-vt
825: .fi
826: .in -.5i
827: .sp
828: That's about it.
829: This will install everything and then clean\-up the source tree.
830: If you just want an installation and no clean\-up, then use:
831: .sp
832: .in +.5i
833: .nf
834: # ./make inst\-vt
835: .fi
836: .in -.5i
837: .sp
838: instead.
839: .SH "DIRECTORY SERVICES"
840: In addition,
841: if you are running the ISODE on a Berkeley UNIX system,
842: there is also an implementation of the OSI Directory, called QUIPU.
843: If you're not interested in running a Directory,
844: skip this text and go to the section entitled \fBGENERATING
845: DOCUMENTATION\fR.
846: .PP
847: Each host using the OSI directory implicitly runs a
848: Directory User Agent (DUA).
849: Additionally,
850: you may wish to run a Directory System Agent (DSA) on some hosts.
851: As such,
852: the instructions which follow indicate which activities are necessary
853: in both instances, as appropriate.
854: .SS "QUIPU GENERATION"
855: To generate QUIPU, go to the \fB\*(VD\fR directory and type:
856: .sp
857: .in +.5i
858: .nf
859: % ./make all-quipu
860: .fi
861: .in -.5i
862: .sp
863: .PP
864: This will cause a complete generation of the DSAP library and the DSA.
865: If all goes well, proceed with the installation.
866: If not, complain as there \*(lqshould be no problems\*(rq at this step.
867: .SS "QUIPU INSTALLATION"
868: You will need to be the super-user to install QUIPU:
869: .sp
870: .in +.5i
871: .nf
872: # ./make install\-quipu
873: .fi
874: .in -.5i
875: .sp
876: This will install everything and then clean\-up the source tree.
877: If you just want an installation and no clean\-up, then use:
878: .sp
879: .in +.5i
880: .nf
881: # ./make inst\-quipu
882: .fi
883: .in -.5i
884: .sp
885: instead.
886: After either command,
887: there is one once-only activity.
888: .PP
889: The QUIPU DSA is a \*(lqstatic responder\*(rq.
890: This means that it accepts new associations and managing old ones as necessary.
891: Hence,
892: if you intend to run a local DSA,
893: it is necessary to start the \fIros.quipu\fR daemon when the
894: machine goes multi-user.
895: On Berkeley UNIX systems, add these lines to the \fB/etc/rc.local\fR file:
896: .sp
897: .in +.5i
898: .nf
899: if [ \-f $(SBINDIR)ros.quipu ]; then
900: (cd /usr/etc/quipu-db; $(SBINDIR)ros.quipu) & (echo \-n ' quipu') > /dev/console
901: fi
902: .fi
903: .in -.5i
904: .sp
905: (This assumes your database is in the directory \fB/usr/etc/quipu-db\fR -
906: it need not be)
907: On other systems, a similar procedure is followed.
908: .SS "QUIPU DATABASE"
909: If you intend to run a local DSA,
910: then you will need to build a Directory database.
911: (If you are already running QUIPU 5.0 or later,
912: then you've done this before and so you can skip to the next section
913: on \fBQUIPU TAILORING\fR.)
914: The database directory, by default, lives in the ETCDIR area
915: (usually \fB/usr/etc/\fR) under the name of \fBquipu-db/\fR.
916: Three prototype databases can be found in the directory
917: \fBothers/quipu/quipu-db/\fR.
918: These database files should be protected as they contain Directory passwords and
919: other sensitive information. The DSA needs to be able to read this
920: information, and so performs a setuid on execution to the UID of the owner
921: of the database directory.
922: .PP
923: Now customize the chosen prototype database under \fB/usr/etc/quipu-db/\fR. The
924: details of this database are explained in Volume 5 of the users manual.
925: However you should be able to derive a minimal database by following
926: the example structure defined for University College London in
927: the GB branch of the Directory tree.
928: Then delete the example structure for O=University College London.
929: .SS "QUIPU TAILORING"
930: Before starting the DSA and the applications using the Directory Service
931: Element (DSE),
932: they (along with the ISODE) should be tailored.
933: .PP
934: Currently,
935: the interaction between the DSE loaded by programs using the ISODE and
936: the DSA is available over a \*(lquser-friendly nameservice\*(rq
937: protocol which uses the OSI CO-mode transport service as backing.
938: Programs using the ISODE determine the address of the nameservice by looking
939: at the \fB$(ETCDIR)isotailor\fR file.
940: This file is not normally installed during the installation.
941: Check to see if such a file exists on your system.
942: If not, create it as the super-user.
943: Regardless, verify that the file contains a line like this:
944: .sp
945: .in +.5i
946: .nf
947: ns_address: Internet=localhost+17006
948: .fi
949: .in -.5i
950: .sp
951: Substitute the name of the system running a DSA for \*(lqlocalhost\*(rq
952: (or leave it be, if you wish),
953: and substitute any unused TCPport on this host for \*(lq17006\*(rq.
954: Next, you must enable the use of the nameservice by the DSE.
955: This is done by setting another runtime configuration variable in the
956: \fB$(ETCDIR)isotailor\fR file:
957: .sp
958: .in +.5i
959: .nf
960: ns_enable: on
961: .fi
962: .in -.5i
963: .sp
964: Programs using the ISODE will automatically check this variable.
965: If \*(lqon\*(rq, they will first try the nameservice to resolve the
966: service address.
967: If this fails, they will use the stub-directory service as a fallback.
968: .PP
969: So, you should arrange for the nameservice to be started with the
970: machine goes multi\-user.
971: On Berkeley UNIX systems, add these lines to the \fB/etc/rc.local\fR file:
972: .sp
973: .in +.5i
974: .nf
975: if [ \-f $(SBINDIR)dased ]; then
976: $(SBINDIR)dased & (echo \-n ' dase') > /dev/console
977: fi
978: .fi
979: .in -.5i
980: .sp
981: On other systems,
982: a similar procedure is followed.
983: .PP
984: If you choose to run a local DSA, now configure it.
985: The DSA tailors itself at runtime by reading the file \fB$(ETCDIR)quiputailor\fR.
986: A prototype of this file will be installed during the normal ISODE
987: installation process.
988: Only one entry in the file usually needs to be changed:
989: .sp
990: .in +.5i
991: .nf
992: mydsaname CN=toucan
993: .fi
994: .in -.5i
995: .sp
996: Substitute the name of the DSA as it occurs in the Directory for
997: \*(lqCN=toucan\*(rq.
998: See \fIquiputailor\fR\0(5) for a description of the full range of
999: tailoring options in the \fB$(ETCDIR)quiputailor\fR file.
1000: .PP
1001: Now configure the various DUA programs.
1002: These tailor themselves at runtime by reading the file
1003: \fB$(ETCDIR)dsaptailor\fR.
1004: A prototype of this file will be installed during the normal ISODE
1005: installation process.
1006: Only one entry in the file usually needs to be changed:
1007: .sp
1008: .in +.5i
1009: .nf
1010: dsa_address toucan Internet=localhost+17003
1011: .fi
1012: .in -.5i
1013: .sp
1014: Substitute the name of your \*(lqprimary\*(rq DSA for \*(lqtoucan\*(rq
1015: and its corresponding presentation address for the
1016: \*(lq'0101'H/Internet+...\*(rq string.
1017: This information can be found in the Directory on the host which is
1018: running the DSA.
1019: .PP
1020: Do not confuse the \fIdsa_address\fR used in this file with the
1021: \fIns_address\fR used in the \fB$(ETCDIR)isotailor\fR file.
1022: These are separate services and must live at different addresses.
1023: See \fIquiputailor\fR\0(5) for a description of the full range of
1024: tailoring options in the \fB$(ETCDIR)dsaptailor\fR file.
1025: .SS "QUIPU ONCE-ONLY"
1026: Having tailored QUIPU,
1027: you can now start the DSA.
1028: However, if you are already running QUIPU,
1029: then you will need to kill and restart the QUIPU DSA.
1030: .PP
1031: Start the DSA now.
1032: From the \fICShell\fR, the command might be:
1033: .sp
1034: .in +.5i
1035: .nf
1036: # $(SBINDIR)ros.quipu >& /dev/null
1037: .fi
1038: .in -.5i
1039: .sp
1040: The daemon will automatically detach.
1041: If you do not redirect the daemon's standard\-error,
1042: then it will not detach, instead printing messages as to what actions it
1043: is taking.
1044: .SS "ISOENTITIES REPLACEMENT"
1045: The last step
1046: which you MAY want to perform (only if you choose to run a local DSA
1047: and only the first time you install QUIPU)
1048: is to load the Directory from your \fB$(ETCDIR)isoentities\fR file.
1049: This step is not critical, missing this step will not effect the use of the
1050: Directory as a White Pages Service.
1051:
1052: WARNING, this does not provide for replication of such data, or non local
1053: interaction.
1054:
1055: To load the data from isoentities into the Directory use the \fIdsabuild\fR program:
1056: .sp
1057: .in +.5i
1058: .nf
1059: % dsabuild
1060: manager: c=US@o=The Wollongong Group@cn=Chris Moore
1061: password:
1062: .fi
1063: .in -.5i
1064: .sp
1065: By default, this will create only entries for the current host.
1066: You can use the `\-p\0designator' switch to load information on
1067: services available on other hosts.
1068: Typically,
1069: you will run \fIdsabuild\fR with the `\-p' option once for each host
1070: at your site.
1071: .PP
1072: As shown above,
1073: the \fIdsabuild\fR program will prompt for the DSA manager name and
1074: password. To determine this you will need to consult your database as
1075: configured above and get the \fImanager\fR attribute for the DSA which
1076: is responsible for the portion of the Directory tree you will be adding
1077: to. Substitute this value for \*(lqc=US@o=The Wollongong Group@cn=Chris\0Moore\*(rq.
1078: You will then need to find the password attribute for the manager
1079: object in the database as well.
1080: While running, \fIdsabuild\fR may print out messages for the form:
1081: .sp
1082: .in +.5i
1083: .nf
1084: *** Update error - Already exists ***
1085: .fi
1086: .in -.5i
1087: .sp
1088: This is normal.
1089: .PP
1090: That's about it.
1091: You can now use one of the user interfaces to look around in the Directory.
1092: .SS "DIRECTORY USER INTERFACE PROGRAMS"
1093: You may, optionally, want to build one or more of the user interface
1094: programs for interacing with the Directory.
1095: The default DUA is DISH which is located in the \fBquipu/dish\fR directory.
1096: Consult the \fBREAD-ME\fR file in this directory for a instructions on
1097: building it.
1098: .PP
1099: Two other interfaces - WIDGET and SUNINT are provided as example DUAs.
1100: These programs are located in the \fBothers/quipu/uips\fR directory.
1101: Consult the \fBREAD-ME\fR files in these directories for descriptions
1102: of these interfaces and instructions on building them.
1103: .PP
1104: When building the user interfaces,
1105: it is expected that you have NOT cleaned the basic ISODE build tree or
1106: the QUIPU tree.
1107: .SH "NETWORK MANAGEMENT"
1108: In addition,
1109: if you are running the ISODE on a Berkeley UNIX system,
1110: there is also an implementation of the SNMP.
1111: Although this is not the OSI network management service,
1112: Inasmuch as the continued survival of the Internet hinges on all nodes
1113: becoming network manageable,
1114: this package was developed using the ISODE and is being freely
1115: distributed with releases of Berkeley UNIX.
1116: .PP
1117: It must be stressed that this package is not a complete network management
1118: system.
1119: In particular,
1120: whilst \fIsnmpd\fR provides a minimal agent functionality,
1121: there are no Network Operation Center (NOC) tools--\fIsnmpi\fR is a
1122: debugging aid only.
1123: .PP
1124: To generate the SNMP system, go to the \fB\*(VD\fR directory and type:
1125: .sp
1126: .in +.5i
1127: .nf
1128: % ./make all-snmp
1129: .fi
1130: .in -.5i
1131: .sp
1132: .PP
1133: This will cause a complete generation of the SNMP agent and the
1134: minimal SNMP initiator program.
1135: If all goes well, proceed with the installation.
1136: If not, complain as there \*(lqshould be no problems\*(rq at this step.
1137: .PP
1138: There are two once\-only activities which must be performed prior to installation.
1139: First,
1140: check your \fB/etc/services\fR file,
1141: and verify that these three lines are present:
1142: .sp
1143: .in +.5i
1144: .nf
1145: snmp 161/udp
1146: snmp-trap 162/udp
1147: smux 199/tcp
1148: .fi
1149: .in -.5i
1150: .sp
1151: If not, add them.
1152: .PP
1153: Second,
1154: add these lines to the \fB/etc/rc.local\fR file:
1155: .sp
1156: .in +.5i
1157: .nf
1158: if [ \-f $(SBINDIR)snmpd ]; then
1159: $(SBINDIR)snmpd & (echo \-n ' snmp') > /dev/console
1160: fi
1161: if [ \-f $(SBINDIR)smux.unixd \-a \-f $(SBINDIR)snmpd ]; then
1162: $(SBINDIR)smux.unixd & (echo \-n ' smux-unix') > /dev/console
1163: fi
1164: .fi
1165: .in -.5i
1166: .sp
1167: .PP
1168: You will need to be the super-user to install SNMP:
1169: .sp
1170: .in +.5i
1171: .nf
1172: # ./make install\-snmp
1173: .fi
1174: .in -.5i
1175: .sp
1176: This will install everything and then clean\-up the source tree.
1177: If you just want an installation and no clean\-up, then use:
1178: .sp
1179: .in +.5i
1180: .nf
1181: # ./make inst\-snmp
1182: .fi
1183: .in -.5i
1184: .sp
1185: instead.
1186: .PP
1187: Regardless of the command you use,
1188: read the comments in the \fB$(ETCDIR)snmpd.rc\fR file which will tell
1189: you how to tailor the agent for your installation.
1190: .PP
1191: Finally,
1192: if you are already running the SNMP,
1193: then you will need to kill and restart the \fIsnmpd\fR\0(8c) and SMUX
1194: UNIX daemons.
1195: (It is best to kill \fIsmux.unixd\fR first, and then \fIsnmpd\fR.)
1196: Otherwise, start the daemons now.
1197: From the \fICShell\fR, the command might be:
1198: .sp
1199: .in +.5i
1200: .nf
1201: # $(SBINDIR)snmpd >& /dev/null
1202: # $(SBINDIR)smux.unixd >& /dev/null
1203: .fi
1204: .in -.5i
1205: .sp
1206: The daemon will automatically detach.
1207: If you do not redirect the daemon's standard\-error,
1208: then it will not detach, instead printing messages as to what actions it
1209: is taking.
1210: .SH "LIGHTWEIGHT PRESENTATION PROTOCOL"
1211: In addition,
1212: if you are running the ISODE on a Berkeley UNIX system,
1213: there is also an implementation of RFC1085,
1214: the lightweight presentation protocol for TCP/IP-based internets.
1215: .PP
1216: To generate the LPP system, go to the \fB\*(VD\fR directory and type:
1217: .sp
1218: .in +.5i
1219: .nf
1220: % ./make all\-lpp
1221: .fi
1222: .in -.5i
1223: .sp
1224: .PP
1225: This will cause a complete generation of the LPP library and support programs.
1226: If all goes well, proceed with the installation.
1227: If not, complain as there \*(lqshould be no problems\*(rq at this step.
1228: .PP
1229: You will need to be the super-user to install the LPP system.
1230: There are two kinds of activities:
1231: once\-only activities that you perform the first time the software is
1232: installed;
1233: and each\-time activities that you perform every time the software is
1234: installed.
1235: .PP
1236: The first once\-only activity is to verify that the \fIlppd\fR daemon will be
1237: run when the machine goes multi\-user.
1238: On Berkeley UNIX systems, add these lines to the \fB/etc/rc.local\fR file:
1239: .sp
1240: .in +.5i
1241: .nf
1242: if [ \-f $(SBINDIR)lppd ]; then
1243: $(SBINDIR)lppd & (echo \-n ' lpp') > /dev/console
1244: fi
1245: .fi
1246: .in -.5i
1247: .sp
1248: On other systems, a similar procedure is followed.
1249: .PP
1250: The next once\-only activity is to verify that systems with a native
1251: \fB/etc/services\fR file contain an entry for the miscellany service.
1252: This is used when the ISODE miscellaneous services is run using the LPP.
1253: If not,
1254: add the line:
1255: .sp
1256: .in +.5i
1257: .nf
1258: miscellany 17002/lpp
1259: .fi
1260: .in -.5i
1261: .sp
1262: to the \fB/etc/services\fR file.
1263: If your system does not have such a file,
1264: the software automatically compensates for this.
1265: .PP
1266: There are two each\-time activities:
1267: .sp
1268: .in +.5i
1269: .nf
1270: # ./make install\-lpp
1271: .fi
1272: .in -.5i
1273: .sp
1274: This will install everything and then clean\-up the source tree.
1275: If you just want an installation and no clean\-up, then use:
1276: .sp
1277: .in +.5i
1278: .nf
1279: # ./make inst\-lpp
1280: .fi
1281: .in -.5i
1282: .sp
1283: instead.
1284: .PP
1285: Regardless of the command you use,
1286: the second each\-time activity,
1287: is that if you are already running the LPP system,
1288: then you will need to kill and restart the \fIlppd\fR\0(8c) daemon,
1289: otherwise incoming connections will not be initialized correctly.
1290: Otherwise, start the daemon now.
1291: From the \fICShell\fR, the command might be:
1292: .sp
1293: .in +.5i
1294: .nf
1295: # $(SBINDIR)lppd >& /dev/null
1296: .fi
1297: .in -.5i
1298: .sp
1299: The daemon will automatically detach.
1300: If you do not redirect the daemon's standard\-error,
1301: then it will not detach, instead printing messages as to what actions it
1302: is taking.
1303: .PP
1304: That's about it.
1305: .SH "GENERATING DOCUMENTATION"
1306: The directory \fBdoc/\fR contains the documentation set for this release.
1307: Consult the file \fBdoc/READ\-ME\fR for a description of each document.
1308: The directory \fBdoc/ps/\fR contains PostScript versions of each document.
1309: Usually it is easier to print the files in this directory than
1310: generate the documentation from scratch as
1311: the sources to these documents are in either LaTeX (for papers)
1312: or SLiTeX (for presentations).
1313: .PP
1314: If you received this distribution from the network,
1315: then the directory \fBdoc/ps/\fR does not contain any PostScript files.
1316: There should be a separate compressed \fItar\fR file,
1317: containing only PostScript files,
1318: available on the machine where you retrieved this distribution.
1319: .SH FILES
1320: Too numerous to mention.
1321: Honest.
1322: .SH "SEE ALSO"
1323: \fIThe ISO Development Environment: User's Manual\fR
1324: .SH AUTHOR
1325: Marshall T. Rose
1326: .br
1327: with assistance from a cast of thousands
1328: (read the \fBPreface\fR in the \fIUser's Manual\fR)
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.