X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <4C2B1AF9.20909@ivu.de> Date: Wed, 30 Jun 2010 12:22:49 +0200 From: =?UTF-8?B?SmFuIEzDvGJiZQ==?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; de; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: default text mode References: <4C28834A DOT 9040001 AT ivu DOT de> <20100628113502 DOT GD6310 AT calimero DOT vinschen DOT de> <4C288E13 DOT 1090208 AT ivu DOT de> <20100628150342 DOT GF6310 AT calimero DOT vinschen DOT de> In-Reply-To: <20100628150342.GF6310@calimero.vinschen.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Hi, Am 28.06.2010 17:03, schrieb Corinna Vinschen: > On Jun 28 13:57, Jan Lübbe wrote: >> Am 28.06.2010 13:35, schrieb Corinna Vinschen: >>> Role? The automatism is to use binary mode unless /etc/fstab says >>> something else. Other than that, why would you do that at all? >>> If you need textmode for something, do it under some mount point >>> of your own. There's no good reason to use textmode for the system >>> directories, unless Cygwin is too fast on your machine. >> >> Cygwin is not to fast, but if I run sed on files all Windows EOL are >> replaced with Unix EOL. That damages my version control. Of course I >> can run u2d on that files manually, but I don't want to remind that >> all time. >> >> The files itself are mounted in text mode. They are under >> /cygdrive/d/Projekte/. But sed changes the EOL anyway. Because sed >> is saved in /usr/bin, which is mounted in binary mode, I thought >> this is the reason for sed doing so. > > Nope. Sed is a stream editor. Usually it does not open the output file > by itself but just writes to stdout. Whoever opened the stdout stream > has opened it in binary mode. Are you sure the file is actually written > to the textmode mounted area? Maybe it's written to /tmp and then just > moved over. That would explain the behaviour quite naturally. > >> Also one cannot change the way of mounting /, /usr/bin, and /usr/lib >> in fstab, as you can see: >> >>> % cat /etc/fstab >>> # For a description of the file format, see the Users Guide >>> # http://cygwin.com/cygwin-ug-net/using.html#mount-table >>> >>> none /cygdrive cygdrive text,posix=0,user 0 0 >> >> There is only the possibility to change the way of mounting /cygdrive. > > Erm... > >> Thanks for further advises. > > The advice is given in the /etc/fstab file itself: > > # For a description of the file format, see the Users Guide > # http://cygwin.com/cygwin-ug-net/using.html#mount-table > > > Corinna > Which part in that description do you mean? I only find: > Note that entries for /, /usr/bin, and /usr/lib are never generated. How can I check wether the files are written to /tmp? In one directory I got the error > sed: preserving permissions for `./sedBHiGtF': Permission denied which seems to indicate, that the file is not moved to /tmp, right? Any further ideas? Can somebody reproduce this, or the opposite? Cheers, Jan -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple