Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id:	<199911041603.KAA26434@tigris.pounder.sol.net>
To:	cygwin AT sourceware DOT cygnus DOT com
From:	rodmant AT sol DOT net
Reply-to:	rodmant AT sol DOT net
Subject:	cygwin without an install?
Date:	Thu, 04 Nov 1999 10:03:01 -0600

What impact should we expect if we run cygwin binaries 
without running the installation.  Our goal would be to 
allow our (non-unix literate) users to run some basic 
shell scripts, while avoiding install, upgrade, and 
configuration issues.

For example, if after a single install of cygwin, we copy 
the bin dir to a network drive.  Then we write scripts 
that 100 users run off the network drive.  (We realize 
that certain functionality may be lost.)

I've done some basic searching of the mail archives,
and found some users that prefered the "tarball" approach
to installing cygwin - sort of a simular issue.
 
Can anyone comment on the problems we will run into, and
how we might solve them?

  regards,
 
  Tom Rodman 
 
  Johnson Controls/ Milwaukee WI
  work: Tom DOT Rodman AT jci DOT com
  home: rodmant AT sol DOT net


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -