Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Message-ID: <19990914005431.15504.rocketmail@web108.yahoomail.com> Date: Mon, 13 Sep 1999 17:54:31 -0700 (PDT) From: Earnie Boyd Reply-To: earnie_boyd AT yahoo DOT com Subject: Re: POSIX and uid_t resp. gid_t To: Corinna Vinschen Cc: cygwin-developers AT sourceware DOT cygnus DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- Corinna Vinschen wrote: > Chris Faylor wrote: > > [...] > > I know that some Unixes have implemented access control lists. > > If you want a model to follow that might be the way to go. > > I know that Digital UNIX implements this, for instance. > > > > -chris > > I don't have access to implementation details of Digital UNIX. > Is their solution POSIX compliant? How can I get infos? > > I fear, the only way is, to have a translation table between > NT SIDs and Cygwin [UG]IDs. Ok, this would have the > advantage to allow Cygwin UID 0 for user `Administrator' and > other mess. The translation could be placed in the /etc/passwd > and /etc/group files which I'd like to eliminate originally. > > Hmmm... on the other hand, this wouldn't be compatible to the > current solution and it would be harder to maintain. > > Any comments? Just thinking outloud, what about using the text Ids for the translation table since it will be a part of the passwd and group files? === Earnie Boyd Newbies, please visit (If you respond to the list, then please don't cc me) __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com