From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 97967 invoked by alias); 2 Feb 2016 23:57:19 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 97951 invoked by uid 89); 2 Feb 2016 23:57:18 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.1 required=5.0 tests=AWL,BAYES_50,FSL_HELO_BARE_IP_2,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,SPF_PASS autolearn=no version=3.3.2 spammy=patience, everyones, everyone's, herring X-HELO: co03.mbox.net Received: from co03.mbox.net (HELO co03.mbox.net) (165.212.64.33) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Tue, 02 Feb 2016 23:57:17 +0000 Received: from co03.mbox.net (localhost [127.0.0.1]) by co03.mbox.net (Postfix) with ESMTP id 3pw33H3swTzq2bb for ; Tue, 2 Feb 2016 23:57:15 +0000 (UTC) X-USANET-Received: from co03.mbox.net [127.0.0.1] by co03.mbox.net via mtad (C8.MAIN.4.02J) with ESMTP id 409uBBX6J1088M03; Tue, 02 Feb 2016 23:57:09 -0000 X-USANET-Routed: 3 gwsout-vs Q:bmvirus X-USANET-Routed: 3 gwsout-vs Q:bmvirus X-USANET-GWS2-Tenant: usa.net X-USANET-GWS2-Tagid: UNKN Received: from ca31.cms.usa.net [165.212.11.131] by co03.mbox.net via smtad (C8.MAIN.4.02Q) with ESMTP id XID028uBBX6J3700X03; Tue, 02 Feb 2016 23:57:09 -0000 X-USANET-Source: 165.212.11.131 OUT kdbotts@usa.net ca31.cms.usa.net CLR X-USANET-MsgId: XID028uBBX6J3700X03 Received: from web05.cms.usa.net [165.212.8.205] by ca31.cms.usa.net (ESMTP/kdbotts@usa.net) via mtad (C8.MAIN.3.95M) with ESMTP id 326uBBX6J2656M31; Tue, 02 Feb 2016 23:57:09 -0000 X-USANET-Auth: 165.212.8.205 AUTO kdbotts@usa.net web05.cms.usa.net Received: from 66.54.154.34 [66.54.154.34] by web05.cms.usa.net (USANET web-mailer C8.MAIN.4.04N); Tue, 02 Feb 2016 23:57:09 -0000 Date: Tue, 02 Feb 2016 23:57:00 -0000 From: "KARL BOTTS" To: Subject: Re: less.exe v481-1 cannot seek to EOF in CRLF file; current cygwin32, Win10 only. Mime-Version: 1.0 Message-ID: <882uBBX5J7984S05.1454457429@web05.cms.usa.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Z-USANET-MsgId: XID326uBBX6J2656X31 X-IsSubscribed: yes X-SW-Source: 2016-02/txt/msg00029.txt.bz2 This is to close out my earlier bug report. I think it contains a useful caveat for others. I have a very old cygwin installation, which I propagate by updating it on = one machine via setup.exe, and then copying the whole c:/cygwin tree to several other machines, with tar or rsync. I have not installed it from scratch for well over ten years. After I updated from cyg1.7 to cyg2.3, I started havi= ng various line-ending related problems, particularly from and . I reported that here under the subject line of this message, a week or so a= go. Helmut and Marco kindly tried to reproduce it, and failed. I inferred from this that there was something wrong with my ancient installation. I reinstalled from scratch on one machine, and the problems were gone. After diffing and digging for awhile, I think I found the problem: My old /etc/fstab, that had not been changed for years and worked under 1.7, has one non-comment line: none / cygdrive text,posix=3D0,user 0 0 The same file in the from-scratch install (after running 'mount -c /') has: none / cygdrive binary,user 0 0 Also present in my (even more ancient) home dir, is a bash script containing lines like: mount -u -t --change-cygdrive-prefix "/" mount -s -t --change-cygdrive-prefix "/" Note that the -u, -s and -t options are not supported by cygwin anymore. I dimly remember that, long ago, I would run that script after copying to a new machine, but I have not done so for years. So the upshot, I think, is this: Cygwin _used_ to support the notion of mounting volumes with a "text" optio= n, which had some effect on how line endings were handled. I am not sure it w= as ever valuable, and I don't remember why I did it, but apparently I did, long ago. Cygwin no longer really supports the "text" option (you could still set it with mount -o, but I do not recommend that). Further, it is no longer need= ed, if it ever was, which I doubt. And with it, some critical apps will suffer line ending problems. So don't do that. I think the Win10 business was a red herring. Thanks for everyone's help and patience. --- Karl Botts, kdbotts@usa.net -- 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