Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3C07FC89.721551E7@ece.gatech.edu> Date: Fri, 30 Nov 2001 16:39:21 -0500 From: Charles Wilson X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: "Pierre A. Humblet" CC: cygwin AT cygwin DOT com Subject: Re: More exim, and fcntl lock problems References: <3C07F55F DOT 5B2E669D AT ieee DOT org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-milter (http://amavis.org/) "Pierre A. Humblet" wrote: > That's where the bad news start, I tried Win98 and NT. > 1) Under Win98 I hit issues that were traced to gdbm > emulation of ndbm on FAT > http://cygwin.com/ml/cygwin/2001-11/msg01793.html > That looks hopeless to me. Please tell me I am wrong! Not totally. See cvs-1.10-1 announcement, and the patchfile within cygwin's cvs-1.10-1-src tarball. Basically, there are two solutions; 1) convert exim over to use the gdbm interface (only one file, no worries about timestamp sync between two files, no hardlink/cp problems). 2) write your own wrapper functions for all "ndbm" calls, that thunk to actual gdbm (not ndbm emulation in gdbm) calls. This is what I did to get cvs repositories to host on FAT. --Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/