delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
DomainKey-Signature: | a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id |
:list-unsubscribe:list-subscribe:list-archive:list-post | |
:list-help:sender:date:from:to:subject:message-id:reply-to | |
:references:mime-version:content-type:in-reply-to; q=dns; s= | |
default; b=d0W8eUpKyPuZ4nT+ylFnXXHkv61O0LVSZU3sqDwONBpR0h6mTCTVv | |
0NSN9e/nk1fNPnUwZdBhx1RIxeolfDFn63k7Jy5VFzDcfvkebdFXOBUlr2KCAwwa | |
6UZIHjUxYNyfoEk7kux1hy9dYVfK1JXwcAp1jR43hPW1HarPBM/yV0= | |
DKIM-Signature: | v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id |
:list-unsubscribe:list-subscribe:list-archive:list-post | |
:list-help:sender:date:from:to:subject:message-id:reply-to | |
:references:mime-version:content-type:in-reply-to; s=default; | |
bh=E579+69JkSvSO9DLtSHt5mFSU6o=; b=VH3jGj83V07ryvBnWiR090XKE7Cx | |
h38+OPN1Rmqg38DsoPo6QdJyiQWZOJodJwinoaJfL+iUjBn6Y0TNPAFGpM+rvas0 | |
+5zP/L0hRCK+epvZeZeZnEFJGeTLWkMyerFU6QA2Uh/CY8nyndBvkE+wZGj4vmJM | |
zJ4g5nkTDiEjwbI= | |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Authentication-Results: | sourceware.org; auth=none |
X-Virus-Found: | No |
X-Spam-SWARE-Status: | No, score=-4.5 required=5.0 tests=AWL,BAYES_20,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 |
X-HELO: | calimero.vinschen.de |
Date: | Sat, 2 May 2015 15:47:01 +0200 |
From: | Corinna Vinschen <corinna-cygwin AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: Problems with screen on Windows 10 Preview system |
Message-ID: | <20150502134701.GC12723@calimero.vinschen.de> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
References: | <CANnLRdjiHWKS8VBzTs0dh5K3h+3raffCeDN-JBu+HHic+FduVA AT mail DOT gmail DOT com> |
MIME-Version: | 1.0 |
In-Reply-To: | <CANnLRdjiHWKS8VBzTs0dh5K3h+3raffCeDN-JBu+HHic+FduVA@mail.gmail.com> |
User-Agent: | Mutt/1.5.23 (2014-03-12) |
--jy6Sn24JjFx/iggw Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On May 1 17:32, Stephen John Smoogen wrote: > I downloaded and installed a copy of Windows 10 on a spare system to > see how Cygwin works. Most of the applications worked similarly to > what I was testing on my Windows 7 system. However I have run into a > problem with the screen command. >=20 > The first time I run screen the command gives me a standard help > screen and data. If I type exit to get back to mintty and then > type screen again.. I get: >=20 > Directory '/tmp/uscreens' must have mode 777. >=20 > Which after going through the faq and old mailing list was > something that occurred on FAT partitions. So I went to check the > install and the file format is NTFS. I then looked at /tmp and > got >=20 > drwx---rwt+ 1 smoog smoog 0 May 1 16:01 uscreens You're using a "Microsoft Account", one of those for twhich the primary group SID is set to the same SID as your user account has. So uid=3D=3Dgid=3D=3Dthe exact same SID. The group "smoog" is NOT a group cal= led "smoog", it's your user account. This leads to a chicken-egg problem: Either Cygwin sets the group permissions in the POSIX permission attributes to the same value as the user permissions, e.g. rwxrwxr-x then security-sensitive POSIX applications will complain that the permissions are too wide-open. Or, Cygwin sets the group permissions to 0, e.g. rwx---r-x Then, apparently, screen complains. There would be a third way, which is, to spill the "other" permissions into the group permissions, in my example: rwxr-xr-x That should work, but needs YA patch to Cygwin and needs some testing. Bad timing right now (vaca). Workaround: Set the primary group to the affected files explicitely to an existing group which is in your user token. That would typically be the group "users", e.g. chgrp users /tmp/uscreens should work, and then you can chmod it and screen should stop complaining. HTH, Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --jy6Sn24JjFx/iggw Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVRNVVAAoJEPU2Bp2uRE+geE8P/1ikoQcX0oAtvThnItle221Z poCFpxFjAFazT//qeJboupQK67MaBPtclaJ1M0BgckMbjIUr4IEdlyPOMiuTjxuv VWcc4h1M689b0h/7uH65KWNS8JGRLGWTrwywqVvS+/Wd42WdVR3i5ehiiJE9xMi3 DLxp0kLxVH/6W+05/PqZTiwmO2icnTy59p254tt0FUCwMqi5otd3bNsQWRCKp7C8 2TrPS7sur3ZWf8wuMoUof4ufNw8mBISzAjQ3RTom8MtwCiP8xbfUmgDvX2vkSoHe 50yzolPBvEjgEv1Ia1JIpmPt+jAk2iKJ1/E9XqtduJbVyZdQeb2mI2CQWFHJegWy Kz18pwYEAWo9lZ1wkR8uv79sNjeKhivyKZcmG4+EbCJhkKHQWPIcTmz+mYt0LlGu cs3Vrd956SlRwSkHkXH+3YKkBZFtr/YcbJZPgJPbTidMAXe45Ga3Err6X7VpUm2G culvqxOKviE9D4MihjrSWjySW8JvQnjGzHHALbrbM8hZ1OzSKzWzaUrzq7UXsETU jTfJ7puGu0uXAFxaBEiirmBHrVjy64vUIsKZrN+hzad912ZHGcuH1lQ6duaGg7MB pNY2eLjRQlgrq1EJJ2dGqgo+aVa+dt9UPeg4zOJl85o3/07ZYmqEXDiabEQn9/Tt qb9pyYXvWMC5EhEFpEYT =lAfB -----END PGP SIGNATURE----- --jy6Sn24JjFx/iggw--
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |