OK - I just re-read the ntsec portion of the cygwin manual and found this
paragraph:
> This has the following unfortunate consequence. Consider a service
> started under the SYSTEM
> account (up to Windows XP) switches the user context to DOMAIN\my_user
> using a token created
> directly by ca
Andy Koppe wrote:
2009/11/15 aputerguy:
>> why does
>> cygwin 1.5 seem to encode it as \357\200\272
> What do you mean? 1.5 doesn't know anything about Unicode filenames.
Well I'm using Putty to ssh into my Windows machine running cygwin 1.5
When I do tab completion on the "foo:bar" file it comp
Dave Korn writes...
> So, it just doesn't work, and that's using all MS software; it's not
> going
> to work any better in bash. I think you're probably out of luck here; I
> don't
> know any way to capture direct console output like that (short of some
> sort of
> screen scraper or even if you
aputerguy wrote:
> Dave Korn writes:
> Yes the output (both stderr and stdout) appear on screen
>
>> I checked: you can't redirect its error output at all, even in a genuine
>> cmd.exe shell with cygwin having nothing to do with it. It must indeed
>> be using the console directly. Curiouser and
2009/11/15 aputerguy:
>> I'd suspect the support for ADSs in 1.5 was rather accidental anyway.
>> POSIX programs certainly don't know about them, and you get the rather
>> weird situation that "files" like foo:bar can be accessed but don't
>> show up in the directory they're in.
>
> Fair point. But
On Sun, Nov 15, 2009 at 02:53:24PM -0800, Martin Dorey wrote:
>>Before the reloc changes, you'd already get an error if your program
>>used ctype functions.
>
>Thinking it might be useful to get the error messages into the
>googlotron, I tried to demonstrate this with little programs like this:
>
>
Andy Koppe writes:
> I'd suspect the support for ADSs in 1.5 was rather accidental anyway.
> POSIX programs certainly don't know about them, and you get the rather
> weird situation that "files" like foo:bar can be accessed but don't
> show up in the directory they're in.
Fair point. But also hav
2009/11/15 Martin Dorey:
>> Before the reloc changes, you'd already get an error if
>> your program used ctype functions.
>
> Thinking it might be useful to get the error messages into the googlotron, I
> tried to demonstrate this with little programs like this:
>
> $ cat /tmp/ctype.c
> #include
> Before the reloc changes, you'd already get an error if
> your program used ctype functions.
Thinking it might be useful to get the error messages into the googlotron, I
tried to demonstrate this with little programs like this:
$ cat /tmp/ctype.c
#include
int main() {
return tolower(' ');
2009/11/15 aputerguy:
> In cygwin 1.7
> $ ls -1s foo*
> 1 foo:bar
> 1 foo:baz
>
> Which might seem ok,
> *But* now explorer shows two files
> foo[]bar
> foo[]baz
> where [] is a square box indicating an illegal symbol.
The square box doesn't represent an illegal symbol but one that the
font being
Cygwin 1.7 seems to have lost support for NTFS Alternative Data Streams --
which it seems not to either create or read (vs. Cygwin 1.5 behavior) --
specifically,
$ echo "dog" > foo:bar
$ echo "cat" > foo:baz
$ cat foo:bar
dog
$ cat foo:baz
dog
In Cygwin 1.5
$ ls -s foo*
0 foo
$ ls -1s foo:bar
2009/11/15 Steven Monai:
> In 1.7.0-64, /usr/sbin/cygserver is linked against cygstdc++-6.dll.
> cygserver will not run (exit status 128) unless the 'libstdc++6' package
> is installed.
Yep. Known issue.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http:/
And in case anyone is interested, here is a bash function that launches a
command via 'at' at the next minute and returns the number of seconds until
the launch (actually if you are less than 5 seconds before the next minute,
it waits until the minute after so that at has time to setup - you could
2009/11/15 Martin Dorey:
> Linking a C program using 1.7.0-63 or 1.7.0-64 causes this runtime error when
> attempting to run the program on Cygwin 1.5:
>
> "The procedure entry point cygwin_create_path could not be located in the
> dynamic link library cygwin1.dll".
>
> This happens with gcc-3 or
For a while, I have been using the "trick" of executing scripts via 'at' when
logged in over ssh to get around the limitations of USRNAME=SYSTEM. This is
necessary for running things like vshadow, dosdev, and apparently subinacl.
While I have written a short script that figures out the nearest mi
Linking a C program using 1.7.0-63 or 1.7.0-64 causes this runtime error when
attempting to run the program on Cygwin 1.5:
"The procedure entry point cygwin_create_path could not be located in the
dynamic link library cygwin1.dll".
This happens with gcc-3 or gcc-4 - it's the Cygwin version that
In 1.7.0-64, /usr/sbin/cygserver is linked against cygstdc++-6.dll.
cygserver will not run (exit status 128) unless the 'libstdc++6' package
is installed.
-SM
--
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://
I find /proc/registry is a nice shortcut for reading registry entries rather
than having to use regtool/reg/regedit etc.
It would be nice though if there were links for the commonly accepted
shortcuts as used for example by regtool.
Any reason not to add them within /proc/registry itself (of cou
Jason DePriest wrote:
> Does 'ls -n' show the UIDs under both users?
ls -n shows uid=gid=4294967295 which I believe is UINT_MAX (2^32-1), so this
is just -1.
Maybe what's happening is that cygwin is returning an error (-1) here?
BTW I'm running cygwin 1.7
--
View this message in context:
http
19 matches
Mail list logo
