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