Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date: Fri, 12 Mar 1999 12:11:35 -0800
From: Geoffrey Noer <noer AT cygnus DOT com>
To: Corinna Vinschen <corinna DOT vinschen AT cityweb DOT de>
Cc: Sergey Okhapkin <sos AT prospect DOT com DOT ru>,
        "cygwin32-developers AT cygnus DOT com" <cygwin32-developers AT cygnus DOT com>
Subject: Re: Patch, Version 2: UNIX-like permissions on objects
Message-ID: <19990312121135.A9190@cygnus.com>
References: <01BE6763 DOT 664406B0 AT sos> <36E8C558 DOT BC757DBE AT cityweb DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <36E8C558.BC757DBE@cityweb.de>; from Corinna Vinschen on Fri, Mar 12, 1999 at 08:42:16AM +0100

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.

Opinions?

-- 
Geoffrey Noer		Email: noer AT cygnus DOT com
Cygnus Solutions