Greetings, Stephen John Smoogen!
>> 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, C
On May 2 11:51, Stephen John Smoogen wrote:
> On 2 May 2015 at 07:47, Corinna Vinschen wrote:
> > On May 1 17:32, Stephen John Smoogen wrote:
> > Workaround: Set the primary group to the affected files explicitely to
> > an existing group which is in your user token. That would typically be
>
On 2 May 2015 at 07:47, Corinna Vinschen 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
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
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
5 matches
Mail list logo
