Re: Ping crashes

On Oct 29 23:59, Andrey Repin wrote: > Greetings, Corinna Vinschen! > > > I just pushed a patch supposed to fix this issue. The bug is actually > > worse and potentially affects more than just ping. Every time a socket, > > socketpair, or accept call fails for some rea

Re: Ping crashes

On Oct 29 17:39, Houder wrote: > On Mon, 29 Oct 2018 16:40:43, Corinna Vinschen wrote: > > > > On Oct 27 15:25, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote: > > > Hello, > > > > > > I have a problem with the ping utility on Cygwin: it keeps cra

Re: Ping crashes

Greetings, Corinna Vinschen! > I just pushed a patch supposed to fix this issue. The bug is actually > worse and potentially affects more than just ping. Every time a socket, > socketpair, or accept call fails for some reason, there's a potential > SEGV. Oh, boy, oh boy.

Re: Ping crashes

On Mon, 29 Oct 2018 16:40:43, Corinna Vinschen wrote: > > On Oct 27 15:25, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote: > > Hello, > > > > I have a problem with the ping utility on Cygwin: it keeps crashing with = > segmentation fault. I've checked

Re: Ping crashes

On Oct 27 15:25, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote: > Hello, > > I have a problem with the ping utility on Cygwin: it keeps crashing with > segmentation fault. I've checked that all my packages (including Cygwin core) > are up to date. What am I miss

Re: Ping crashes

Hello, Anton. I'm a maintainer of ping package. Thank you for your report. Ping requires administrator privilege in windows OSs older than Windows 10 build 14926. In such OSs, ping should result in error: 'ping: Lacking privilege for raw socket.' However, with cygwin 2.11.0 or

Re: Ping crashes

On Sat, 27 Oct 2018 15:25:50, X wrote: > Hello, > > I have a problem with the ping utility on Cygwin: it keeps crashing with se= > gmentation fault. I've checked that all my packages (including Cygwin core) [snip] > $ ping 192.168.1.1 > Segmentation fault (core dumpe

Re: Ping crashes

On Sat, 27 Oct 2018 15:25:50, X wrote: > Hello, > > I have a problem with the ping utility on Cygwin: it keeps crashing with se= > gmentation fault. I've checked that all my packages (including Cygwin core) [snip] > $ ping 192.168.1.1 > Segmentation fault (core dump

Ping crashes

Hello, I have a problem with the ping utility on Cygwin: it keeps crashing with segmentation fault. I've checked that all my packages (including Cygwin core) are up to date. What am I missing? At any rate, I guess it should not have crashed ungracefully if it needs something it doesn&#

[ANNOUNCEMENT] Updated: httping 2.4+20151029+gitb1521a6-1 -- Ping-like program for http-requests

PACKAGE DESCRIPTION === Homepage: http://freshmeat.net/projects/httping License : AGPL-3+ Show how long it takes to connect to a hostname or remote url; send a request and retrieve the reply (only the headers). CHANGES SINCE LAST RELEASE == See homepage

Re: Is ping only supposed to work for admin accounts?

Yes. Ping needs admin rights in all operating systems, but they have various ways to allow access, such as running suid in unix or using a special API call on Windows. If you need ping from cygwin, it's best to rely on the Windows version without installing the cygwin one. ~ Brian On Sun

Is ping only supposed to work for admin accounts?

I just used the cygwin installer to install ping-1.0.2-1.tar.xz but it doesn't work for limited user accounts: $ ping google.com ping: socket: Operation not permitted 149 29930 [main] ping 11668 dup_ent: duping protoent "icmp", 0xD56580 46 29976 [main] ping 11668 dup_ent

Re: ctrl-c doesn't reliably kill ping

On 3/15/2016 7:43 AM, Adam Dinwoodie wrote: > On Tue, Mar 15, 2016 at 02:00:38PM +0300, Andrey Repin wrote: >> Greetings, Frank Farance! >> >>> A little digression, so you understand the background ... The workstation I >>> am >>> doing this from is connected to a Verizon router to their FIOS netw

Re: ctrl-c doesn't reliably kill ping

