Message-Id: <200503060140.j261e5Zw023514@delorie.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Gary R. Van Sickle" To: Subject: RE: apparent bug: incorrect file position after write() Date: Sat, 5 Mar 2005 19:39:57 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20050305212628.80C37164005@ws1-4.us4.outblaze.com> X-IsSubscribed: yes > -----Original Message----- > From: cygwin-owner AT cygwin DOT com > [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of imaginate > australiamail.com > Sent: Saturday, March 05, 2005 3:26 PM > To: cygwin AT cygwin DOT com > Subject: Re: apparent bug: incorrect file position after write() > > > > > Brian Dessent wrote: > > > > > If > you don't want that, then don't use textmode mounts. > > > > ...or open the file with O_BINARY. > > > > Mounting binary solves the problem - I wasn't aware of that > functionality. O_BINARY is probably not so portable so I'll > steer clear of that. > > Cheers for the help. > O_BINARY is POSIX. Use it. Do this if you have to: #ifndef O_BINARY #define O_BINARY 0 -- Gary R. Van Sickle -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/