Greetings, cyg Simple!
>>> Explain, please? How exactly you're testing it, and what you're observing?
>>> I don't see any issues with noacl cygdrive mount in that regard.
>>
>> http://cygwin.com/ml/cygwin/2014-08/msg00179.html
>>
> I am assuming that this is an issue with the host you're trying t
Greetings, Steven Penny!
> On Sat, Nov 22, 2014 at 7:54 PM, Andrey Repin wrote:
>> Explain, please? How exactly you're testing it, and what you're observing?
>> I don't see any issues with noacl cygdrive mount in that regard.
> http://cygwin.com/ml/cygwin/2014-08/msg00179.html
You know, unless y
On Sat, Nov 22, 2014 at 10:49 PM, Steven Penny wrote:
> On Sat, Nov 22, 2014 at 7:54 PM, Andrey Repin wrote:
>> Explain, please? How exactly you're testing it, and what you're observing?
>> I don't see any issues with noacl cygdrive mount in that regard.
>
> http://cygwin.com/ml/cygwin/2014-08/msg0
On Sat, Nov 22, 2014 at 7:54 PM, Andrey Repin wrote:
> Explain, please? How exactly you're testing it, and what you're observing?
> I don't see any issues with noacl cygdrive mount in that regard.
http://cygwin.com/ml/cygwin/2014-08/msg00179.html
--
Problem reports: http://cygwin.com/proble
Greetings, Steven Penny!
>> add the noacl flag to the cygdrive entry in /etc/fstab.
> Hm, after further testing, the noacl flag kills tab completion.
Explain, please? How exactly you're testing it, and what you're observing?
I don't see any issues with noacl cygdrive mount in that regard.
--
W
On Fri, Nov 21, 2014 at 11:15 AM, Corinna Vinschen wrote:
> add the noacl flag to the cygdrive entry in /etc/fstab.
Hm, after further testing, the noacl flag kills tab completion.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation
On Fri, Nov 21, 2014 at 11:15 AM, Corinna Vinschen wrote:
> add the noacl flag to the cygdrive entry in /etc/fstab.
Ah yes, thanks!
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscrib
On Nov 21 10:47, Steven Penny wrote:
> On Fri, Nov 21, 2014 at 4:28 AM, Corinna Vinschen wrote:
> > The permission settings are wrongly evaluated as permissions of a "shared"
> > folder, since Vista AFAIR.
>
> In this situation Cygwin creates these extra entries
>
> - CREATOR OWNER
> - CREATOR G
On Fri, Nov 21, 2014 at 4:28 AM, Corinna Vinschen wrote:
> The permission settings are wrongly evaluated as permissions of a "shared"
> folder, since Vista AFAIR.
In this situation Cygwin creates these extra entries
- CREATOR OWNER
- CREATOR GROUP
- Steven
- None
so how is it Windows fault in t
On Nov 20 22:24, Steven Penny wrote:
> Tested on Windows 7
>
> 1. Create a Homegroup
> 2. cd C:/Users
>
> Now, if you run a command like this
>
> mkdir C:/Users/foo
>
> all is well.
Depends on your POV. When using a DOS path, you're getting default
Windows permissions, as documented. No
Tested on Windows 7
1. Create a Homegroup
2. cd C:/Users
Now, if you run a command like this
mkdir C:/Users/foo
all is well. However if you run a command such as this
mkdir foo
"foo" then has strange permissions. If you try to delete using Window Explorer,
you get this message
Th
11 matches
Mail list logo