home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!UH01.Colorado.EDU!DWING
- From: DWING@UH01.Colorado.EDU (Dan Wing)
- Newsgroups: comp.os.vms
- Subject: Re: VMSINSTALLable and those .A files HELP!!!
- Message-ID: <01GO90U18XIA0001BH@VAXF.COLORADO.EDU>
- Date: 1 Sep 92 06:17:45 GMT
- Sender: daemon@ucbvax.BERKELEY.EDU
- Distribution: world
- Organization: The Internet
- Lines: 41
-
- Matthew Harttree, Harttree@vax1.elon.edu, writes:
-
- >I notice that many call for VMSINSTALL and are distributed in a format as
- >follows:
- >
- >program.A
- >program.B
- >program.C
- >
- >I know INSTALL well (I think) and I believe VMSINSTALL and INSTALL
- >are two different things.
-
- Yes, very different.
-
- >We are running cmu and MX and they came in
- >this format. My boss did the installation and I cant find a trace of
- >the product.
- >
- >How does one setup and install such packages that come in the above format??
- >If it is a public domain program, could someone provide me with a FTP
- >pointer.
-
- From a privileged account:
-
- $ @SYS$UPDATE:VMSINSTAL product location
-
- For example:
-
- $ @SYS$UPDATE:VMSINSTAL MX031 SYS$SYSDEVICE:[KITS.MX]
-
- See the VMS System Management Master Index under VMSINSTAL - there should
- be pointers to relevent documentation. VMSINSTAL is used by DEC for *all*
- software installations - be familiar with how it works.
-
- Keep in mind that when you run VMSINSTAL, you will run a program, supplied
- by the author of the kit, that will run with all your privileges. Trust
- your source, or examine the program prior to running it!
-
- -Dan Wing, DWING@UH01.Colorado.EDU or WING_D@UCOLMCC.BITNET (DGW11)
- Systems Programmer, University Hospital, Denver
-
-