On 15/03/2016 01:45, Frank Farance wrote: I have been having this problem with "ping". If I "ping" a location that doesn't exist, then "ping" just hangs and cannot be killed via "kill -KILL [pid]". Back to the problem, so when I type $

Re: ctrl-c doesn't reliably kill ping

On 16.03.2016 08:57, Michael Enright wrote: On Wed, Mar 16, 2016 at 7:51 AM, cyg Simple wrote: My ISP for my connection to the WWW is the one that is doing the inappropriate redirects. I sometime get these even when using VPN to my employer's intranet. My ISP also provides phone and TV Cabl

Re: ctrl-c doesn't reliably kill ping

Hi, On 3/14/16, Frank Farance wrote: > I have been having this problem with "ping". If I "ping" a location that > doesn't exist, then "ping" just hangs and cannot be killed via "kill -KILL > [pid]". > > A little digression, so you under

Re: ctrl-c doesn't reliably kill ping

On 17/03/2016 22:10, Frank Farance wrote: Folks- Anyway, as we'd say in standardizing the C programming language, this behavior is a "surprise" ... and we should look to eliminate "surprises". Again, thank you in advance for your help. -FF as mentioned on: https://cygwin.com/ml/cygwin/

Re: ctrl-c doesn't reliably kill ping

On Wed, Mar 16, 2016 at 7:51 AM, cyg Simple wrote: > > My ISP for my connection to the WWW is the one that is doing the > inappropriate redirects. I sometime get these even when using VPN to my > employer's intranet. My ISP also provides phone and TV Cable and I'm > guessing that the accepted pra

Re: ctrl-c doesn't reliably kill ping

Folks- Thank you for the thoughtful observations, responses, and suggestions, which I will summarize: - Suggestion #1: Try different DNS settings not using Verizon. - Suggestion #2: Try different Verizon configuration. - Suggestion #3: Try Windows version of ping. - Observation #4: This

Re: ctrl-c doesn't reliably kill ping

> If I weren't happy with upstream DNS, I'd go into the router's > configuration and tell dnsmasq to send its queries to some alternative > DNS. Instructions for Verizon customers to opt out of "DNS Assistance" are here: https://www.verizon.com/support/consumer/internet/opt-out-of-dns-assist Le

Re: ctrl-c doesn't reliably kill ping

On 3/16/2016 12:56 AM, Kaz Kylheku wrote: > On 15.03.2016 04:00, Andrey Repin wrote: >> Greetings, Frank Farance! >>> So all of this is normal ISP stuff: they actually resolve unknown >>> addresses to >>> their own website (which is 90.242.140.21). >> >> This is NOT "normal", this is a violation of

Re: ctrl-c doesn't reliably kill ping

On Mar 16, 2016, at 10:07 AM, Lee wrote: > > The last time I tried the cygwin ping program it didn't return a > failure status It does if you don’t Ctrl-C out of it. So, if you’re using it from a script, you just ask for one packet: # ping does.not.exist 1 1 ping

Re: ctrl-c doesn't reliably kill ping

Greetings, Kaz Kylheku! > On 15.03.2016 04:00, Andrey Repin wrote: >> Greetings, Frank Farance! >>> So all of this is normal ISP stuff: they actually resolve unknown >>> addresses to >>> their own website (which is 90.242.140.21). >> >> This is NOT "normal", this is a violation of protocol. >> W

Re: ctrl-c doesn't reliably kill ping

On 3/16/16, Warren Young wrote: > On Mar 16, 2016, at 10:07 AM, Lee wrote: >> >> The last time I tried the cygwin ping program it didn't return a >> failure status > > It does if you don’t Ctrl-C out of it. So, if you’re using it from a > script, you just

Re: ctrl-c doesn't reliably kill ping

On 15.03.2016 04:00, Andrey Repin wrote: Greetings, Frank Farance! So all of this is normal ISP stuff: they actually resolve unknown addresses to their own website (which is 90.242.140.21). This is NOT "normal", this is a violation of protocol. Whoever encounter such behavior should call thei

