X-Spam-Check-By: sourceware.org
Date: Sat, 17 Jun 2006 22:36:24 -0400 (EDT)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Richard Foulk <richard AT skydive1 DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: Installed Applications?
In-Reply-To: <200606180222.k5I2MPxp011537@sd.skydive1.com>
Message-ID: <Pine.GSO.4.63.0606172232170.11100@access1.cims.nyu.edu>
References: <200606172338 DOT k5HNci9e005973 AT sd DOT skydive1 DOT com>   <Pine DOT GSO DOT 4 DOT 63 DOT 0606172011450 DOT 11100 AT access1 DOT cims DOT nyu DOT edu>  <200606180222 DOT k5I2MPxp011537 AT sd DOT skydive1 DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Sat, 17 Jun 2006, Richard Foulk wrote:

> > On Sat, 17 Jun 2006, Richard Foulk wrote:
> >
> > > Aloha,
> > >
> > > I'm looking for a good way to determine the software packages
> > > installed on a machine.
> > >
> > > We're hoping to do this remotely on a network of clients by mounting
> > > a client's drive and rummaging around.
> > >
> > > Is there an easy/reliable way to do this with Cygwin?
> >
> > If you've set up sshd on the remote machine, 'ssh MACHINE "cygcheck
> > -cd"' ought to do it.  Otherwise, looking at the drive is probably not
> > going to get you anything reliably (in a way that's guaranteed to
> > always work). For a non-portable hack using the current settings, look
> > at the source of the Cygwin setup program.
> >
> > Incidentally, most software leaves traces in the registry, at
> > well-known keys, so the easiest way to check for it is look in the
> > registry (as it may actually be installed anywhere).  The same is the
> > case with Cygwin (look for "HK(LM|CU)/Software/Cygnus
> > Solutions/Cygwin" -- even though the mount information might be moved
> > out at some point, the key itself will probably stay around).  Though
> > how you intend to browse the registry on a mounted drive is not very
> > clear.
> > HTH,
> > 	Igor
>
> Thanks very much for the response.
>
> This is a large network of clients.  We're hoping not to have to install
> more software on all the clients to monitor them.
>
> Cygwin is a tool on our administrative machines.  (Which is serving us
> well in this capacity so far.)

Whoops, sorry, I misread your question.  I thought you were asking whether
there is an easy way to detect whether Cygwin is installed on the client
machines...

But again, as I said, most Windows software is usually detectable via the
registry, and I don't know of an easy way to read remote registries off a
mounted disk using Cygwin.  Unless your remote machines are Linux, in
which case you might be able to point some packaging tool in Cygwin (e.g.,
rpm, or apt) to the appropriate package database on those machines and use
the query mechanism.  But I'm not very familiar with either apt or rpm, so
you'll probably have to read some manuals to get the exact incantation.
HTH,
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/