/
READ-ME
1386 lines (823 loc) · 43 KB
/
READ-ME
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
ISODE-GEN(8) MAINTENANCE COMMANDS ISODE-GEN(8)
NAME
isode-gen - generating the ISO Development Environment
READ THIS
This documentation describes how to configure, generate, and
install the ISO Development Environment.
Acquisition, use, and distribution of this module and
related materials are subject to the restrictions of a
license agreement. Consult the Preface in the _U_s_e_r'_s _M_a_n_u_a_l
for the full terms of this agreement.
You will probably want to read over this entire document
first, before typing any commands; e.g., there are optional
components described later on that require additional set-
tings in the configuration file.
There is an ISODE discussion group "ISODE@NIC.SRI.COM". If
you want to subscribe to the ISODE discussion group, drop a
note to "ISODE-Request@NIC.SRI.COM".
SYNOPSIS
% cd isode-8.0
% cp config/_s_y_s_t_e_m.h h/config.h
% cp config/_s_y_s_t_e_m.make config/CONFIG.make
% cp config/*.local support/
% ./make everything
# ./make inst-everything
DESCRIPTION
This is a description of how one can bring up the ISODE. It
is assumed that you have super-user privileges in order to
(re-)install the software. Super-user privileges are not
required to configure or generate this software.
The distribution tape contains the hierarchy for the
isode-8.0 directory. Bring the sources on-line by changing
to a directory for local sources and running tar, e.g.,
% cd /usr/src/local/
% tar x
% cd isode-8.0
CONFIGURATION
First, go to the config/ directory.
% cd config
Sun Release 4.1 Last change: 19th June 1992 1
ISODE-GEN(8) MAINTENANCE COMMANDS ISODE-GEN(8)
Select the Makefile and include-file skeletons which most
closely match your system. The current choices are:
_f_i_l_e _c_o_n_f_i_g_u_r_a_t_i_o_n
aix AIX 3.2
apollo Apollo
aux A/UX release 2.0.1
bsd42 generic 4.2BSD UNIX
bsd43 generic 4.3BSD UNIX
bsd43-rt RT/PC with 4.3BSD
bsd44 4.4BSD UNIX with OSI
ccur Concurrent RTU 6.0
hpux HP-UX
mips MIPS RISC/OS
osx Olivetti LSX 30xx
ros Ridge Operating System
solbourne Solbourne
sunlink3 SunOS release 3 with SunLink OSI/X.25 release 5.2
sunlink4 SunOS release 4 with SunLink OSI/X.25 release 6.0
sunnet7 SunOS release 4 with SunNet OSI release 7.0
sunnet7x SunOS release 4 with SunNet X.25 release 7.0
sunos3 SunOS release 3
sunos4 SunOS release 4
sunos4-1 SunOS release 4.1
sys52-exos SVR2 UNIX with EXOS
sys52-rt RT/PC with AIX
sys52-sun SVR2 UNIX emulation on SunOS release 3
sys52-win SVR2 UNIX with WIN/TCP
sys53 generic SVR3
sys54 generic SVR4
ultrix Ultrix 3.1
The makefile skeleton has the extension .make, whereas the
include-file skeleton has the extension .h.
MAKEFILE
Copy the makefile skeleton of your choice to pickle.make,
where "pickle" is the name of your system. Now edit this
file to set the following _m_a_k_e variables:
_v_a_r_i_a_b_l_e _d_e_f_a_u_l_t _s_p_e_c_i_f_i_e_s
OPTIONS options to _c_c and _l_i_n_t (e.g., -I../h)
LSOCKET libraries to link in (e.g., -lcci)
BINDIR /usr/local/bin/ where to install user programs
SBINDIR /usr/etc/ where to install administrator
programs
ETCDIR /usr/etc/ where to install administrator files
LOGDIR /usr/tmp/ where to install log files
INCDIR /usr/include/isode/ where to install include files
LIBDIR /usr/lib/ where to install object libraries
LINTDIR /usr/lib/lint/ where to install lint libraries
SYSTEM directs how to create loader libraries
Sun Release 4.1 Last change: 19th June 1992 2
ISODE-GEN(8) MAINTENANCE COMMANDS ISODE-GEN(8)
MANDIR /usr/man/ where to install man pages
MANOPTS see compat/inst-man.sh for details
NOTE THAT ALL THESE DIRECTORIES MUST BE ABSOLUTE PATH NAMES
(i.e., start and end with a `/').
Finally,
ln pickle.make CONFIG.make
(yes, that's "CONFIG" in uppercase and "make" in lowercase).
Both of these files are in the isode-8.0/config/ directory.
This latter file is the one which the software uses to con-
figure itself during generation.
INCLUDE-FILE
Copy the include-file skeleton of your choice to pickle.h,
where "pickle" is the name of your system. Now add any
additional definitions you like (usually none). Consult the
file config/OPTIONS for a list.
Now:
ln pickle.h ../h/config.h
This latter file is the one which the software uses to con-
figure itself during generation.
ALIASES DATABASE
Typically, sites run with the default aliases database used
by the OSI directory. In this case, simply copy the default
local configuration file to the support/ directory:
% cp aliases.local ../support/
If you have local modifications you wish to make, either
copy in your own file or edit the file
support/aliases.local as appropriate.
SERVICES DATABASE
Typically, sites run with the default services database. In
this case, simply copy the default local configuration file
to the support/ directory:
% cp services.local ../support/
If you have local modifications you wish to make, either
copy in your own file or edit the file
support/services.local as appropriate.
ENTITIES DATABASE
Typically, sites run with the default application entity
Sun Release 4.1 Last change: 19th June 1992 3
ISODE-GEN(8) MAINTENANCE COMMANDS ISODE-GEN(8)
database used by the stub-directory service. However, once
things are running, sites should use the OSI Directory to
keep track of application entities. So, to begin, simply
copy the default local configuration file to the support/
directory:
% cp entities.local ../support/
If you have local modifications you wish to make, either
copy in your own file or edit the file
support/entities.local as appropriate.
In particular, if you are using SunNet OSI, it will be
necessary to put an entry in your support/entities.local
file of the form:
myhost default 1.17.4.1.0 #1/NS+mynsap
where "myhost" is the name of the local machine, and "myn-
sap" is the NSAP of the local machine. For SunNet OSI 7.0
the NSAP is most easily determined by running
% /usr/sunlink/osi/etc/osirstat -n | grep ^DA
provided that the SunNet OSI osi.routed program is running.
For earlier SunLink OSI releases you can run
% cd others/osilookup
% ./make
% xosilookup localhost CLIENT
providing that the SunLink OSI file /etc/sunlink/osi/hosts
has an entry defining the service for "localhost" called
"CLIENT". (Note that in releases earlier than SunLink OSI
6.0, the file is called /usr/etc/osi.hosts) Note that this
entry is mandatory if you are running SunLink OSI release
5.2 or greater.
One further note for users of a release earlier then 7.0 of
SunLink OSI: if you intend to run the standard SunLink OSI
listener (osi.netd), then you must change the TSEL used by
_t_s_a_p_d when it listens. This is done in two steps: First, in
support/entities.local, change your entry to read as:
myhost default 1.17.4.1.0 #2/NS+mynsap
Second, in support/services.local, add a line that reads as:
tsap/session #2 tsapd-bootstrap
which overrides the default TSEL in the support/services.db
file.
Sun Release 4.1 Last change: 19th June 1992 4
ISODE-GEN(8) MAINTENANCE COMMANDS ISODE-GEN(8)
MACROS DATABASE
Typically, sites run with the default macros database. In
this case, simply copy the default local configuration file
to the support/ directory:
% cp macros.local ../support/
If you have local modifications you wish to make, either
copy in your own file or edit the file support/macros.local
as appropriate.
OBJECTS DATABASE
Typically, sites run with the default objects database. In
this case, simply copy the default local configuration file
to the support/ directory:
% cp objects.local ../support/
If you have local modifications you wish to make, either
copy in your own file or edit the file
support/objects.local as appropriate.
GENERATION
Go to the isode-8.0 directory
% cd ..
Now reset the dates of the configuration files for the sys-
tem. This is done only once per source-tree:
% ./make once-only
then generate the basic system.
% ./make
If you are using SunOS, do not use the _m_a_k_e program supplied
with the SunPro package. It is not, contrary to any claims,
compatible with the standard _m_a_k_e facility. Further, note
that if you are running a version of SunOS 4.0 prior to
release 4.0.3, then you may need to use the _m_a_k_e program
found in /usr/old/, if the standard _m_a_k_e your are using is
the SunPro _m_a_k_e. In this case, you will need to put the
old, standard _m_a_k_e in /usr/bin/, and you can keep the SunPro
_m_a_k_e in /bin/.
If you are using SVR3, then you will probably have to type
this command before starting the compilation:
% ulimit 32768
Similarly, you may need to increase the stacksize limitation
Sun Release 4.1 Last change: 19th June 1992 5
ISODE-GEN(8) MAINTENANCE COMMANDS ISODE-GEN(8)
on other systems. For example, some users of the RT, report
needing to use
% limit stacksize 16m
in order to get FTAM to fully compile.
The _m_a_k_e command from the top-level directory will cause a
complete generation of the system. If all goes well,
proceed with the installation. If not, complain, as there
"should be no problems" at this step. Some files while com-
piling may produce a
warning: statement not reached
or a
type ObjectDescriptor: Warning: Can't find file DSE.ph failed
message. This is normal. Sometimes when building a loader
library, you might see several
ranlib: warning: ../libisode.a(aetdbm.o): no symbol table
messages. This is also normal. You might also see a few
messages like:
*** Error code 1 (ignored)
This is also normal. As a rule, unless _m_a_k_e says something
like
*** Error code 1
or perhaps
Exit
then everything is going just fine!
TESTING
Some directories may have a resident test program, e.g., in
the psap/ directory, there is a program called _p_s_a_p_t_e_s_t.
These programs are for internal testing only, and are not
for use by "mere mortals". If you want to test things,
after installation run _i_s_o_d_e-_t_e_s_t (see the USER PROGRAMS
section).
INSTALLATION
You will need to be the super-user to install the software.
Note that installing the software from an NFS-mounted parti-
tion requires that you perform the installation as the
Sun Release 4.1 Last change: 19th June 1992 6
ISODE-GEN(8) MAINTENANCE COMMANDS ISODE-GEN(8)
super-user on the _t_a_r_g_e_t system after changing to the source
directory on the _s_o_u_r_c_e system.
In the directions that follow, reference is made to some of
the directories defined in the CONFIG.make file. You should
substitute in the correct value, for example, if the expres-
sion
$(SBINDIR)tsapd
and if SBINDIR is defined as /usr/etc/ in the CONFIG.make
file, then you should type
/usr/etc/tsapd
instead.
There are two kinds of activities: once-only activities that
you perform the first time the software is installed; and
each-time activities that you perform every time the
software is installed.
The first once-only activity is to verify that the _t_s_a_p_d
daemon will be run when the machine goes multi-user. On
Berkeley UNIX systems, add these lines to the /etc/rc.local
file:
if [ -f $(SBINDIR)tsapd ]; then
$(SBINDIR)tsapd >/dev/null 2>&1 &
(echo -n ' tsap') > /dev/console
fi
On other systems, a similar procedure is followed. For
example, on systems derived from AT&T UNIX, the file
/etc/rc2 script might be edited.
Once you are familiar with the system, you will likely want
to run the OSI Directory and use another program, _i_a_e_d to
invoke local services. The section DIRECTORY SERVICES
discusses this in greater detail. (However, if this is your
first time, don't skip ahead.)
The next once-only activity is to verify that systems with a
native /etc/services file contain an entry for the tsap ser-
vice (if you have configured the ISODE to run over TCP). If
not, add the line:
tsap 102/tcp
to the /etc/services file. Alternatively, some systems may
have a definition of the form
Sun Release 4.1 Last change: 19th June 1992 7
ISODE-GEN(8) MAINTENANCE COMMANDS ISODE-GEN(8)
iso-tsap 102/tcp
which is also acceptable. If your system does not have such
a file, the software automatically compensates for this.
Next, on Berkeley UNIX systems, add a line to the
/usr/lib/crontab file to invoke a shell-script that will
re-cycle the log files. Usually, the line you add looks
something like this:
0 4 * * * su daemon < $(SBINDIR)isologs
which says that the shell-script $(SBINDIR)isologs should be
invoked at 4am each morning. On other systems, a similar
procedure is followed. For example, on systems derived from
AT&T UNIX, the file /usr/spool/cron/crontabs/root might be
edited followed by the command
% crontab root
There are two each-time activities:
# ./make inst-all
which does the installation. This command will try to build
all the directories you have specified, using _m_k_d_i_r. This
means that the parent of each of these directories must
exist for the the _m_k_d_i_r to succeed.
The second each-time activity, is that if you are already
running the ISODE, then you will need to kill and restart
the _t_s_a_p_d (8c) daemon, otherwise incoming connections will
not be initialized correctly. Otherwise, start the daemon
now. From the _C_S_h_e_l_l, the command might be:
# $(SBINDIR)tsapd >& /dev/null
The daemon will automatically detach. If you do not
redirect the daemon's standard-error, then it will not
detach, instead printing messages as to what actions it is
taking.
That's about it. This will install everything. To clean-up
the source tree as well, then use:
% ./make clean
at this point. Note that if you are planning on generating
or installing FTAM or VT or QUIPU (described below), then
you should not clean-up the source tree until after you are
finished dealing with these.
Sun Release 4.1 Last change: 19th June 1992 8
ISODE-GEN(8) MAINTENANCE COMMANDS ISODE-GEN(8)
If your system is configured for TCP/IP, and you are not
already running an SNMP agent, then you are URGED to immedi-
ately install the SNMP agent distributed with the ISODE.
Consult the NETWORK MANAGEMENT section below.
Finally, if you are interested in discussing the ISODE with
others running the software, drop a note to the Internet
mailbox "ISODE-Request@NIC.DDN.MIL", and ask to be added to
the "ISODE@NIC.DDN.MIL" list.
TAILORING
If you create a file called $(ETCDIR)isotailor, then you can
customize the behavior of the programs which use the ISODE
when they start. Consult the support/isotailor.5 file for
further information.
USER PROGRAMS
By default, two services are installed.
The first service, having programs _i_s_o_c and _i_s_o_d, is used to
test out the installation of the ISODE on your system:
% ./make test
which runs the _i_s_o_d_e-_t_e_s_t script.
The second service, having programs _i_m_i_s_c and _r_o_s._i_m_i_s_c, is
a small demo service supporting things like _f_i_n_g_e_r, _w_h_o and
so forth.
There are additional programs in the others/ directory.
These aren't integral parts of the system and assume that
the ISODE is already installed. Use at your own discretion.
REGISTERING OSI APPLICATION SERVICES
Earlier releases of the ISODE relied on static tables to
keep track of the OSI application services offered on an
end-system. This is a problematic exercise in keeping local
and remote tables synchronized. In this release of the
ISODE, the OSI Directory can be used to manage this informa-
tion, thereby automating the synchronization process.
Preparation
Once you have installed the ISODE, you must bring up a DSA.
The procedures for doing this varies, depending on your
location; consult the section "Setting up an Initial DSA" in
Volume 5 of the _U_s_e_r'_s _M_a_n_u_a_l.
You should also configure the $(ETCDIR)ufnrc file to reflect
your local Directory Tree. Details are given at the head of
the stub ufnrc file installed during the ISODE installation
phase.
Sun Release 4.1 Last change: 19th June 1992 9
ISODE-GEN(8) MAINTENANCE COMMANDS ISODE-GEN(8)
Once your DSA is running, you should build the DMD for your
organization. Underneath the entry for your organization,
you should select an area where your end-system's applica-
tion entities will reside in the DIT. For example, the OSI
application services available in PSI's Santa Clara office
reside somewhere under:
c=US
@o=Performance Systems International
@ou=Research and Development
@ou=Santa Clara
Note that this area may very well be different than the
value of the "local_DIT" in your dsaptailor file. In gen-
eral, all the end-systems at a site will have the same
"local_DIT" value, but each of those end-systems offering
OSI application services will place those services at a dif-
ferent portion in the DIT (usually somewhere underneath the
"local_DIT" value).
By convention, all the OSI application services offered by a
given end-system are placed in the same location in the DIT,
under an applicationProcess entry with the short name of the
end-system, e.g., "cn=cheetah". So, using the example
above, the entry
c=US
@o=Performance Systems International
@ou=Research and Development
@ou=Santa Clara
@cn=cheetah
would contain all the entries of interest.
Once-only Installation
The _b_o_o_t_s_v_c script will generate a shell script that will
create an applicationProcess entry and then an entry for
each of the OSI services provided by the ISODE. So, you
must first select the RDN for the applicationProcess entry.
Run _b_o_o_t_s_v_c to create a script:
% support/bootsvc <<aP-name>> > run.sh
e.g.,
% support/bootsvc cheetah > run.sh
Note that the first line of this script is used to define
the network address where _i_a_e_d listens for incoming connec-
tions. By default, only the address for the Internet com-
munity (RFC1006) is set. If the end-system is configured
Sun Release 4.1 Last change: 19th June 1992 10
ISODE-GEN(8) MAINTENANCE COMMANDS ISODE-GEN(8)
for other OSI communities, then this line should be changed
accordingly, e.g.,
A="Internet=`hostname`|NS+aabbcc"
Next, start _d_i_s_h in the background, bind as the manager,
move to the location in the DIT where the services are to be
registered and run the script, e.g.,
% setenv DISHPROC "127.0.0.1 `expr $$ + 32768`"
% bind -u <<DN of DSA Manager>>
% moveto "ou=Research and Development@ou=Santa Clara"
% sh run.sh
Following this, you need to arrange for _i_a_e_d rather than
_t_s_a_p_d to run when the machine goes multi-user. On Berkeley
UNIX systems, replace these lines to the /etc/rc.local file:
if [ -f $(SBINDIR)tsapd ]; then
$(SBINDIR)tsapd >/dev/null 2>&1 &
(echo -n ' tsap') > /dev/console
fi
with:
if [ -f $(SBINDIR)iaed ]; then
$(SBINDIR)iaed -D 'ou=Research and ...@cn=services' >/dev/null 2>&1 &
(echo -n ' iae') > /dev/console
fi
On other systems, a similar procedure is followed.
When _i_a_e_d starts, it will connect to the Directory, find the
services contained therein, and start listening as appropri-
ate.
Finally, when the Directory software was installed, this
included a program called _d_a_s_e_d. If you have not already
done so, edit the $(ETCDIR)isotailor file to have these two
lines:
ns_enable: on
ns_address: Internet=domain-name+17006
where "domain-name" is the DNS name or IP-address of the
machine which is running _d_a_s_e_d. This can be a different
machine than the one running the DSA, but it's probably best
to have the local DSA and _d_a_s_e_d running on the same machine.
Next, arrange for _d_a_s_e_d to be started when the machine goes
multi-user. On Berkeley UNIX systems, add these lines to
Sun Release 4.1 Last change: 19th June 1992 11
ISODE-GEN(8) MAINTENANCE COMMANDS ISODE-GEN(8)
the /etc/rc.local file:
if [ -f $(SBINDIR)dased ]; then
$(SBINDIR)dased >/dev/null 2>&1 &
(echo -n ' dase') > /dev/console
fi
On other systems, a similar procedure is followed.
When _d_a_s_e_d starts, it will listen for incoming connections
from initiator ISODE programs. (By default, the initiator
programs aren't loaded with the user-friendly nameservice
and the DAP, owing to the code size--instead, they talk to
_d_a_s_e_d.)
For your other systems, edit the $(ETCDIR)isotailor file to
have these two lines:
ns_enable: on
ns_address: Internet=domain-name+17006
where "domain-name" is the DNS name or IP-address of the
machine which is running _d_a_s_e_d.
To test the system:
% isode-test -iaed
If all goes well, users should be able to type things such
as
% ftam cheetah,sc,psi,us
and "the right thing" will happen (i.e., local users can
access remote services, even if they have not been entered
into the entities database).
Adding New Services
The installation procedures need be performed only once. If
you decide to disable a service, simply remove the
corresponding entry from the Directory. To add a new ser-
vice, see the Section "Defining New Services" in the _U_s_e_r'_s
_M_a_n_u_a_l.
FTAM/FTP gateway
Because the FTAM/FTP gateway is meant to appear as an FTAM
entity, the entry for this service must be placed in a dif-
ferent portion of the DIT than the regular FTAM service. As
such, the _b_o_o_t_s_v_c script will not install this service.
Hence, if you wish to run such a service, you will have to
install it manually. The entry might be something like
Sun Release 4.1 Last change: 19th June 1992 12
ISODE-GEN(8) MAINTENANCE COMMANDS ISODE-GEN(8)
this:
objectClass= top & quipuObject &\
applicationEntity & iSODEApplicationEntity
cn= <<whatever you want>>
presentationAddress= <<unique transport selector>>/<<end-system's NSAP>>
supportedApplicationContext= iso ftam
acl=
execVector= iso.ftam-ftp
Look in your part of the Directory to see some examples of
what these entries look like. The are some scripts
described in _o_t_h_e_r_s/_q_u_i_p_u/_t_o_o_l_s/_s_c_r_i_p_t_s/_R_E_A_D-_M_E which can be
used to maintain such entries.
FILE TRANSFER, ACCESS AND MANAGEMENT
In addition, if you are running the ISODE on a Berkeley or
AT&T System V UNIX system, then there is also an implementa-
tion of the ISO FTAM. FTAM, which stands for File Transfer,
Access and Management, is the OSI file service. The imple-
mentation provided is fairly complete in the context of the
particular file services it offers. It is a minimal imple-
mentation in as much as it offers only four core services:
transfer of text files, transfer of binary files, directory
listings, and file management.
To generate FTAM, go to the isode-8.0 directory and type:
% ./make all-ftam
This will cause a complete generation of the FTAM libraries
and programs. If all goes well, proceed with the installa-
tion. If not, complain as there "should be no problems" at
this step.
You will need to be the super-user to install FTAM:
# ./make install-ftam
That's about it. This will install everything and then
clean-up the source tree. Note that if you are planning on
generating or installing the FTAM/FTP gateway (described
below), then you should not clean-up the source tree until
after you are finished dealing with the gateway. In this
case, or if you just want an installation and no clean-up,
then use:
# ./make inst-ftam
instead.
Sun Release 4.1 Last change: 19th June 1992 13
ISODE-GEN(8) MAINTENANCE COMMANDS ISODE-GEN(8)
FTAM/FTP GATEWAY
In addition, if you are running the ISODE on a Berkeley or
AT&T System V UNIX system, there is also an implementation
of an FTAM/FTP application gateway. The gateway is actually
two programs: one which acts as an ftam responder and an ftp
client, and the other which acts as an ftp server and an
ftam initiator. Note that the gateway currently resides at
a different location than the standard FTAM responder and
FTP server. (This may be corrected in a future release.)
Read the manual entries for _f_t_a_m_d-_f_t_p (8c) and _f_t_p_d-
_f_t_a_m (8c) for the details.
To generate the FTAM/FTAM gateway, go to the isode-8.0
directory and type:
% ./make all-ftam-ftp
This will cause a complete generation of the gateway. If
all goes well, proceed with the installation. If not, com-
plain as there "should be no problems" at this step.
You will need to be the super-user to install the FTAM/FTP
gateway:
# ./make install-ftam-ftp
This will install everything and then clean-up the source
tree. If you just want an installation and no clean-up,
then use:
# ./make inst-ftam-ftp
instead.
Regardless of the command you use, on 4.2BSD-derived sys-
tems, add this line to your /etc/servers file:
ftp-ftam tcp $(SBINDIR)in.ftpd-ftam
On 4.3BSD-derived systems, add this line to your
/etc/inetd.conf file:
ftp-ftam stream tcp nowait root $(SBINDIR)in.ftpd-ftam in.ftpd-ftam
Finally, add this line to your /etc/services file:
ftp-ftam 531/tcp
VIRTUAL TERMINAL
In addition, if you are running the ISODE on a Berkeley UNIX
Sun Release 4.1 Last change: 19th June 1992 14
ISODE-GEN(8) MAINTENANCE COMMANDS ISODE-GEN(8)
system, there is also an implementation of the ISO VT. VT
is the OSI terminal service. The implementation provided is
roughly comparable to an average telnet implementation.
To generate the VT system, go to the isode-8.0 directory and
type:
% ./make all-vt
This will cause a complete generation of the VT initiator
and responder programs. If all goes well, proceed with the
installation. If not, complain as there "should be no prob-
lems" at this step.
You will need to be the super-user to install VT:
# ./make install-vt
That's about it. This will install everything and then
clean-up the source tree. If you just want an installation
and no clean-up, then use:
# ./make inst-vt
instead.
DIRECTORY SERVICES
In addition, if you are running the ISODE on a Berkeley UNIX
or AT&T System V UNIX system, there is also an implementa-
tion of the OSI Directory, called QUIPU. If you're not
interested in running a Directory, skip this text and go to
the section entitled GENERATING DOCUMENTATION.
Each host using the OSI directory implicitly runs a Direc-
tory User Agent (DUA). Additionally, you may wish to run a
Directory System Agent (DSA) on some hosts. As such, the
instructions which follow indicate which activities are
necessary in both instances, as appropriate.
QUIPU GENERATION
To generate QUIPU, go to the isode-8.0 directory and type:
% ./make all-quipu
This will cause a complete generation of the DSAP library
and the DSA. If all goes well, proceed with the installa-
tion. If not, complain as there "should be no problems" at
this step.
Sun Release 4.1 Last change: 19th June 1992 15
ISODE-GEN(8) MAINTENANCE COMMANDS ISODE-GEN(8)
QUIPU INSTALLATION
You will need to be the super-user to install QUIPU: