This is the mail archive of the firstname.lastname@example.org
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: Patch, Version 2: UNIX-like permissions on objects
- To: Corinna Vinschen <email@example.com>
- Subject: Re: Patch, Version 2: UNIX-like permissions on objects
- From: Geoffrey Noer <firstname.lastname@example.org>
- Date: Fri, 12 Mar 1999 12:11:35 -0800
- Cc: Sergey Okhapkin <email@example.com>, "firstname.lastname@example.org" <email@example.com>
- Delivered-To: firstname.lastname@example.org
- Delivered-To: mailing list email@example.com
- In-Reply-To: <36E8C558.BC757DBE@cityweb.de>; from Corinna Vinschen on Fri, Mar 12, 1999 at 08:42:16AM +0100
- Mailing-List: contact firstname.lastname@example.org; run by ezmlm
- References: <01BE6763.664406B0@sos> <36E8C558.BC757DBE@cityweb.de>
- Sender: email@example.com
On Fri, Mar 12, 1999, Corinna Vinschen wrote:
> How would you like to get the information about the users
> default shell???
Consider shadow passwd files on Unix. The actual passwords are
stored elsewhere; this is a little like what we're already doing
with Cygwin in that the passwds are kept in the Windows OS.
We can continue to use a physical /etc/passwd as an optional file to
keep home directories and shells but have Cygwin handle the rest?
If a user doesn't have an /etc/passwd entry, then slash would be
their home and bash would be their default shell.
Geoffrey Noer Email: firstname.lastname@example.org