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 sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <17B78BDF120BD411B70100500422FC6309E056@IIS000> From: Bernard Dautrevaux To: "'cygwin AT sourceware DOT cygnus DOT com'" Subject: RE: New version of setup.exe with fixes for i686-pc-cygwin/* prob lem Date: Fri, 9 Jun 2000 18:07:25 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id MAA21154 > -----Original Message----- > From: Chris Faylor [mailto:cgf AT cygnus DOT com] > Sent: Thursday, June 08, 2000 10:11 PM > To: cygwin AT sourceware DOT cygnus DOT com > Subject: Re: New version of setup.exe with fixes for i686-pc-cygwin/* > problem > > > On Thu, Jun 08, 2000 at 09:03:22PM +0100, Jonathan Larmour wrote: > >In article <20000608173106 DOT 5178 DOT qmail AT web125 DOT yahoomail DOT com> > you write: > >> > >>You need to decide, binmode or textmode. Operating in both > is a major cause > >>for a major headache. > > > >Isn't the point that it depends on the data at that mount > point? In the case > >of Windows-y areas, text mode is exactly correct. > > > >Plus textmode is still the default for mount. > > Yup. Good points. > > If you know what you're doing, there is no reason not to mix. > I think that > the default "root" mounts like /bin, /lib, and /usr should be > binary. Everything > else can be whatever makes sense. > > The problem is that many people use an "identity mount" where > c:\ == /. The > current version of setup.exe mounts root as binary, similarly > to the Cygwin CD. > > This causes problems who have something like a 'c:\src' > directory since it will > automatically be considered to be binmode by default. > > DJ has suggested that a future version of cygwin should > default to "read text, > write binary". I think we'll probably be moving to that > model sometime soon. Here is how I've managed to avoid problems in my UNIX->Windows ports: I wrapped all open's in a routine that (among other things) change all "read only" opens to text if not specified, and all "read/write" or "write only" opens to binary (still if not explicitely specified). Thus providing an implicit default like this (perhaps for a drive mounted "-a") should be quite good. Note that "read/write" in text mode is quite difficult to implement and use correctly, especially if one seeks before writing... :-), so the best default in this case is "binary". Chris, do I understand correctly that above, when saying "read text, write binary" you are speaking about the default mode for open's where neither O_TEXT nor O_BINARY are specified? otherwise reading a file in text mode then switching to binary when writing the same file will most probably give quite weird results ;-( Anyway thanks for the good job, 1.1.2 seems what I was waiting for. Bernard > > This will essentially provide a third mount option, like "-a". > > cgf > > -- > Want to unsubscribe from this list? > Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com > -------------------------------------------- Bernard Dautrevaux Microprocess Ingéniérie 97 bis, rue de Colombes 92400 COURBEVOIE FRANCE Tel: +33 (0) 1 47 68 80 80 Fax: +33 (0) 1 47 88 97 85 e-mail: dautrevaux AT microprocess DOT com b DOT dautrevaux AT usa DOT net -------------------------------------------- -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com