Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Message-ID: <007f01c1c4f4$b4a6f730$0200a8c0@lifelesswks>
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Bernard Dautrevaux" <Dautrevaux@microprocess.com>,
   "Stephano Mariani" <sk.mail@btinternet.com>, <cygwin@cygwin.com>
References: <17B78BDF120BD411B70100500422FC6309E4AF@IIS000>
Subject: Re: Suggestion for setup
Date: Wed, 6 Mar 2002 20:53:00 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


===
----- Original Message -----
From: "Bernard Dautrevaux" <Dautrevaux@microprocess.com>

> On the same ground, it would be nice if, when creating /etc/passwd and
> /etc/group, setup.exe pass the "-d" flag to mkpasswd/mkgroup;
otherwise,
> ntsec is almost unusable for the (vast majority of) NT/2k/XP users
that
> happen to be in a Windows domain.
>
> I don't know what happens if "mkpasswd -d" is used on 9x/Me if not in
a
> domain, but this seems harmless on NT/2k/XP, so always passing -d
seems
> harmless in these cases.
>
> In fact for our own use, we package cygwin on the same CD as our own
product
> (with full source of course) and our own install procedure just
overwrites
> (after asking the user) the cygwin-setup generated files by calling
> mk{passwd,group} with "-d".
>
> Sorry for not providing a patch, but it should be fairly
straightforward for
> anybody used to working on setup.exe sources :-)

Well, as this is one of the things that are about to move out of
setup.exe, and into install-scripts of one sort or another, the
setup.exe source doesn't really matter :}.

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/