Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3BF2E32C.4030106@Salira.com>
Date: Wed, 14 Nov 2001 13:33:32 -0800
From: Andrew DeFaria <ADeFaria AT Salira DOT com>
Organization: Salira Optical Networks
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Setup suggestions
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Nov 2001 21:33:32.0469 (UTC) FILETIME=[02336E50:01C16D54]

I have a few suggestions for Cygwin's setup.exe:

1) Setup should be runnable by the command line with no dialog prompting 
at all. This way one could envision an administrator rsh'ing to somebody 
else's machine and installing Cygwin in one command or setting up a cron 
job to periodically insure the user's Cygwin setup is up to date.

2) After setup runs it runs a DOS window doing things like mkpasswd -l > 
/etc/passwd. I would like to be able to specify to setup not to do that 
(after all we are in a domain and -l just isn't appropriate!) but 
instead run my own "finishing touches" script. My script does things 
like sets up inetd, makes a domain password file, adjusting fields as 
needed, etc.

3) Setup will inevitably fail if the user is configured to run inetd as 
a service. Invariably the service will be running because the user 
forgets to stop the service and that makes inetd busy and cygwin1.dll 
busy. Now if I could run setup via a script for totally automated 
installation (see #1 above) and insure that I could do my own finishing 
touches (see #2) then I can easily do a net stop inetd then run setup 
then do my own finishing touches. However I think that setup might be 
made smarter so as to check to see if the inetd service is running and 
turn it off before continuing (and, of course, turn it back on later). 
With the addition of say a -local-setup-script <script> option to setup 
I think that all of this can be automated.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/