Re: ctrl-c doesn't reliably kill ping

On Mar 14, 2016, at 6:45 PM, Frank Farance wrote: > > I have been having this problem with "ping". If I "ping" a location that > doesn't exist, then "ping" just hangs and cannot be killed via "kill -KILL > [pid]”. Are you certain that you’

Re: ctrl-c doesn't reliably kill ping

On Tue, Mar 15, 2016 at 02:00:38PM +0300, Andrey Repin wrote: > Greetings, Frank Farance! > > > A little digression, so you understand the background ... The workstation I > > am > > doing this from is connected to a Verizon router to their FIOS network. > > Now the > > reason I mention this is

Re: ctrl-c doesn't reliably kill ping

Greetings, Frank Farance! > A little digression, so you understand the background ... The workstation I am > doing this from is connected to a Verizon router to their FIOS network. Now > the > reason I mention this is that the router's DNS (via DHCP to my workstation) is > 192.168.1.1, which I p

ctrl-c doesn't reliably kill ping

I have been having this problem with "ping". If I "ping" a location that doesn't exist, then "ping" just hangs and cannot be killed via "kill -KILL [pid]". A little digression, so you understand the background ... The workstation I am doing this f

[ANNOUNCEMENT] Updated: httping 2.4+20150928+git5f905fc-1 -- Ping-like program for http-requests

PACKAGE DESCRIPTION === Homepage: http://freshmeat.net/projects/httping License : AGPL-3+ Show how long it takes to connect to a hostname or remote url; send a request and retrieve the reply (only the headers). CHANGES SINCE LAST RELEASE == See homepage

Re: Cygwin's ping requires privilege elevation.

gping.) I understand, that some of the ping functionality, indeed, require raw device access, but if it is possible to avoid elevated calls for basic functions, that would be highly appreciated. Yes, it is a know limitation of raw socket https://cygwin.com/ml/cygwin/2009-12/msg00164.html

Cygwin's ping requires privilege elevation.

Greetings, All! I had this issue running for some time, but recently I've (with a little help from my friends) stumbled upon another Cygwin rip-off, and the hack they implemented to get around this issue. (Yes, they just renamed the ping.exe to cygping.) I understand, that some of the

Re: fish PATH problem [ping Konrad]

> So I just re-tested starting a fish login shell after updating cygwin64. > As I suspected, fish has not been updated since the thread I quoted (Apr > 2014), and the issue remains (with my install). Google doesn't show the > maintainer on list since the announcement (Oct 2013), and his e-mail

[ANNOUNCEMENT] Updated: ping-1.0.2-1

New versions 1.0.2-1 of ping are available in the Cygwin distribution (32 and 64 bit) : CHANGES - First release for cygwin 64 bit. Minimal source change to remove all build warning with latest gcc-4.8 (additional header and some casts) - No functional change for 32 bit, just same

ping stalls sometimes

Hi Cygwin people, I run Cygwin on Windows 7 ultimate. Pinging on the command prompt, on rxvt, or on mitty sometimes makes ping stall. That is, even if I press ctrl-C, ping does not exit. This happens sporadically. It happens everyday but not all day. Here's the ping version: $ cygche

Re: INETUTILS and PING package missing from 64-bit Setup 2.830

On 10/23/2013 3:20 PM, Charles Butterfield wrote: Also noticed that "inetutils" package is missing from 64-bit. Also noticed that "ping" package is missing from 64-bit. Gosh - I use both of these on occasion. I'm now feeling I may have made a mistake in upgrading to

INETUTILS and PING package missing from 64-bit Setup 2.830

Also noticed that "inetutils" package is missing from 64-bit. Also noticed that "ping" package is missing from 64-bit. Gosh - I use both of these on occasion.  I'm now feeling I may have made a mistake in upgrading to 64-bit. My questions: 1)  Is there some way to i

[ANNOUNCEMENT] Updated: httping 1.6-1 -- Ping-like program for http-requests

PACKAGE DESCRIPTION === Homepage: http://freshmeat.net/projects/httping License : GPL-2 Show how long it takes to connect to a hostname or remote url; send a request and retrieve the reply (only the headers). CHANGES SINCE LAST RELEASE == See homepage fo

