Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 23 Jan 2003 10:00:20 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: NTEA extensions for uid/gid Message-ID: <20030123090020.GR29236@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3E2F19E0 DOT 8010301 AT csgsystems DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E2F19E0.8010301@csgsystems.com> User-Agent: Mutt/1.4i On Wed, Jan 22, 2003 at 11:23:28PM +0100, Christian Mueller wrote: > Thus, I went ahead and modified ntea.cc and security.cc to support > uid/gid in addition to the file mode. The modified version now uses > three extended attributes: > > .UNIXATTR - file mode (same as in current versions) > .UNIXUID - UID (file owner) > .UNIXGID - GID (file group) > [...] I like the idea. I don't like ntea but that's a completely different thing... > What I'm looking for right now is some feedback on this idea. > Naturally, I would like those modifications to end up in the Cygwin > core distribution but this probably needs to be discussed properly > before being considered. I added the source changes at the bottom of > this email. They are not complete, yet, but already work for me and > should be good enough for discussion. First step is to read http://cygwin.com/contrib.html carefully. Especially important is the fact, that we need a copyright assignment from you before we can consider to look into your changes. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/