RE: Advocacy

I can't believe I'm actually chiming in on this one... If you add some sort of END marker, you might as well add a BEGIN marker of some sort as well, in case over-zealous corporate e-mail security-types get wind of what's going on. :-) Always be sure to point out that this isn't meant to defeat th

RE: file name case sensitivity

Sorry this is getting a bit OT... Shankar Unni wrote: > Very interesting. Once you do create such files [...], will regular > Windows programs be able to even look at that directory? Or will > they choke on those names [...] ? Obviously, you need to do something special to get at the files or the

RE: file name case sensitivity

Shankar Unni wrote: > > Yes, but in my opinion it could be of use to John Williams because he > > wanted to "case sensitivity in filenames under Cygwin". > > No, it won't work, because if you remember, he said that he had files > with the same name but different case *in the same directory*. Th

RE: GPL Violation

cgf wrote: > The standalone DLL that we support is cygwin1.dll. We don't support > it for free, however, as much as people want us to. My mistake. Yes, that's exactly what I was talking about. I was thinking about open-source projects (which in this case they have to be) posting binary releases f

RE: GPL Violation

I wrote: > There is another side to this issue: the fact that RedHat is > not in the business of supporting a standalone cygwin1.DLL, ^^^ I knew that I shouldn't have touched that one yet... I'm assuming that the standalone DLL that RedHat IS in the business of supporting (i.e.,

RE: GPL Violation

Robert Citek wrote: > Lawyer? Three years? We don't even have funds to buy pizza and beer let > alone a lawyer. We are not in the software distribution business. > That's what Red Hat is for. That is why I buy and recommend Red Hat. Disclaimer: IANAL RedHat uses the option whereby you can dow

RE: GPL Violation

<[EMAIL PROTECTED]> wrote: > > Please provide the Cygwin source that corresponds to the > > version of cygwin1.dll on the above web page at your > > earliest convenience. > > Not necessarily. See section 3 of the GPL (version 2) where other > alternatives are listed. Good point. You are not req

Re: hi

Marcel Telka wrote: > cat > filename:-) Of course, if you count cat as an editor, you have to count uudecode as a compiler. :-) -Jerry -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cyg

Re: Cygwin official logo ?

Unless someone at least has some artwork to show, why are we still discussing alternative animals? I could give more reasons to choose a cygnet, but why waste the time? If cgf wants an otter, we should be looking into how to get a good drawing of one. Preferably a mean one, I guess. :-) I suppose

Re: cygwin official logo ?

Christopher Faylor wrote: > Please grant me this one conceit. Linus likes penguins. I like otters. > > If there is going to be an animal mascot for cygwin it should be an otter. Bummer, I was going to suggest a baby swan (i.e., a cygnet). So, will it be a river otter or a sea otter? -Jerry

[ANNOUNCEMENT] Updated: swig-1.3.16-1

I've updated the version of SWIG to 1.3.16-1. Tarballs should be available on the Cygwin mirrors shortly. As per the SWIG web page (http://www.swig.org): SWIG (Simplified Wrapper Interface Generator) is a software development tool that connects programs written in C and C++ with a variety o

RE: "==" operand not found

Scott Prive wrote: > 1) Why is ash the default? At least on UNIX systems that use "true" >sh -- usually just /bin/bash in /bin/sh compatibility mode But bash in compatibility mode isn't true Bourne shell. For instance, /bin/sh on a Solaris box doesn't support the "==" operator either. This is

RE: Python support for Tcl 8.0

Jason Tishler wrote: > > (I'm not entirely sure why Tcl/Tk is stuck at 8.0--I thought Cygwin > > was supported through 8.2 or 8.3. But that's another matter.) > > As Chris has already stated, it is in the archives. I know, but from the 80,000 foot view it looked like the pieces were there. The o

Re: Python support for Tcl 8.0

Jason Tishler wrote: > I guess that when Python 2.3 is released, I will most likely have to > drop support for the _tkinter module. Please let's not. The BDFL's comments were based on the assumption that Tcl/Tk 8.0 isn't being used, which is clearly not true if Cygwin is stuck with it for a while

[ANNOUNCEMENT] Updated: swig-1.3.15-1

I've updated the version of SWIG to 1.3.15-1. Tarballs should be available on the Cygwin mirrors shortly. As per the SWIG web page (http://www.swig.org): SWIG (Simplified Wrapper Interface Generator) is a software development tool that connects programs written in C, C++, and Objective-C w

Re: "Application failed to initialize (0xc0000022)"