Re: Conflated ping issues

On 03/01/2013 18:07, David McAllister wrote: Hi. I have three machines that all run Win 7 x64 and all have updated Cygwin installs. I thought I installed them all the same, but I'm getting two differences, both centered around the ping command. Machine 1 doesn't have /usr/bin/ping.

[ANNOUNCEMENT] Updated: httping 1.5.4-1 -- Ping-like program for http-requests

PACKAGE DESCRIPTION === Homepage: http://freshmeat.net/projects/httping License : GPL Show how long it takes to connect to a hostname or remote url; send a request and retrieve the reply (only the headers). CHANGES SINCE LAST RELEASE == See homepage for

[ANNOUNCEMENT] Updated: httping 1.5.2-1 -- Ping-like program for http-requests

PACKAGE DESCRIPTION === Homepage: http://freshmeat.net/projects/httping License : GPL Show how long it takes to connect to a hostname or remote url; send a request and retrieve the reply (only the headers). CHANGES SINCE LAST RELEASE == See homepage and

[ANNOUNCEMENT] Updated: httping 1.4.4-2 -- Ping-like program for http-requests

PACKAGE DESCRIPTION === Homepage: http://freshmeat.net/projects/httping License : GPL Show how long it takes to connect to a hostname or remote url; send a request and retrieve the reply (only the headers). CHANGES SINCE LAST RELEASE == - Cygwin: remove

Re: mintty/ping issue

On Apr 1 13:20, Nellis, Kenneth wrote: > From: Nellis, Kenneth > > Running Cygwin 1.7.9, bash 4.1.10, the Windows ping command works > > fine from the Command Prompt window, but not from mintty, where > > it writes the IP address octets as binary, appearing as garbage: &g

RE: mintty/ping issue

From: Nellis, Kenneth > Running Cygwin 1.7.9, bash 4.1.10, the Windows ping command works > fine from the Command Prompt window, but not from mintty, where > it writes the IP address octets as binary, appearing as garbage: Actually, I can eliminate mintty's involvement, as I see th

mintty/ping issue

Running Cygwin 1.7.9, bash 4.1.10, the Windows ping command works fine from the Command Prompt window, but not from mintty, where it writes the IP address octets as binary, appearing as garbage: From Command Prompt (works fine): C:\>ping 127.1.1.1 Pinging 127.1.1.1 with 32 bytes of d

[ANNOUNCEMENT] Updated: httping 1.4.4-1 -- Ping-like program for http-requests

PACKAGE DESCRIPTION === Homepage: http://www.vanheusden.com/httping License : GPL Show how long it takes to connect to a hostname or remote url; send a request and retrieve the reply (only the headers). CHANGES SINCE LAST RELEASE == See homepage and sect

List Ping

-- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple

Re: lighttpd, nano, tidy: update (ping?)

On 25 August 2010 10:50, Yaakov (Cygwin/X) wrote: > Lapo, > > Ping on updates for lighttpd, nano and tidy? > > http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/ports;a=tree;f=apps/nano Yeah, an update for nano would be really nice. Is the 2.2.4-wchar.patch stil

lighttpd, nano, tidy: update (ping?)

Lapo, Ping on updates for lighttpd, nano and tidy? http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/ports;a=tree;f=apps/nano http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/ports;a=tree;f=libs/tidy http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi

[ANNOUNCEMENT] Updated: httping 1.4.1-1 -- Ping-like program for http-requests

PACKAGE DESCRIPTION === Homepage: http://www.vanheusden.com/httping License : GPL Show how long it takes to connect to a hostname or remote url; send a request and retrieve the reply (only the headers). CHANGES SINCE LAST RELEASE == See homepage and sect

Re: ping "Operation not permitted" on Windows 7

On 6/25/2010 3:07 AM, David Arnstein wrote: Using Windows 7 Professional, cygwin, mintty,and bash. All are up to date. I am getting this: $ type ping ping is hashed (/usr/bin/ping) $ ping www.microsoft.com ping: socket: Operation not permitted If I launch mintty "R

