X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Setup - command line only
Date: Mon, 23 Feb 2009 11:21:35 -0600
Message-ID: <297343D29C14AA4D822142893ABEAEF306090619@srv1163ex1.flightsafety.com>
In-Reply-To: <49A2D900.7010609@gmail.com>
References: <49A1DF61 DOT 5000509 AT gmail DOT com> <49A20419 DOT 4050603 AT cygwin DOT com> <49A21B54 DOT 1030305 AT bmts DOT com> <49A2207E DOT 6030804 AT cygwin DOT com> <49A2A848 DOT 8010907 AT gmail DOT com> <49A2D900 DOT 7010609 AT gmail DOT com>
From: "Thrall, Bryan" <bryan DOT thrall AT flightsafety DOT com>
To: <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
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

Kevin and Nancy wrote on Monday, February 23, 2009 11:13 AM:

> Ok, I take it back.  "setup.exe -q" will work on an SSH remote
> connection.  It remains to be seen if it actually updates packages,
but
> a GUI setup display did not appear on the the local Windows display
with
> a remotely invoked "setup.exe -q".  Thus, I question if "setup.exe -q"
> on a remote SSH session will actually update anything.  Cygnus for
> Windows is "da bom" in my book.  You guys have been great in your
> comments.  Usually postings like this for me results in virtual blank
> stares.

We have a system that uses rlogin to update remote machines with 'setup
-q' and it works just fine. Since setup is a Windows app, it displays on
the remote machine. Of course, when using -q, there isn't much to see
but a flickering window as setup non-interactively goes through the
install/upgrade process.

Setup even returns an error condition if anything went wrong.

A couple of gotchas, though:

*) Since setup remembers the last download location and mirror, etc., it
is a good idea to use the command line flags to set these options every
time, so you know exactly what it will be doing.

*) Running setup non-interactively will bypass warnings (IIRC) about
files-in-use, so if you've got Cygwin processes running, you will need
to reboot after upgrading. You'll have to check the setup log files to
see if there were any files-in-use. Obviously, though, the ideal
situation is to stop all Cygwin processes before running setup :)

HTH

> In reply to Kevin and Nancy, sent at 2009-02-23 7:44 AM :
>>=20
>> I have seen the options that allow to expedite the update process
with
>> a command line, and the GUI is still displayed.  I don't think this
>> works if you're trying to use these options from a SSH remote access,
>> i.e. you'd still need access to Windows to run the setup so the GUI
>> can be displayed.  (I'm not sure on this point exactly.  Seems like I
>> tried it.)  I will look a the link for the source, to see how
>> difficult it may be to assist.
>> Kevin
>>=20
>> In reply to Larry Hall (Cygwin), sent at 2009-02-22 10:05 PM :
>>> Ralph Hempel wrote:
>>>> Larry Hall (Cygwin) wrote:
>>>>=20
>>>>> No, it's only the 289th time, which probably accounts for why you
couldn't
>>>>> find it with Google. ;-)  These kinds of features are missing from
>>>>> 'setup.exe' because there hasn't been a volunteer contributor for
them.
>>>>> If you're interested in contributing something, see the link
below:
>>>>=20
>>>> OK, the update of setup is not supported, but setup DOES in fact
>>>> allow fully command line based operation. I know because I moaned
>>>> about it, collected and tested patches, and even contributed a
minor
>>>> fix to the option parsing.
>>>=20
>>> That's true but I believe the OP was lamenting that there wasn't a
>>> version that didn't still have the GUI even when run from the
command
>>> line.  If I'm wrong, then I'm sure you've made the OP's day. :-)



--=20
Bryan Thrall
FlightSafety International
bryan DOT thrall AT flightsafety DOT com

--
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/