Re: 1.7: hostname resolution works for Windows programs, but not Cygwin programs

Brolin Empey wrote: Hostname resolution has started working for Cygwin programs on optiplex960 since the last time I tried, even though the Windows (non-Cygwin) version of nslookup returns NXDOMAIN for the same hostname. Strange, but at least it works. So now only howard + brolin-V13 need to be

Re: 1.7: hostname resolution works for Windows programs, but not Cygwin programs

Brolin Empey wrote: Hostname resolution stopped working for Cygwin programs in 2 other Cygwin installations which were upgraded from Cygwin 1.5 too: one of these installations is on howard, which is a desktop running Windows 2000 Professional Edition SP4 i386. The other is optiplex960, a tower

1.7: hostname resolution works for Windows programs, but not Cygwin programs

Hello, I have a new installation of Cygwin 1.7 on Windows 7 Professional 32-bit on brolin-V13, my Dell Vostro V13 laptop. Windows (non-Cygwin) programs, such as nslookup, can resolve the hostnames of Ubuntu PCs on the LAN, but Cygwin programs, such as ssh from OpenSSH, cannot resolve the sa

Re: missing setup command line arguments in the FAQ.

I found this message in my hosted Gmail (Google Apps) account’s Spam folder. I wonder why Gmail thought it was spam? Because it contained the URL of a(n) (Windows) executable file? Dave Korn wrote: G.W. Haywood wrote: BTW, if you run "setup.exe --help", it will (depending on OS version) ei

packaging mtr + minicom

Hello list, Is anyone willing to maintain Cygwin packages of mtr and/or minicom? I know about WinMTR, but I prefer the original mtr over WinMTR because I think mtr is better suited to a console program, not a GUI program. I also know about the “Minicom binaries for Cygwin” Web page [1] and know