Cross-posting the resolution... Christopher Faylor wrote: > It's usually caused by the use of CYGWIN=ntsec and cygwin1.dll not having > executable permissions, I believe. It's showed up here from time to time. > > So, doing something like: > > c:\>set CYGWIN=ntsec > c:\>chmod a+rx /bin/* > >

RE: Viruses being transported with cygwin messages

Tim Prince wrote: > Earthlink gave me immediate automatic acknowledgment that these were viruses > originated by one of their customers. Sorry for the extra noise, but in case anyone's trying to track down the sources, I also got a message claiming to be from Christopher Faylor (though with the

RE: "Application failed to initialize (0xc0000022)"

Now I'm pretty convinced it's not a rebase thing but some time of security/access issue. I found a few references in MSDN referring to this error message. They seem to have to do with access rights and directories searched for a DLL (e.g., if you don't have rights to a network drive in your path)

RE: "Application failed to initialize (0xc0000022)"

Jason Tishler wrote: > > Is it possible that this is an aspect of the dreaded "rebase" issue? > > I don't think so. If it was, then you would have experienced fork() > failures with messages (not dialogs) like the following: That was my initial impression also. But what could cause that error?

"Application failed to initialize (0xc0000022)"

I'm running Win2K and very recent full Cygwin install. I ran into this when I tried to install KDE, but it's not a KDE issue (I tried that list anyway to see if this had been seen). It involves XFree86, although I suspect it's not really an X issue, either. When I replace the X library with one

RE: NTTY

Karen Oakley wrote: > >could you please tell me what NTTY stands for?? thanks I seem to remember this having something to do with low-level line control in Unix. The following web page calls it a "Hardware Emulation Module" (Google is your friend): http://www.ceng.metu.edu.tr/~aydin/files/PROGRA

RE: mkpasswd (Win2K) cannot find the domain controller

Heribert Dahms wrote: > maybe Jerry should improve his patch to make it runtime selectable like > mkpasswd --use-netgetanydcname [...] Corinna Vinschen wrote: > > I'm somewhat reluctant to apply that patch to mkpasswd. The > > reason is... I don't know. I recalled that I'd once changed > > from

RE: Finding your SID (was Re: problem starting inetd as NT service)

Problem solved. I thought that I was able to contact the domain controller, since I was able to change my domain password successfully and do other sorts of things that required me to login. However, apparently this was something other than the PDC or BDC. Or at least I was in a situation where I

[ANNOUNCEMENT] New Package: SWIG

The 'SWIG' package is now available via setup.exe. As per the SWIG web page (http://www.swig.org): SWIG (Simplified Wrapper Interface Generator) is a software development tool that connects programs written in C, C++, and Objective-C with a variety of high-level programming languages. SWIG is pr

RE: pthread_cond_wait does not relock mutex on release

ber of sem_wait() and sem_post() calls (extra sem_post() calls would cause future sem_wait()'s not to wait). -Jerry -O Gerald S. Williams, 55A-134A-E : mailto:[EMAIL PROTECTED] O- -O AGERE SYSTEMS, 6755 SNOWDRIFT RD : office:610-712-8661 O- -O ALLENTOWN, PA, USA 18106-9353: mobile:

RE: sunRPC on V1.3.x

I'm not sure if this helps, but there are some ports for Windows NT/95. A google search for ONCRPC found this site: http://www.plt.rwth-aachen.de/ks/english/oncrpc.html Although I know there are several versions of that same code by Marting Gergeleit. Source code is included. -O Ger

RE: sem_trywait returns EAGAIN (rather than returning -1 and setting errno)

for failure (putting the error code in errno), since 0 is never a legal errno code. You may find it useful if you are using pthreads and semaphore code at the same time and want the return codes to work the same. -Jerry -O Gerald S. Williams, 22Y-103GA : mailto:[EMAIL PROTECTED] O- -O AGERE SYSTEMS,

RE: Threaded Cygwin Python Problem (was Re: Creating a local mirror ...)

provide more details on the above. Maybe the same or similar > workaround could help for Cygwin too? I wasn't privy to the details, although I'll shoot him an e-mail (he's no longer with the company). From the source code (uncommented, of course), it looks like the workaround h

RE: Creating a local mirror for setup.exe

and put into an official release. BTW, Cygwin is not the only platform to have problems with pthreads. Another member of my group found a problem with the Solaris pthreads package that he had to work around. -Jerry -O Gerald S. Williams, 22Y-103GA : mailto:[EMAIL PROTECTED] O- -O AGERE SYSTEMS, 555 UNIO

RE: "Best" way to build a DLL?

stutils package sets this automatically, but we're not using it. -Jerry -O Gerald S. Williams, 22Y-103GA : mailto:[EMAIL PROTECTED] O- -O AGERE SYSTEMS, 555 UNION BLVD : office:610-712-8661 O- -O ALLENTOWN, PA, USA 18109-3286 : mobile:908-672-7592 O- Jason Tishler wrote: > Just to be cle

RE: /usr/bin/env - Incorrect parsing of #! line?

ing breaks anything (i.e., find out if this is a win-win feature), although this is hardly likely to be on anyone's priority list soon. -Jerry -O Gerald S. Williams, 22Y-103GA : mailto:[EMAIL PROTECTED] O- -O AGERE SYSTEMS, 555 UNION BLVD : office:610-712-8661 O- -O ALLENTOWN, PA, USA 1810

RE: /usr/bin/env - Incorrect parsing of #! line?

WIN issue as well. Either way, it sounds like DG has a pretty good handle on this issue. -O Gerald S. Williams, 22Y-103GA : mailto:[EMAIL PROTECTED] O- -O AGERE SYSTEMS, 555 UNION BLVD : office:610-712-8661 O- -O ALLENTOWN, PA, USA 18109-3286 : mobile:908-672-7592 O- -- Unsubscribe info

RE: /usr/bin/env - Incorrect parsing of #! line?

is ignored. I have also seen examples in popular Unix books (such as the O'Reilly nutshell books) that rely on multiple arguments. -Jerry -O Gerald S. Williams, 22Y-103GA : mailto:[EMAIL PROTECTED] O- -O AGERE SYSTEMS, 555 UNION BLVD : office:610-712-8661 O- -O ALLENTOWN, PA, USA 18109-3286