Re: ping "Operation not permitted" on Windows 7

> From: David Arnstein > To: cygwin@cygwin.com > Date: Fri, 25 Jun 2010 03:07:54 -0400 > Subject: ping "Operation not permitted" on Windows 7 > Using Windows 7 Professional, cygwin, mintty,and bash. All are up to date. > I am getting this: >$ type ping >

Re: operation not permitted when attempting to ping

On Dec 3 21:08, Robert Pendell wrote: > On Thu, Dec 3, 2009 at 7:54 PM, Larry Hall (Cygwin) wrote: > > On 12/03/2009 07:35 PM, Robert Pendell wrote: > >> > >> Whenever I use ping it returns the message socket: Operation not > >> permitted.  This only happens

Re: operation not permitted when attempting to ping

On Thu, Dec 3, 2009 at 7:54 PM, Larry Hall (Cygwin) wrote: > On 12/03/2009 07:35 PM, Robert Pendell wrote: >> >> Whenever I use ping it returns the message socket: Operation not >> permitted.  This only happens if I am not running the shell as an >> administrator oth

Re: operation not permitted when attempting to ping

On 12/03/2009 07:35 PM, Robert Pendell wrote: Whenever I use ping it returns the message socket: Operation not permitted. This only happens if I am not running the shell as an administrator otherwise it works fine.. The windows stock ping command doesn't need admin rights to run. I am ru

operation not permitted when attempting to ping

Whenever I use ping it returns the message socket: Operation not permitted. This only happens if I am not running the shell as an administrator otherwise it works fine.. The windows stock ping command doesn't need admin rights to run. I am running Windows 7 and cygwin 1.7. Attached

Re: Puppet in Cygwin [ping Reini]

n this? There's a still-small wiki page about Puppet in Cygwin at http://reductivelabs.com/trac/puppet/wiki/PuppetCygwin. If you are interested, please start contributing there. [Ping Reini] I guess you are referring to my question on the wiki: "via ruby's windows port you can ha

Re: Puppet in Cygwin [ping Reini]

> Shouldn't there have been an explanation of what Puppet is and why it is > useful somewhere above? Okay. Puppet is configuration management software. It allows a LAN administrator to specify sets of files, sofware packages, services, cron jobs, and so on, and the relationships between them, an

Re: Puppet in Cygwin [ping Reini]

On 11/27/2009 07:51 PM, Christopher Faylor wrote: Shouldn't there have been an explanation of what Puppet is and why it is useful somewhere above? http://lmgtfy.com/?q=puppet&l=1 -- Andrew DeFaria Someone who thinks logically is a nice contrast to the real world. -- Proble

Re: Puppet in Cygwin [ping Reini]

On Fri, Nov 27, 2009 at 02:15:05PM -0500, Andrew Schulman wrote: >It would be great to port Puppet to Cygwin. > >Puppet's scope on a Cygwin host is going to be more limited than on Linux, >just because Cygwin's scope is limited. Puppet could easily manage >Cygwin's file and services, but managin

Puppet in Cygwin [ping Reini]

It would be great to port Puppet to Cygwin. Puppet's scope on a Cygwin host is going to be more limited than on Linux, just because Cygwin's scope is limited. Puppet could easily manage Cygwin's file and services, but managing Windows files and services would take more work because the environm

Re: [1.7] ping: socket: Operation not permitted

e is the cygcheck. >> >> >> >> I use Vista Ultimate, 32 bits. >> > >> > The previous thread that you refer to applies here unless you're running >> > your shell with elevated permissions (and your user is part of the >> > administrator

Re: [1.7] ping: socket: Operation not permitted

evious thread that you refer to applies here unless you're running > > your shell with elevated permissions (and your user is part of the > > administrator group).  As noted, this only applies to Cygwin's ping.  The > > Windows ping (the one which you showed working) do

Re: [1.7] ping: socket: Operation not permitted

vated permissions (and your user is part of the > administrator group).  As noted, this only applies to Cygwin's ping.  The > Windows ping (the one which you showed working) does not have this > restriction. > I see... here's what I don't understand: I have been using cygwin for years

