From: Andrew DeFaria <ADeFaria@Salira.com>
To: cygwin@cygwin.com
Subject: Setup suggestions
Date: Sun, 11 Nov 2001 08:26:00 -0000 [thread overview]
Message-ID: <3BF2E32C.4030106@Salira.com> (raw)
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/
next reply other threads:[~2001-11-14 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-11 8:26 Andrew DeFaria [this message]
2001-11-11 8:26 ` Robert Collins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BF2E32C.4030106@Salira.com \
--to=adefaria@salira.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).