Re: 1.7] Can you have multipe cygdrive path prefixes active at once

2009-11-07 Thread Larry Hall (Cygwin)
On 11/06/2009 06:16 PM, Jeremy Bopp wrote: Larry Hall (Cygwin) wrote: On 11/06/2009 05:35 PM, Jeremy Bopp wrote: Thrall, Bryan wrote: Jeremy Bopp wrote on Friday, November 06, 2009 3:31 PM: Well, it's a bit of a hack, but you could try something like the following: $ dirname $(cygpath -u C:

Re: [1.7] Undocumented change in accessing by dos drive letters?

2009-11-07 Thread Dave Korn
Eric Blake wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > According to aputerguy on 11/5/2009 2:34 PM: >> >From the cygwin shell, I can do tab-completion on drive letters to get >> things like C:/usr/bin/ls >> However, when I press return, I get: >> bash: C:/usr/bin/ls: No such

Re: Why do 'find' and 'ls' act differently on ACLs

2009-11-07 Thread Steven Monai
aputerguy wrote: > Why do 'ls and 'find' seem to treat the ACL restrictions differently. They definitely should not. If they do, then there's a bug to be squashed. > Specifically, 'ls /c/Documents and Settings/Administrators' works > while 'find /c/Documents and Settings/Administrators' returns:

Re: 1.7] Can you have multipe cygdrive path prefixes active at once

2009-11-07 Thread Lee D. Rothstein
Bopp wrote: > aputerguy wrote: >> Jeremy Bopp writes: >>> Well, it's a bit of a hack, but you could try something like the >>> following: >>> $ dirname $(cygpath -u C:/) >>> This assumes that there is always a C: drive and converts the path to >>> the root of that drive into a POSIX path which

Why do 'find' and 'ls' act differently on ACLs

2009-11-07 Thread aputerguy
As a newbie to Windoze/ACL security, I am probably missing something. But... Why do 'ls and 'find' seem to treat the ACL restrictions differently. Specifically, 'ls /c/Documents and Settings/Administrators' works while 'find /c/Documents and Settings/Administrators' returns: find: `/c/Document

Re: setup-1.7.exe replace on boot. Was it deprecated?

2009-11-07 Thread Shaddy Baddah
Hi again, Shaddy Baddah wrote: Actually you are if you look at your command line again. Try this version of it. /cygdrive/d/Temp/setup-1.7 -L /cygdrive/c/cygwin-1.7 -l /cygdrive/d/cygwin-1.7-downloads -P rsync -q Note the lacking -r in this version. Ouch. How very embarrassing. That's wha

Re: 1.7] Can you have multipe cygdrive path prefixes active at once

2009-11-07 Thread Jeremy Bopp
aputerguy wrote: > Jeremy Bopp writes: >> Well, it's a bit of a hack, but you could try something like the >> following: >> >> $ dirname $(cygpath -u C:/) > >> This assumes that there is always a C: drive and converts the path to >> the root of that drive into a POSIX path which will include the c

Re: setup-1.7.exe replace on boot. Was it deprecated?

2009-11-07 Thread Shaddy Baddah
Hi, Robert Pendell wrote: On Sat, Nov 7, 2009 at 8:47 AM, Shaddy Baddah wrote: /cygdrive/d/Temp/setup-1.7 -L -r /cygdrive/c/cygwin-1.7 -l /cygdrive/d/cygwin-1.7-downloads -P rsync -q replace on boot can be turned "off", if I had specified -r, which I hadn't. That suggests that it is

Re: 1.7] BUG - GREP slows to a crawl with large number of matches on a single file

2009-11-07 Thread aputerguy
Changing LC_ALL also solved the problem for me. But it begs the question of how many other basic and take-for-granted functions might be affected by this apparent UTF-8 slowdown. And again we, are not talking about some minor overhead, we are talking about a slowdown of 1500X or 150,000% As a

Re: 1.7] Can you have multipe cygdrive path prefixes active at once

2009-11-07 Thread aputerguy
Jeremy Bopp writes: > Well, it's a bit of a hack, but you could try something like the > following: > > $ dirname $(cygpath -u C:/) > This assumes that there is always a C: drive and converts the path to > the root of that drive into a POSIX path which will include the cygdrive > prefix. Then d

Re: 1.7] Can you have multipe cygdrive path prefixes active at once

2009-11-07 Thread aputerguy
Jeremy Bopp writes: > The concern posed by the instigator of this thread is that it can't be > known from the output of "mount -p" whether or not the spaces which > follow the listed cygdrive prefix are part of the prefix or padding for > the outputted columns. It should be pretty rare that some

Re: setup-1.7.exe replace on boot. Was it deprecated?