Re: [1.7] ping: socket: Operation not permitted

d your user is part of the administrator group). As noted, this only applies to Cygwin's ping. The Windows ping (the one which you showed working) does not have this restriction. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9

Re: [1.7] ping: socket: Operation not permitted

On 09/25/2009 09:10 AM, Gustavo Seabra wrote: Hi, I have just installed a brand new cygwin installation. When I try to ping anything from cygwin, I get the message above: $ ping 150.161.5.10 ping: socket: Operation not permitted If I try exactly the ssame from the command shell, it works

[1.7] ping: socket: Operation not permitted

Hi, I have just installed a brand new cygwin installation. When I try to ping anything from cygwin, I get the message above: $ ping 150.161.5.10 ping: socket: Operation not permitted If I try exactly the ssame from the command shell, it works: C:\>ping 150.161.5.10 Pinging 150.161.5.10 w

Re: PING: Deprecation of -mno-cygwin.

Eric Backus wrote: > Christopher Faylor cygwin.com> writes: >>> which would put all the confusion to rest. >> Big DITTO. As Dave said, the option is already gone... > > Moving to a better solution is great! But isn't it customary to have some > overlap period where the deprecated solution sti

Re: PING: Deprecation of -mno-cygwin.

Christopher Faylor cygwin.com> writes: > On Mon, Mar 23, 2009 at 02:22:03PM +, Greg Chicares wrote: > >On 2009-03-23 14:00Z, Steve Thompson wrote: > >> On Mon, 23 Mar 2009, Dave Korn wrote: > >> > >>> It's a bit of a kludge compared to having a real honest-to-god > >>> cross-compiler. It's

Re: PING: Deprecation of -mno-cygwin.

Steve Thompson wrote: > On Mon, 23 Mar 2009, Dave Korn wrote: > >> It's a bit of a kludge compared to having a real honest-to-god >> cross-compiler. It's never worked entirely right in terms of keeping >> cygwin and mingw headers and libs completely separate. A full-blown mingw >> cross-compiler

Re: PING: Deprecation of -mno-cygwin.

On Mon, Mar 23, 2009 at 02:22:03PM +, Greg Chicares wrote: >On 2009-03-23 14:00Z, Steve Thompson wrote: >> On Mon, 23 Mar 2009, Dave Korn wrote: >> >>> It's a bit of a kludge compared to having a real honest-to-god >>> cross-compiler. It's never worked entirely right in terms of keeping cygw

Re: PING: Deprecation of -mno-cygwin.

On 2009-03-23 14:00Z, Steve Thompson wrote: > On Mon, 23 Mar 2009, Dave Korn wrote: > >> It's a bit of a kludge compared to having a real honest-to-god >> cross-compiler. It's never worked entirely right in terms of keeping cygwin >> and mingw headers and libs completely separate. A full-blown

Re: PING: Deprecation of -mno-cygwin.

On Mon, 23 Mar 2009, Dave Korn wrote: It's a bit of a kludge compared to having a real honest-to-god cross-compiler. It's never worked entirely right in terms of keeping cygwin and mingw headers and libs completely separate. A full-blown mingw cross-compiler won't cost that much in terms of d

Re: PING: Deprecation of -mno-cygwin.

Steve Thompson wrote: > uOn Mon, 23 Mar 2009, Yaakov (Cygwin/X) wrote: > >> Please, NO! -mno-cygwin needs to go away already. > > Why? > It's a bit of a kludge compared to having a real honest-to-god cross-compiler. It's never worked entirely right in terms of keeping cygwin and mingw heade

Re: PING: Deprecation of -mno-cygwin.

Yaakov (Cygwin/X) wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Corinna Vinschen wrote: >> It might be helpful for a transition period to retain both options. >> >> $ i686-pc-cygwin-gcc -mcygwin <- just works >> $ i686-pc-cygwin-gcc -mno-cygwin <- Spits out a wa

Re: PING: Deprecation of -mno-cygwin.

