X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=AWL,BAYES_05,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Thorsten Kampe Subject: Re: Read only flag in C:\cygwin\tmp Date: Sun, 29 Mar 2009 18:48:13 +0200 Lines: 53 Message-ID: References: <49CE0DB9 DOT 8030106 AT googlemail DOT com> <49CE2760 DOT 3000309 AT googlemail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit User-Agent: MicroPlanet-Gravity/2.71.11 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 * wishi (Sat, 28 Mar 2009 14:34:24 +0100) > Thorsten Kampe schrieb: > > * wishi (Sat, 28 Mar 2009 12:44:57 +0100) > >> After the initial setup on a Windows XP SP III Cygwin's setup.exe > >> creates a Read-Only folder. That normally isn't that big of a > >> problem, but screen needs \tmp. > >> > >> I tried to change the attributes without any success. > >> > >> What do you need to do to change that? > > > > Nothing. Windows doesn't have the concept of "read-only" folders. > > Neither has Cygwin. > > > If I on my Windows XP SP III box right click on a folder, "Read-Only" > is listed in the folder's properties. You're misinterpreting what you see there. The box means "not defined" (or more precisely: "I don't know"). In the description of the box it says "only applies to file in folders". If you look at your other directories you will see that all have the same "non property". If you understand German read [1]. Knowledgebase article 326549[2] explains the details. > Maybe I should have mentioned that I use NTFS. > [...] > > My initial problem is that cygwin hangs if I start the GNU screen > untility. Cygwin is an environment and a DLL and cannot "hang". What exactly hangs? Screen? Or the shell you want to start in it? How do you notice that it "hangs"? > $ ls /tmp/uscreens/ > S-Administrator > > So my thought was that this socket isn't initialized due permission > problems. > I guess the Windows file attributes aren't the cause of this problem. > I have a fresh install and no .screenrc, that might interfere with the > starting process... There was a "Directory '/tmp/uscreens' must have mode 777." bug with screen on FAT. That has been fixed long ago. I suggest you start with http://cygwin.com/problems.html and especially focus on http://cygwin.com/faq/faq.using.html#faq.using.bloda . Thorsten [1] [2] http://support.microsoft.com/?id=326549 -- 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/