2009-11-07 Thread Robert Pendell
On Sat, Nov 7, 2009 at 8:47 AM, Shaddy Baddah wrote: > Hi, > > I was wondering if the replace on boot feature in setup was deprecated > with setup-1.7.exe? I am trying to do an install via the following > command-line: > > /cygdrive/d/Temp/setup-1.7 -L -r /cygdrive/c/cygwin-1.7 -l > /cygdrive/d/cyg

Re: 1.7] BUG - GREP slows to a crawl with large number of matches on a single file

2009-11-07 Thread Richard Foulk
Jim Reisert wrote: >On Fri, Nov 6, 2009 at 7:12 AM, Cooper, Karl (US SSA) > wrote: > >> Corinna Vinschen wrote: >>> Or try LANG=C.ASCII since LANG=C will still return UTF-8 as charset >>> when calling nl_langinfo(CHARSET). >> >> Yes, this solves it: >> >> $ time LC_ALL=C.ASCII grep dog testfile |

Re: [1.7] Updated: cygwin-1.7.0-63

2009-11-07 Thread Eric Backus
Jim Reisert AD1C alum.mit.edu> writes: > Thanks, Eric. I tried this but could not get what I wanted: > > LTDENA-REISERT:c/Home> ls -al --time-style="posix-long-iso" > > -rwx-- 1 reisertDomain Users3326 2009-10-30 12:51 .XWinrc > -rwx-- 1 reisertUsers66

Re: Problem with rsync 3.0.6-1 under 1.7.0-62 and 63

2009-11-07 Thread Steven Monai
Eliot Moss wrote: >> Eliot Moss wrote: >>> I am getting this output when trying to rsync >>> to any of several systems. I have RSYNC_RSH set >>> to use ssh, and the ssh commands work just fine. >>> This smells like some kind of non-matching library >>> issue to me ... >>> >>> rsync: Failed to dup/c

Re: Re: Problem with rsync 3.0.6-1 under 1.7.0-62 and 63

2009-11-07 Thread Eliot Moss
Steven Monai wrote: Eliot Moss wrote: I am getting this output when trying to rsync to any of several systems. I have RSYNC_RSH set to use ssh, and the ssh commands work just fine. This smells like some kind of non-matching library issue to me ... rsync: Failed to dup/close: Bad file descriptor

Re: Problem with rsync 3.0.6-1 under 1.7.0-62 and 63

2009-11-07 Thread Steven Monai
Eliot Moss wrote: > I am getting this output when trying to rsync > to any of several systems. I have RSYNC_RSH set > to use ssh, and the ssh commands work just fine. > This smells like some kind of non-matching library > issue to me ... > > rsync: Failed to dup/close: Bad file descriptor (9) > rs

Problem with rsync 3.0.6-1 under 1.7.0-62 and 63

2009-11-07 Thread Eliot Moss
I am getting this output when trying to rsync to any of several systems. I have RSYNC_RSH set to use ssh, and the ssh commands work just fine. This smells like some kind of non-matching library issue to me ... rsync: Failed to dup/close: Bad file descriptor (9) rsync error: error in IPC code (cod

[ANNOUNCEMENT] Updated: mintty-0.5.3-1

2009-11-07 Thread Andy Koppe
Mintty is a terminal emulator for Cygwin with a native Windows user interface and minimalist design. Among its features are Unicode support and a graphical options dialog. Its terminal emulation is largely compatible with xterm, but it does not require an X server. Mintty is based on code from PuTT

cygwin 1.7.0-63 problems with X programs

2009-11-07 Thread Eliot Moss
Like another user, I had difficulty getting X to fire up. After setting LANG=en_US.UTF-8 I got farther, but these issues remain: Each xterm, xemacs, and xclock I start outputs this: Warning: Missing charsets in String to FontSet conversion I also get a series of: twm: warning: font for charset

setup-1.7.exe replace on boot. Was it deprecated?

2009-11-07 Thread Shaddy Baddah
Hi, I was wondering if the replace on boot feature in setup was deprecated with setup-1.7.exe? I am trying to do an install via the following command-line: /cygdrive/d/Temp/setup-1.7 -L -r /cygdrive/c/cygwin-1.7 -l /cygdrive/d/cygwin-1.7-downloads -P rsync -q as an Administrator user on Windows

Re: 1.7: missing 'rand' command

2009-11-07 Thread Mark J. Reed
On Sat, Nov 7, 2009 at 12:27 AM, Lee D. Rothstein wrote: > My bad. Thanks. Sorry. How silly of me to expect a rand(1) page to be for a > rand command. This is something of a quirk of the openssl doc, useful because you can in fact set up the openssl subcommands as standalone UNIX shell commands -