uOn Mon, 23 Mar 2009, Yaakov (Cygwin/X) wrote: Please, NO! -mno-cygwin needs to go away already. Why? -Steve -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ:

Re: PING: Deprecation of -mno-cygwin.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Corinna Vinschen wrote: > It might be helpful for a transition period to retain both options. > > $ i686-pc-cygwin-gcc -mcygwin <- just works > $ i686-pc-cygwin-gcc -mno-cygwin<- Spits out a warning Please, NO! -mno-cygwin ne

Re: PING: Deprecation of -mno-cygwin.

On Mar 23 00:42, Dave Korn wrote: > > > Ho there gang. Over on gcc-patches, Kai has posted a patch to add some > documentation for the i386 cygming subtarget options. See the thread at: > > http://gcc.gnu.org/ml/gcc-patches/2009-03/threads.html#00994 > > I asked him if he would add a

PING: Deprecation of -mno-cygwin.

Ho there gang. Over on gcc-patches, Kai has posted a patch to add some documentation for the i386 cygming subtarget options. See the thread at: http://gcc.gnu.org/ml/gcc-patches/2009-03/threads.html#00994 I asked him if he would add a note mentioning that -mno-cygwin is deprecated, an

Re: [boost and xerces] ping maintainers

--- Ven 6/3/09, Werner Wothke ha scritto: > Da: Werner Wothke > Oggetto: Re: [boost and xerces] ping maintainers > A: cygwin@cygwin.com > Data: Venerdì 6 marzo 2009, 05:58 > > Larry and Greg, > > Thank you for your responses, I overlooked these libraries, > mostly

Re: [boost and xerces] ping maintainers

Larry and Greg, Thank you for your responses, I overlooked these libraries, mostly because I have not been using them. Your guidance was very educational! Werner Greg Chicares wrote: Can you point out to me where you see any Boost DLLs? I only see *.hpp template files. The boost fil

Re: [boost and xerces] ping maintainers

Werner Wothke wrote: Haclav, I am using Boost's random number generator template library with cygwin for statistical simulations and am very happy with it. It would be a shame to abandon support of the Boost libraries. Can you point out to me where you see any Boost DLLs? I only see *.hpp t

Re: [boost and xerces] ping maintainers

On 2009-03-06 02:30Z, Werner Wothke wrote: > > I am using Boost's random number generator template library with cygwin > for statistical simulations > and am very happy with it. It would be a shame to abandon support of the > Boost libraries. That's one of the many boost libraries that has a he

Re: [boost and xerces] ping maintainers

Haclav, I am using Boost's random number generator template library with cygwin for statistical simulations and am very happy with it. It would be a shame to abandon support of the Boost libraries. Can you point out to me where you see any Boost DLLs? I only see *.hpp template files. Best,

Re: [boost and xerces] ping maintainers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 b...@nc.rr.com wrote: > First, thank-you for supporting these packages in Cygwin. It's > appreciated very much, at least by me. > > From the mailing list archives, it appears the last boost package > (v1.33.1) was rolled in 01/08, and the last xerc

Re: [boost and xerces] ping maintainers

b...@nc.rr.com wrote: > First, thank-you for supporting these packages in Cygwin. It's > appreciated very much, at least by me. > > From the mailing list archives, it appears the last boost package > (v1.33.1) was rolled in 01/08, and the last xerces package (v2.8.0) > in 05/08. Any possibility

[boost and xerces] ping maintainers

First, thank-you for supporting these packages in Cygwin. It's appreciated very much, at least by me. >From the mailing list archives, it appears the last boost package (v1.33.1) >was rolled in 01/08, and the last xerces package (v2.8.0) in 05/08. Any >possibility of updating them to the curr

Re: Bug in ping? ICMP Sequence Number octets are reversed

