Xref: utzoo comp.sys.pyramid:1110 comp.misc:12352 comp.databases:9870
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!stanford.edu!leland.Stanford.EDU!scmiller
From: scmiller@leland.Stanford.EDU (Susan Miller)
Newsgroups: comp.sys.pyramid,comp.misc,comp.databases
Subject: Help Wanted With Packaging INGRES
Keywords: INGRES, VAR, Pyramid
Message-ID: <1991May1.215722.19620@leland.Stanford.EDU>
Date: 1 May 91 21:57:22 GMT
Sender: scmiller@leland.Stanford.EDU (Susan )
Followup-To: hmortaz@raynet.com, smiller@raynet.com
Organization: AIR, Stanford University
Lines: 30



Fellow INGRES VARs:

We are packaging an application with INGRES 6.3 on Pyramid 
Osx 5.1 and were wondering if there are elegant ways to create 
a single tape of both INGRES and the application; without driving 
our support people crazy during installation.  

I am advised that INGRES VAX/VMS VARS create a subdirectory under 
ingres and copy all their application code into this subdirectory 
before writing everything to a single tape. Anyone else with better 
alternatives and suggestions for Unix platforms?! Anyone using cpio?!  

Also, has anyone found an elegant way to prevent end-user access to 
all the enabled INGRES modules (QBF, VIFRED, RBF, RW) included with the 
Embedded INGRES!?! I am looking for a solution other than changing 
the file protection or removing the executables from ingres/bin.  The 
VAR authorization string associated with Embedded INGRES does allow 
access to these modules which will create security problems for our 
application.   

Thanx very much for all the help.  

----------------------------------------------------------------------
H. Mortaz            hmortaz@raynet.com
Raynet Corporation
185 Constitution Drive 
Menlo Park, CA 94025-1164
(415) 324-6638