Date: Tue, 9 Dec 2008 10:16:57 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: ssh-host-config problem on windows 2003, please help.
Message-ID: <20081209091657.GD12905@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <582532.8302.qm@web53310.mail.re2.yahoo.com> <20081208151350.GY12905@calimero.vinschen.de> <493E1E35.2020407@cwilson.fastmail.fm>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <493E1E35.2020407@cwilson.fastmail.fm>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Dec  9 02:28, Charles Wilson wrote:
> Okay. So, suppose we modify the pseudo-code and word the non-auto-answer
> question like the auto-answer=yes case.  Then, somebody looking at a
> manual transcript might ask: I want to run this script "safely" so that
> things are set up, but no services are actually installed and no new
> user accounts are created. Should I use --yes, or --no?  Under this
> modified pseudocode, the answer would be --no, except I think I want
> --yes (e.g. I want the default prived user) for "Do you want to use this
> account name for running this service"
> 
> Anybody have a better idea, that works for both "automated" cases yet
> doesn't confuse the heck out of somebody trying to figure out which of
> --yes or --no to use when implementing their own automation?

A --user option?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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