On Fri, Jun 13, 2008 at 10:10:53AM -0700, Gary Johnson wrote: >> However, I think it's possible to get equivalent behavior >> from Windows ping if you give it the right command line parameters. > >The feature of Cygwin's (Unix's) ping that I found particular

Re: Bug in ping? ICMP Sequence Number octets are reversed

On 2008-06-13, Corinna Vinschen wrote: > On Jun 13 10:07, Christopher Faylor wrote: > > ping does not have a maintainer currently so, unless someone wants to take > > over maintainership, it is not likely to be changed and bug reports against > > ping are not likely to be

Re: Bug in ping? ICMP Sequence Number octets are reversed

On 2008-06-13, Christopher Faylor wrote: > On Fri, Jun 13, 2008 at 04:36:03PM +0200, Corinna Vinschen wrote: > >On Jun 13 10:07, Christopher Faylor wrote: > >> ping does not have a maintainer currently so, unless someone wants to take > >> over maintainership, it is n

Re: Bug in ping? ICMP Sequence Number octets are reversed

On Jun 13 11:14, Lee Maschmeyer wrote: > Cygwin does have "pinky" but it never works for me. Is pinky supposed to > need a special server? Our site works for (Windows) finger but not Cygwin > pinky and I don't know whose fault that is. Pinky access the utmp file which is only created for login's

Re: Bug in ping? ICMP Sequence Number octets are reversed

If you ditch the Cygwin Ping I hope the Windows version can work better than the Windows version of Finger. If I execute finger from Cygwin I get a loop where the help text is executed about 3 times and no finger results are given. It took a distressingly long time before I realized there isn&#

Re: Bug in ping? ICMP Sequence Number octets are reversed

On Fri, Jun 13, 2008 at 04:36:03PM +0200, Corinna Vinschen wrote: >On Jun 13 10:07, Christopher Faylor wrote: >> ping does not have a maintainer currently so, unless someone wants to take >> over maintainership, it is not likely to be changed and bug reports against >> ping

Re: Bug in ping? ICMP Sequence Number octets are reversed

On Jun 13 10:07, Christopher Faylor wrote: > ping does not have a maintainer currently so, unless someone wants to take > over maintainership, it is not likely to be changed and bug reports against > ping are not likely to be acted upon. I'm wondering if we need it at all. It d

Re: Bug in ping? ICMP Sequence Number octets are reversed

On Fri, Jun 13, 2008 at 09:24:27AM +0200, Spiro Trikaliotis wrote: >Hello, > >I just had a (short) session with Wireshark: > >* On Thu, Jun 12, 2008 at 10:39:09PM -0700 Gary Johnson wrote: > >> I've been using Cygwin's ping (/usr/bin/ping, ping-1.0-1) to do some

Re: Bug in ping? ICMP Sequence Number octets are reversed

Hello, I just had a (short) session with Wireshark: * On Thu, Jun 12, 2008 at 10:39:09PM -0700 Gary Johnson wrote: > I've been using Cygwin's ping (/usr/bin/ping, ping-1.0-1) to do some > testing of IP over a wireless modem. [...] > It looks like someone just wrote a s

Bug in ping? ICMP Sequence Number octets are reversed

I've been using Cygwin's ping (/usr/bin/ping, ping-1.0-1) to do some testing of IP over a wireless modem. In the process, I was trying to correlate the icmp_seq values in ping's output with the ICMP Sequence Number field values in a log of the IP messages. What I discove

RE: Bug in /usr/bin/ping

Tom Van Looy wrote on 28 May 2008 13:52: > I looked a little further and saw that this is a port that I probably > just installed to try it out and hoped it had GNU ping arguments (so bash > scripts are portable between Linux and Cygwin). > > Anyway, I don't know what happe

Re: Bug in /usr/bin/ping

I looked a little further and saw that this is a port that I probably just installed to try it out and hoped it had GNU ping arguments (so bash scripts are portable between Linux and Cygwin). Anyway, I don't know what happend but it's a 4.3BSD utility. Even 4.3BSD derived systems do

RE: Bug in /usr/bin/ping

> Didn't read the --help, either, as far as I can see. Ehrr... right, my fault. Wrong copy from my terminal. But that does not change the ping behavior ... $ /usr/bin/ping 192.168.20.9 56 1 ; echo $? PING 192.168.20.9 (192.168.20.9): 56 data bytes 64 bytes from 192.168.20.9: icmp_seq=

  1   2   3   4   >