X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 23 Apr 2009 13:27:12 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: MS-DFSR conflict with cygwin file permissions Message-ID: <20090423172712.GA28739@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <49EFBEA8 DOT 8070609 AT lisec-sw DOT com> <49EFC69E DOT 3060402 AT cygwin DOT com> <49EFD253 DOT 40107 AT lisec-sw DOT com> <49EFE9E2 DOT 104 AT cygwin DOT com> <49EFF80D DOT 6000300 AT lisec-sw DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49EFF80D.6000300@lisec-sw.com> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Thu, Apr 23, 2009 at 03:09:33PM +1000, Stefan Walter wrote: >The loss of the POSIX permissions is fine for me. But what is then the >purpose of tty in the CYGWIN variable? In the context of sshd, setting CYGWIN=tty makes no sense whatsoever. This has been a longstanding source of confusion which has gotten into the cygwin meme. For some reason, people think that they need to set CYGWIN=tty for programs which would never end up using it. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/