e?
I assume you could detect them using cygwin *stat calls. Maybe by compiling
against cygwin headers and cygwin1.dll, or maybe by extracting the relevant
code from cygwin sources (you'd have to check the relevant licenses).
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
rted even larger numbers.
I hope I included everything important. If not, I'll be happy to provide more
information.
--
David Macek
Cygwin Configuration Diagnostics
Current System Time: Sun Mar 29 23:59:58 2015
Windows 8.1 Professional Ver 6.3 Build 9600
Path: D:\cygwin64\usr\local\bin
maybe takeown and icacls will be more precise tools
for this task. This is the ACL for my C root:
C:\> icacls .
. NT AUTHORITY\SYSTEM:(OI)(CI)(F)
BUILTIN\Administrators:(OI)(CI)(F)
NT AUTHORITY\Authenticated Users:(OI)(CI)(RX)
BUILTIN\Users:(OI)(CI)(RX)
Mandatory Label\High Mandator
uld be a widely known problem by now. :)
Does setting `set nocp` in .vimrc help? (More possible solutions here:
http://vim.wikia.com/wiki/Fix_arrow_keys_that_display_A_B_C_D_on_remote_shell)
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
h share you are accessing.
Power Users don't have access to (almost) everything, like Administrators do.
The Domain Administrators group is a member of Administrators, so unless I'm
missing something, there's no reason to have them explicitely in the DACL. I'm
not arguing against configurability though.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
On 11. 4. 2015 11:08, Achim Gratz wrote:
> David Macek writes:
>> Power Users don't have access to (almost) everything, like
>> Administrators do. The Domain Administrators group is a member of
>> Administrators, so unless I'm missing something, there's no reaso
s the mask is
>
> rw- | r-- == rw-
>
> Does this explain it sufficiently?
Yes, thank you. My question was about the case where SYSTEM or Administrator
doesn't have the typical permissions. From this explanation, I assume that I
won't be able to see any diffe
onsidered to be
> executable.
According to has_exec_chars, the sniffing routine also looks for "MZ" (EXE/PE
files) and ":\n" (batch files? (can anyone confirm this?)).
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
On 18. 4. 2015 19:21, Steven Penny wrote:
> On Sat, Apr 18, 2015 at 9:47 AM, David Macek wrote:
>> According to has_exec_chars, the sniffing routine also looks for "MZ" (EXE/PE
>> files) and ":\n" (batch files? (can anyone confirm this?)).
>
> Yeah, I
//cygwin.com/cygwin-ug-net/setup-locale.html>
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
dn't find any difference in how `rm` deletes the file nor in how `touch`
creates the file. Just the result of the last NtCreateFile is different
(STATUS_SUCCESS vs. STATUS_DELETE_PENDING).
Thoughts?
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
On 23. 4. 2015 15:25, Nick Hansen wrote:
> Unsubscribe
Are you trying to unsubscribe from a thread, or from the whole mailing list?
Please read:
http://cygwin.com/ml/#unsubscribe-simple
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
x27;m sorry for a late reply. The snapshot seems to fix the issue. Based on a
quick read of your patch, I thought I could break it with a second-level subst
(subst->subst->volume), but it worked even then.
Thank you.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
ses to create NTFS symlinks to non-existing targets. This is due to
a mismatch between NTFS and POSIX symlink semantics.
Given this information, the error you're seeing should now be obvious to you.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
oken states?
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
ed to Cygwin threads, I assume ...
strace shows tmux getting these:
seterrno_from_win_error:
/usr/src/ports/cygwin/cygwin-2.0.2-1.x86_64/src/newlib-cygwin/winsup/cygwin/pinfo.cc:737
windows error 995
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
ad no effect.
--
David Macek
Cygwin Configuration Diagnostics
Current System Time: Fri Jun 05 00:06:23 2015
Windows 8.1 Professional Ver 6.3 Build 9600
Path: D:\cygwin64\usr\local\bin
D:\cygwin64\bin
C:\Windows\System32
C:\Windows
Output from D:\cygwin64\bin\id.exe
UID:
d thanks for clarifying. The issue exists regardless of if you
> pin the running task or you pin the Desktop icon. Pinning the Desktop
> icon will cause a new icon on the taskbar when MinTTY is executing.
> Pinning the open task will cause subsequent task to bypass initial
> startup and be sitting in /usr/bin instead of $HOME.
Pinning the open task and then modifying the pinned shortcut to include the
correct arguments should make it work (both grouping and environment in shell).
Anyway, mintty has reverted the change, so v2.2.2 will probably work just like
the ones before v2.2.1, once released.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
ng regular symlink files. Is this
behaviour intentional / known?
If it matters, the use case is `ln -sf /proc/self/fd /dev/fd`.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
On 18. 11. 2015 18:55, Corinna Vinschen wrote:
> On Nov 17 23:28, David Macek wrote:
>> Hi.
>>
>> I went through the UG looking for differences between regular Cygwin
>> symlinks and NTFS symlinks, but couldn't find this documented. It
>> seems that when usi
On 18. 11. 2015 20:48, Corinna Vinschen wrote:
> On Nov 18 19:13, David Macek wrote:
>> On 18. 11. 2015 18:55, Corinna Vinschen wrote:
>>> On Nov 17 23:28, David Macek wrote:
>>>> I went through the UG looking for differences between regular Cygwin
>>>>
ill absolute paths.
I'm on Windows 10, if it makes any difference.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
urrent use, the
program directory should ideally be read-only and any user-generated state gets
written in per-user directories.
I'm also suspicious of whether advanced filesystem features will work on a
network path, e.g. deleting/updating files/binaries when in use.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
On 20. 11. 2015 10:29, Corinna Vinschen wrote:
> On Nov 19 19:53, David Macek wrote:
>> On 18. 11. 2015 20:48, Corinna Vinschen wrote:
>>> On Nov 18 19:13, David Macek wrote:
>>>> On 18. 11. 2015 18:55, Corinna Vinschen wrote:
>>>>> On Nov 17 23:28, Da
On 20. 11. 2015 10:26, Corinna Vinschen wrote:
> On Nov 19 22:17, David Macek wrote:
>> On 19. 11. 2015 20:36, Nellis, Kenneth wrote:
>>> FWIW, my results are different:
>>>
>>> $ printenv CYGWIN
>>> winsymlinks:nativestrict
>>> $ touch X
Can you describe what purpose does your C:\proc serve? I'm not currently
arguing for or against Corinna's proposal, I'm just curious.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
t.
>
> How to fix this outside Cygwin? (The Windows side)
>
> How to fix this inside Cygwin?
Sounds to me like your login shell is hard-coded to C:/mksnt/sh.exe.
What does `getent passwd $(whoami) | cut -d: -f7` say (run `C:\cygwin\bin\bash
--login -i` directly to get a working shell)?
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
On 26. 11. 2015 12:53, Corinna Vinschen wrote:
> On Nov 24 20:51, David Macek wrote:
>> My test command is `touch 1 && ln -s 1 2`, then I clean up by `rm 1 2`. Now
>> the results:
>>
>> in /bin/: relative
>> in /: absolute
>> in ~/ (/cygdrive
p in the WOW64 layer in terms of starting 64 bit
> processes, perhaps. Sigh, it's a rather unexpected change after it
> worked fine for so long :(
Yup. I can confirm.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
On 1. 12. 2015 18:40, David Macek wrote:
> On 1. 12. 2015 15:01, Corinna Vinschen wrote:
>> On Dec 1 21:07, nu774 wrote:
>>>> There must be a bug in the new CMD somewhere. But, anyway, I'll look
>>>> into it when I finally managed to update my W10 test m
> That's oh so funny: The good old system info doesn't show this anymore.
> But you can look into the new-style "Settings" -> System -> About.
I've always used the trusty `winver` for version info.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
On behalf of Corinna, who says on IRC that her messages don't make it to the
mailing lists (regular, announce, nor overseers), is she getting detected as
spam now (and why)? Or is there some more global issue?
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
t
a very similar (if not the same) error, but more than 2 years ago.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
On 10. 2. 2016 12:58, Corinna Vinschen wrote:
> I replied in the bug tracker.
It seems a fix (or at least a work-around) was implemented based on your
replies. I can now build `file` from trunk without any issues.
Thanks.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
was to run a Linux VM. (e.g. Node.js, the Oracle JVM (as opposed
> to Cygwin’s current JVM alternative, gcc-gcj), Valgrind, etc.)
This is definitely a win for LSW/UoW, because it goes for Linux compatibility.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
On 21. 4. 2016 18:01, John Cowan wrote:
> David Macek scripsit:
>
>> You're assuming LSW will become pre-installed on these workstations and
>> UoW will become a Windows Store "app". I'm not saying it can't happen,
>> but it seems unlikely at the
ot sure
if the sandboxing feature respects these exceptions, but you can always disable
it completely.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
Sorry to hijack an old thread, but I think maybe the problem is not with ldd
not understanding the binary, but with 64-bit libraries being mixed in (due to
the WOW64 redirection not being enabled in some place).
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
fference I see is `sysmain.sdb` being
checked right after `ls.exe` process creation, but that could very well be a
red herring. Unfortunately, ACT seems to be broken on Win10.
I can try watching them side by side in debuggers tomorrow, maybe I'll find
something.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
On 29. 6. 2016 23:45, David Macek wrote:
> I can try watching them side by side in debuggers tomorrow, maybe I'll find
> something.
Yep, found something. TL;DR the issue is that Windows spins a thread in the
process before our DLLs are loaded. Detailed analysis below.
On my Win8
4.065s
> user0m0.000s
> sys 0m0.015s
>
> `ls /cygdrive/c` or `ls /cygdrive/d` take around 0.013s.
Is it possible there's another -- unavailable -- drive letter, and the driver
needs to wait 4 seconds before declaring it unavailable/disconnected?
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
<https://github.com/git-for-windows/git/wiki/Symbolic-Links> for more
information.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
On 10. 8. 2016 3:16, Andrey Repin wrote:
> Greetings, David Macek!
>
>>> As i understand Cygwin will soon no longer support Windows XP resp.
>>> 2003. This means that only Windows versions with native symbolic link
>>> functionality will be supported after
mes
unreadable/untraversable if its type doesn't match the target's type. The most
prominent example where this is an issue is creating symlinks to non-existent
targets.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
as fake (it really wasn't sent by Yahoo, but by
Sourceware). This is only going to happen more and more often as email
providers up the battle against spam.
The best solution is to change the way ezmlm re-sends the messages, I bet
there's a big discussion about it somewhere on the Internet.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
sitive to something like:
>
> "User name via mailinglist "
>
> when the mail is broadcast to the mailing list. I would have done this
> sooner but my ezmlm skills were really rusty and I almost ran out of
> extremities to shoot.
Thanks. By the way, does that inc
2016-12-16 11:55 x86_64 Cygwin
$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="C.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_ALL=
$ /proc/cygdrive/c/Windows/System32/chcp.com
Active code page: 65001
Using the font Consolas.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
On 6. 4. 2017 11:39, Matt D. wrote:
> Why am I getting garbled output with this line present?
Try calling `/proc/cygdrive/c/windows/system32/chcp.com 65001` before running
`dialog ...`. Does that help?
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
On 6. 4. 2017 16:22, Matt D. wrote:
> On 4/6/2017 5:47 AM, David Macek wrote:
>> Try calling `/proc/cygdrive/c/windows/system32/chcp.com 65001` before
>> running `dialog ...`. Does that help?
>
> It does not. I tried setting the code page to 65001 in cmd and/or after
>
). Can you post the output of your `mount`, also `ls foo*` from both
directories?
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
On 13. 4. 2017 16:24, David Macek wrote:
> On 13. 4. 2017 14:34, Chevallier Yves wrote:
>> I get a very different behaviour with `cygpath` after I upgrade my version
>> of Cygwin. Why? and how can I fix it?
>>
>> With Cygwin 2.7:
>>
>> ```
>> $ unam
Hi. I see this:
$ [[ -p /dev/stdin ]] && echo pipe || echo nopipe
nopipe
$ [[ -t /dev/stdin ]] && echo term || echo noterm
noterm
Am I missing something? I tested various scenarios and stdin is never a pipe,
neither a tty for me.
--
David Macek
smime.p7s
Des
. It's okay in the default
case,
it's exactly what was requested in the non-standard font case and it's future
proof in case ConHost implements rendering using fallback fonts.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
On 4. 9. 2018 16:18, Thomas Wolff wrote:
My vote is against the patch because the nodef glyph will often be just blank
space which is certainly worse than ▒.
How often is "often"? Do the default Windows fonts have okay nodef glyphs?
By the way, how does this work with OEM fonts?
gt; echo > foo
> mklink bar foo
symbolic link created for bar <<===>> foo
> del bar
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
ontaining
ssh.exe and dbus-daemon.exe. The installer is available at
<https://cygwin.com/install.html>.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
havior even on Windows 10.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
On 31. 7. 2017 14:36, David Macek wrote:
On 31. 7. 2017 11:48, Corinna Vinschen wrote:
Well, it works for me. I tested this in tcsh, bash and od on
Windows 10.
I tested on Windows 2012 R2 (8.1 equivalent) and I can confirm Steven's
findings. Tried with an older installation and then
PeekConsoleInputW and ReadConsoleInputW,
select is doing the right thing even with CP 65001.
Awesome. Confirming that the new snapshot allows ö to be input in plain bash
with CP 65001.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
<https://cygwin.com/ml/cygwin-announce/2017-02/msg00035.html> for grep
* <https://cygwin.com/ml/cygwin-announce/2017-02/msg00034.html> for gawk
There was also a discussion about these changes at
<https://cygwin.com/ml/cygwin/2017-06/msg00040.html>.
--
David Macek
smime
ygwin primarily strives to be a good *POSIX* platform, so there may be cases
where the two intentionally differ.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
rfc2646.txt> and it would be nice
if the archives site could display it correctly. I can cooperate on this
with the maintainer(s) if they're interested. Essentially, one line of CSS
should fix it, judging by my quick test.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
Please stop breaking the message threads, it's hard to comprehend what's
happening this way. If needed, I can help with configuring your e-mail client.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
n1.dll!acl_get_perm+0x9aa1
cygwin1.dll!_getreent+0x1097
sort.exe+0x5319
sort.exe+0x103e0
cygwin1.dll!cygwin_dll_init+0x11c2
cygwin1.dll!setprogname+0x35c3
cygwin1.dll!setprogname+0x3674
In my experience, stack traces of Cygwin from MS tools are not very realiable.
Can you try GDB as well?
--
David
pport here. Assuming that's the case, the only thing to do here is to add
this to the BLODA.
I actually can't find any mention of a product nor feature called SecureDesktop, so
unless there are better ideas, let's do only "BeyondTrust".
--
David Macek
smime.p7s
Des
it distros use Cygwin code, it might
be
even more useful to ask here (though I assume Johannes subscribes to Git ML and
he would be able to answer all the intricacies pretty accurately).
So far, Tony Kelman's descriptions were pretty spot on (that's why I didn't
respond
to his call
x27;x @') fails.
/w/temp/@ x$ ./hello.bat
'W:\temp\@' is not recognized as an internal or external command,
operable program or batch file.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
apostrophes) when building the command line, despite the comment near
the top of the function.
Do you have a test case for this? In my testing, paths with spaces (like 'x y'
instead of '@ x') work just fine.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
LODA<https://cygwin.com/faq/faq.html#faq.using.bloda> for the
worst offenders, but note that this list is not exhaustive.
--
David Macek
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Microsoft* receives or processes that information.
--
David Macek
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
et/ntsec.html#ntsec-files>, especially
this part:
> This works on all supported versions of Windows. Only the GUIs aren't able
> (or willing) to deal with that order.
--
David Macek
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
t play, but I don't see why it would behave like this.
--
David Macek
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
72 matches
Mail list logo
