Re: Setup suggestions

["Robert Collins" <robert.collins@itdomain.com.au>]

----- Original Message -----
From: "Andrew DeFaria" <ADeFaria@Salira.com>
To: <cygwin@cygwin.com>
Sent: Thursday, November 15, 2001 8:33 AM
Subject: Setup suggestions


> I have a few suggestions for Cygwin's setup.exe:
>
> 1) Setup should be runnable by the command line with no dialog
prompting
...
Great. Check the list archives. See the discussion from a contributor
that says "I am working on command line options". That might be what you
are referring to no? Oh you meant *different* command line options? No.
What then? Oh, Command line options, now I get it.

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

You can recompile setup.exe to do this... but ...
This is an interesting idea. I am making setup more data driven, and
once that is complete we can look at how to allow this. Please have a
think about
* how you will alter the cygwin.com setup.exe to do this without
recompiling it.

> 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

Again, this is in the list archives. sshd causes problems too. Ever run
setup while a bash shell is open - ouch. And yes, solutions are being
tabled, but no-one has done much yet.

Rob


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