2016-04-18 15:25 GMT+02:00 Gerrit Haase wrote:
> my thought was, that UoW maybe requires (X) to access a file,
> because this is the bit missing from these files, and of course this
> is most probably a bug in UoW, if adding (X) is the solution to access
> Cygwin created files from UoW.
And this
2016-04-15 13:38 GMT+02:00 Corinna Vinschen wrote:
> On Apr 15 10:48, Gerrit Haase wrote:
>> 2016-04-14 11:11 GMT+02:00 Evgeny Grin wrote:
>> > Back to cmd:
>> > @ icacls cmd-file
>> > cmd-file DESKTOP-5PNH8IH\Karlson:(RX)
>> > DESKTOP-5PNH8IH\Karlson:(I)(F)
>> > Everyone:(I)(RX)
On 15.04.2016 11:48, Gerrit Haase wrote:
> BTW. who is Karlson?
It's Karlson på taket.
:)
--
Best Wishes,
Evgeny Grin
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:
On 15.04.2016 14:38, Corinna Vinschen wrote:
> On Apr 15 10:48, Gerrit Haase wrote:
>> 2016-04-14 11:11 GMT+02:00 Evgeny Grin wrote:
>>> Back to cmd:
>>> @ icacls cmd-file
>>> cmd-file DESKTOP-5PNH8IH\Karlson:(RX)
>>> DESKTOP-5PNH8IH\Karlson:(I)(F)
>>> Everyone:(I)(RX)
>>>
>>> @
> It's 100% RFC 1178 compliant,
I have never seen that before. That's awesome. Thanks for that.
I do have one thing they missed: I once named a machine "Null". Screwed up the
whole network.
I find it interesting that the string representation of "Null" is actually used
for some networking p
Gerrit Haase scripsit:
> > cowan@large-skunk ~
>
> LOL, love your machines hostname ;)
It's 100% RFC 1178 compliant, and has the big advantage that it is almost
never in use on any network I belong to, so my home machines are always
called some variant of "skunk", and my work machines too when I
On Apr 15 10:48, Gerrit Haase wrote:
> 2016-04-14 11:11 GMT+02:00 Evgeny Grin wrote:
> > Back to cmd:
> > @ icacls cmd-file
> > cmd-file DESKTOP-5PNH8IH\Karlson:(RX)
> > DESKTOP-5PNH8IH\Karlson:(I)(F)
> > Everyone:(I)(RX)
> >
> > @ icacls cygsh-file
> > cygsh-file DESKTOP-5PNH8IH\
2016-04-14 11:11 GMT+02:00 Evgeny Grin wrote:
> Back to cmd:
> @ icacls cmd-file
> cmd-file DESKTOP-5PNH8IH\Karlson:(RX)
> DESKTOP-5PNH8IH\Karlson:(I)(F)
> Everyone:(I)(RX)
>
> @ icacls cygsh-file
> cygsh-file DESKTOP-5PNH8IH\Karlson:(R,W,D,WDAC,WO)
>DESKTOP-5PNH8IH\Ka
2016-04-15 2:50 GMT+02:00 John Cowan wrtites:
> cowan@large-skunk ~
LOL, love your machines hostname ;)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.c
KARL BOTTS scripsit:
> Did the inability of UoW to read a Cygwin created file ever get explained?
See the long post I just sent out.
> And then, an interesting question. Suppose we Cygwin users think we have
> identified a defect in UoW. Do we notify the MS people? Whom and how? I
> guess I
Did the inability of UoW to read a Cygwin created file ever get explained?
Last I saw was from Evgeny Grin, which contained the iacls dumps.
What jumps out is that the non-Cyg files have X perms, the Cyg file does not.
I assume others noticed that. Of course, X perms should not be needed to re
Gerrit Haase scripsit:
> Seems to be a permission issue, can you provide the output of:
>
> icacls file1
> icacls file2
Here they are:
cowan@large-skunk ~
$ icacls file1
file1 NULL SID:(DENY)(Rc,S,X,DC)
LARGE-SKUNK\cowan:(R,W,D,WDAC,WO)
NT AUTHORITY\SYSTEM:(DENY)(S,X)
BUILTIN\
Need to add that I'm using latest Cygwin64:
$ uname -r
2.5.0(0.297/5/3)
On 14.04.2016 12:11, Evgeny Grin wrote:
> I can reproduce the problem.
> Win10 Enterprise Build 14316 Insider Preview
> Commands:
> On cmd:
> @ echo test1>cmd-file
>
> On Cygwin sh:
> $ echo test2>cygsh-file
>
> On UoW bash
I can reproduce the problem.
Win10 Enterprise Build 14316 Insider Preview
Commands:
On cmd:
@ echo test1>cmd-file
On Cygwin sh:
$ echo test2>cygsh-file
On UoW bash sh:
# echo test3>uowsh-file
# cat cmd-file
test1
# cat cygsh-file
cat: cygsh-file: Permission denied
# cat uowsh-file
test3
# ls -ali
On 13.04.2016 16:36, Eliot Moss wrote:
> I tried it myself
> and found that cmd's echo adds a space after "stuff". If I do:
> c:\Users\moss> echo stuff> file1
> (Note: no space before the > !)
> It writes "stuff" without the extra space.
cmd's echo doesn't add anything. It's just completely diff
Greetings, John Cowan!
>> You can use the cygwin od (octal dump) command to see the exact byte
>> contents of the files.
> The exact contents aren't the point. The point is that file1, created
> under Cygwin, is not readable by UoW (or writable either), whereas file2,
> created by very similar m
How about the perms on the dir containing the file?
---
Karl Botts, kdbo...@usa.net
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscrib
2016-04-13 17:43 GMT+02:00 John Cowan writes:
> The exact contents aren't the point. The point is that file1, created
> under Cygwin, is not readable by UoW (or writable either), whereas file2,
> created by very similar methods under Win32 proper, is readable and
> writable by UoW.
Seems to be a
Eliot Moss scripsit:
> You can use the cygwin od (octal dump) command to see the exact byte
> contents of the files.
The exact contents aren't the point. The point is that file1, created
under Cygwin, is not readable by UoW (or writable either), whereas file2,
created by very similar methods und
On 4/13/2016 9:11 AM, John Cowan wrote:
LLoyd scripsit:
John, if you can confirm?
Exactly right.
Please also provide the "cat /mnt/c/file1" and "cat /mnt/c/file2" from UoW.
From the Cygwin shell (note that my Cygwin and Windows home directories
are the same: /home/cowan is a Cygwin syml
LLoyd scripsit:
> John, if you can confirm?
Exactly right.
> Please also provide the "cat /mnt/c/file1" and "cat /mnt/c/file2" from UoW.
>From the Cygwin shell (note that my Cygwin and Windows home directories
are the same: /home/cowan is a Cygwin symlink to /cygdrive/c/Users/cowan):
cowan@lar
That's what he is saying. Apparently, doing:
/cygdrive/c $ echo stuff > file1
and doing
C:\> echo stuff > file2
Does not produce exactly the same files.
John, if you can confirm?
Please also provide the "cat /mnt/c/file1" and "cat /mnt/c/file2" from UoW.
Regards,
LLoyd
On 13 April 2016 at 19:01,
2016-04-13 7:22 GMT+02:00 John Cowan wrote:
>
> When a file is created under Cygwin, ...
What do you mean "under Cygwin"? I always thought that there is no
difference at all, creating files worked always transparently for me,
given that the permissions were correctly set.
Regards,
Gerrit
--
Pro
After many years as a contented Cygwin user, I decided to check out
the new Ubuntu on Windows (UoW) product from Microsoft. I promptly
ran into a nasty problem. I have filed it with the MS Feedback Hub,
but I thought I should post here as well.
When a file is created under Cygwin, it can neither
24 matches
Mail list logo
