This is the mail archive of the email@example.com
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: Geoffrey Noer <firstname.lastname@example.org>
- Subject: Re: Patch, Version 2: UNIX-like permissions on objects
- From: Corinna Vinschen <email@example.com>
- Date: Fri, 12 Mar 1999 22:31:04 +0100
- CC: Sergey Okhapkin <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>
- Delivered-To: email@example.com
- Delivered-To: mailing list firstname.lastname@example.org
- Mailing-List: contact email@example.com; run by ezmlm
- References: <01BE6763.664406B0@sos> <36E8C558.BC757DBE@cityweb.de> <19990312121135.A9190@cygnus.com>
- Sender: firstname.lastname@example.org
Geoffrey Noer wrote:
> 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.
So, IMHO, we already (nearly) do, what should be done! The inetd
of the remote package already read NT password, the passwd utility
sets the password.
To read also comment and home directory from NT user database is
a trivial thing.
But the problem, from my point of view, is the attachment of a user
to the primary NT group.
Exists a useful solution for this problem anywhere???