RE: Re: Changing symlinks from

>On Tue, Feb 11, 2003 at 01:05:06PM -0000, Christopher January wrote: >> How can I automatically convert all symlinks on my Cygwin filesystem from >> the "!" format to windows shortcuts? Samba doesn't seem to >> maintain the correct permissions for the Cygw

Changing symlinks from "magic" format to windows shortcuts.

How can I automatically convert all symlinks on my Cygwin filesystem from the "!" format to windows shortcuts? Samba doesn't seem to maintain the correct permissions for the Cygwin DLL to detect the "!" files as symlinks, so they are treated as regular files (hence the errors with gcc, etc. I was s

Problems compiling trivial C program.

I'm having trouble compiling this test program: void f(){} using the command line: gcc test.c -c -o test.o using 1.3.19 or latest Cygwin snapshot (2003-Feb-07) (same error with both) and gcc-3.2-3. The error I see is: 16 bit MS-DOS Subsystem /usr/src/cygwin-cvs/obj The NTVDM CPU has encountere

Re: 1.1.3 and upwards: apparent bug with pthread_cond_wait() and/or signal()

> Between 1.1.3 and 1.3.0 a huge change occurred in the pthreads code > base, so this assumption is not safe. (It's not necessarily wrong > either.) I'd definitely be using 1.3.10 though. > > > #include > > #include > > The cygwin c++ libgcc, stdlibc++ and gcc are not built with thread > support

Re: /cygdrive wierdness

> > > > > Using Cygwin DLL 1.3.10. > > > > > > > > Likewise. (On Win2K.) > > > > > > > > > 1. Close all Cygwin programs > > > > > 2. Open bash > > > > > 3. Type: cd /cygdrive > > > > > 4. Type ls > > > > > I get a listing of C:\ instead > > > > > 5. Type bash > > > > > 6. Type: cd /cygdrive > > >

Cygwin website

The news items on http://www.cygwin.com have a closing tag, but are missing the opening tag. Regards Chris -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ:

Re: A real fork() on NT

> >I've got the book; I have a DLL that exports a function called fork and > >I'm seeing what can be done to get it to work with kdeinit. A lot of > >programs do: if (fork() == 0) exec(...) and this could be replaced by > >spawn(...) anyway, but kdeinit does a bit more work. > > So, use vfork().

Re: A real fork() on NT

> When looking at XP's CreateProcessW (or rather, CreateProcessInternalW) I > noticed something strange about the way it creates a process. It seems > that NT is sort of capable of a fork() command. The function > NtCreateProcess appears to create a "blank" process, into which you can put > anyt