Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
X-Injected-Via-Gmane: yes
Path: not-for-mail
From: Andrew DeFaria <Andrew AT DeFaria DOT com>
Newsgroups: gmane.os.cygwin
Subject: Re: Suggestion for setup
Date: Wed, 06 Mar 2002 11:00:55 -0800
Organization: Salira Optical Networks
Lines: 32
Message-ID: <3C866767.7050709@DeFaria.com>
References: <20020306162159 DOT 57702 DOT qmail AT web10508 DOT mail DOT yahoo DOT com>
NNTP-Posting-Host: 206.184.204.2
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: quimby2.netfonds.no 1015441685 31721 206.184.204.2 (6 Mar 2002 19:08:05 GMT)
X-Complaints-To: usenet AT quimby2 DOT netfonds DOT no
NNTP-Posting-Date: 6 Mar 2002 19:08:05 GMT
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us

Rick Rankin wrote:

> Depends on how you define "harmless". We have a *huge* domain, and "mkpasswd
> -d" can take a very long time (20 - 30 minutes) to complete, so I definitely
> wouldn't want to run blindly run it with the -d option here. If it were
> implemented, it should be an option, at least.
> 
> When I run mkpasswd here, I generally run it twice, once to get local machine
> accounts, and once with the -d *and* -u options to get a specific user's info
> from the domain. It might be useful with those options. Hmm, maybe I'll take a
> look at that. It would require some fields in the GUI though...

That's why I lobbied (briefly) for setup to allow the user to specify 
their own setup script - a script to be run automatically after Cygwin 
setup is done. This way the various administrators could determine and 
code their own local customizations as it were.

Personally my setup script does a number of things like setting up 
inetd, cron, etc. One of it's various tasks is to get better passwd and 
group files. I just symlink them to global passwd and group files. I 
know, symlinking /etc/passwd might be considered highly dangerous in 
regular Unix environments however when you think about it in Cygwin you 
don't even really login(1).

(I also symlink a global /etc/profile that has mods to get the user's 
home directory and shell from the global passwd file and actually use 
them. Oh it also sets up some standard, systemwide (or rather site wide) 
mounts such as /home -> //<fileserver>/<homeshare> and I have another 
script which creates the global passwd file and changes home directories 
from the form of \\<fileserver>\<homeshare>\$USER\$ (don't ask me why 
there's a trailing $ sign at the end of the user names) to /home/$USER).




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