I've come across this issue also after installing latest Cygwin. Don't
know how to fix it.
在 2012年4月26日 上午2:13，marco atzeri 写道：
> On 4/25/2012 7:32 PM, Garrison, Jim (ETW) wrote:
>>
>> New install of Cygwin on Win7X64, ssh client is insisting on putting its
>> files in /.ssh instead of ~/.ssh
>>
I've just updated the shutdown package to 1.8-1.
This is a copyright update in the first place, from GPLv2+ to GPLv3+.
All Windows 9x and NT4 considerations have been removed from the code.
I also changed the packaging method to cygport.
To update your installation, click on the "Install Cygwin
In the latest cygwin package fetchmail 6.3.18-1 has been compiled with old
openssl 0.9.8 library.
This causes errors in ssl certificate validation when connecting to imap or
pop3 with ssl.
The problem is openssl 1.0.0 and later has different hash generation algorithm
then previous 0.9.8 version.
I've just updated the Cygwin version of tin to 2.0.1-1.
This is a new upstream release. For a list of changes see
ftp://ftp.tin.org/pub/news/clients/tin/v2.0/CHANGES
I also changed the packaging method to cygport.
To update your installation, click on the "Install Cygwin now" link on
the http:
I've updated the tcsh package to 6.18.01-1.
This is an upstream version update. The Cygwin version is build from
the 6.18.01 sources. I also changed the packaging method to cygport.
To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page. This do
On 4/25/2012 7:32 PM, Garrison, Jim (ETW) wrote:
New install of Cygwin on Win7X64, ssh client is insisting on putting its files
in /.ssh instead of ~/.ssh
$HOME is correctly set, and "echo ~" displays the correct home directory.
Where else should I be looking for a variable or setting that wou
I've updated the cygrunsrv package to 1.40-2.
No changes, just an update to the cygport packaging method.
To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page. This downloads setup.exe to your
system. Then, run setup and answer all of the quest
On Wed, Apr 25, 2012 at 03:19:26PM +0100, alanhowells.e4ward.com wrote:
>> Please don't http://cygwin.com/acronyms/#TOFU
>My apologies
>
>I know my test code wasn't robust, I just wanted to get something
>going to prove any issues. Anyway, I still have the issue when using
>std::cin. Let me start a
From man xargs:
BUGS
The -L option is incompatible with the -I option, but perhaps should
not be.
Thanks, Barry! Clearly I (we) should have RT(F)M! E
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
ProcessMonitor will let you see calls to the WindowsIO subsystems, and
might help you identify the problem.
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
Disclaimer: http://www.peralex.com/disclaimer.html
--
Problem reports: http://cygwin.com/problems.html
FAQ:
Hi Doug,
I came across this message string while searching for some errors I received
trying to compile LEDAPS on cygwin. I was very excited to see someone else
was doing the same thing! I was wondering if you were successful and if you
could let me know how you did it.
Your help is much appreciat
On 4/25/2012 6:29 AM, Ronald Fischer wrote:
>Eliot Moss sent the following at Wednesday, April 25, 2012 7:05 AM
>
>> Why do I get a different output in the following two invocations of
>> xargs? I had expected that the relative order of the command line
>> switches (-I, -L) would not matter:
>>
>>
Eliot Moss wrote:
> On 4/25/2012 6:29 AM, Ronald Fischer wrote:
> > Why do I get a different output in the following two invocations of
> > xargs? I had expected that the relative order of the command line
> > switches (-I, -L) would not matter:
> >
> > $ ls | xargs -I DIR -L 1 echo DIR
> > DIR won
On 4/25/2012 6:29 AM, Ronald Fischer wrote:
Why do I get a different output in the following two invocations of
xargs? I had expected that the relative order of the command line
switches (-I, -L) would not matter:
$ ls | xargs -I DIR -L 1 echo DIR
DIR wontprint.txt
DIR x.cmd
DIR x.pl
DIR x.sh
$
On Apr 25 12:38, Fedin Pavel wrote:
> On 25.04.2012 12:01, Corinna Vinschen wrote:
> >Think of the SFU POSIX layer, formerly called Interix.
> Is it still maintained by MS?I thought it has been dropped long time ago.
It's still available in W8, albeit marked as deprecated.
Corinna
--
Corinna
Why do I get a different output in the following two invocations of
xargs? I had expected that the relative order of the command line
switches (-I, -L) would not matter:
$ ls | xargs -I DIR -L 1 echo DIR
DIR wontprint.txt
DIR x.cmd
DIR x.pl
DIR x.sh
$ ls | xargs -L 1 -I DIR echo DIR
wontprint.txt
On 25.04.2012 12:01, Corinna Vinschen wrote:
Think of the SFU POSIX layer, formerly called Interix.
Is it still maintained by MS?I thought it has been dropped long time ago.
--
Kind regards
Pavel Fedin
Expert engineer, Samsung Moscow research center
--
Problem reports: http://cygwin
Hi Cygwin friends and users,
I just released 1.7.14-2. The code for the new mouse reporting modes in
1.7.14-1 was accidentally based on a wrong patch submission. That has
been fixed in this release. Nothing else has changed, therefore I
didn't raise the Cygwin version number.
Have fun,
Corin
On Apr 25 11:46, Fedin Pavel wrote:
> On 25.04.2012 11:14, Corinna Vinschen wrote:
> >Cygwin understands NFS symlinks just fine, and when it creates symlinks
> >on NFS, these are *real* symlinks, not Cygwin-type fake symlinks. When
> >it recognizes SFU NFS shares, it uses special functionality pro
On 25.04.2012 11:14, Corinna Vinschen wrote:
Cygwin understands NFS symlinks just fine, and when it creates symlinks
on NFS, these are *real* symlinks, not Cygwin-type fake symlinks. When
it recognizes SFU NFS shares, it uses special functionality provided by
the SFU NFS driver to read and creat
On Apr 25 09:39, Fedin Pavel wrote:
> On 24.04.2012 18:11, Corinna Vinschen wrote:
>
> >An NFS client is a filesystem driver. There are companies
> >providing such NFS clients, one of them Microsoft with SFU on
> >pre-Vista and the NFS client in Vista/W7 Ultimate/Enterprise.
> >Corinna
>
> BTW,
21 matches
Mail list logo
