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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=QI
	gusOvwxT65YElHlXYhKD1xBEfCt0iJTCACoVBKizBVwCDFRl6G7s6q7CTXIGvKna
	QWP0WRM6jO6fwUFELHKl6cO6g2mQYWjMaI2zScsPfNe7aKvdkwHId1GuWu7e/RHW
	lF0o57RB/Qnbj8+MCKlKdo0PY3JMFMEf+/I7n2Byg=
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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=2K2uKCUW
	tkuTr7hudTdS8brlYuA=; b=VdHUoQxj7CKmzwOAFpCTCLIhXFaRr8Bw8AKPdHQm
	wrkNDSvy7zZ09vyDCiYSx2OGF1/d1Do/Fb9QwW6hh+Wpgu0ynn82gTYQlJhzYvOm
	X27mV/2m0VIFGD9L61Zgyu29EYcqkSHz1k94C2YxIuYg3531EaDqNjIVFGcQST5s
	ZrA=
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=2.4 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-qk0-f173.google.com
MIME-Version: 1.0
X-Received: by 10.140.92.181 with SMTP id b50mr17783830qge.72.1430589097757; Sat, 02 May 2015 10:51:37 -0700 (PDT)
In-Reply-To: <20150502134701.GC12723@calimero.vinschen.de>
References: <CANnLRdjiHWKS8VBzTs0dh5K3h+3raffCeDN-JBu+HHic+FduVA AT mail DOT gmail DOT com>	<20150502134701 DOT GC12723 AT calimero DOT vinschen DOT de>
Date: Sat, 2 May 2015 11:51:37 -0600
Message-ID: <CANnLRdgGktkROkekReY9wWmdybQgMntY+wRhuctj=MYTUZ4NMw@mail.gmail.com>
Subject: Re: Problems with screen on Windows 10 Preview system
From: Stephen John Smoogen <smooge AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes

On 2 May 2015 at 07:47, Corinna Vinschen <corinna-cygwin AT cygwin DOT com> wrote:
> 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.
>>
>> 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:
>>
>> Directory '/tmp/uscreens' must have mode 777.
>>
>> 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
>>
>> 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==gid==the exact same SID.  The group "smoog" is NOT a group called
> "smoog", it's your user account.  This leads to a chicken-egg problem:
>

Oooooh that explains a lot. I was figuring there was an issue with my
account but I wasn't sure if this was a new one due to Windows 10
preview, or something I didn't know about Windows account systems.
[Time to get a book on deep Windows internals and administration.]


> 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.
>

Thank you for answering while you are on vacation. I am going to see
if a /etc/passwd and /etc/group entry to better fix that long term.



>
> HTH,
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Maintainer                 cygwin AT cygwin DOT com
> Red Hat



-- 
Stephen J Smoogen.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple