delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-developers-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-developers-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin-developers/> |
List-Post: | <mailto:cygwin-developers AT cygwin DOT com> |
List-Help: | <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-developers-owner AT cygwin DOT com |
Delivered-To: | mailing list cygwin-developers AT cygwin DOT com |
Date: | Fri, 14 Dec 2001 12:31:55 -0500 |
From: | Jason Tishler <jason AT tishler DOT net> |
To: | Cygwin-Developers <cygwin-developers AT sources DOT redhat DOT com> |
Subject: | mkpasswd --path-to-home change |
Message-ID: | <20011214123155.B2348@dothill.com> |
Mail-Followup-To: | Cygwin-Developers <cygwin-developers AT sources DOT redhat DOT com> |
Mime-Version: | 1.0 |
User-Agent: | Mutt/1.3.18i |
Currently, mkpasswd's --path-to-home option is only effective if the NT account does not contain home directory information. I would like to change the semantics so that this option *unconditionally* sets the the home directory field. This will make it easier to override what a misguided IT staff is trying to enforce. :,) Does the above sound good? Or, am I misguided... Thanks, Jason
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |