From: "KARL BOTTS" <kdbotts@usa.net>
To: <cygwin@cygwin.com>
Subject: Re: less.exe v481-1 cannot seek to EOF in CRLF file; current cygwin32, Win10 only.
Date: Tue, 02 Feb 2016 23:57:00 -0000 [thread overview]
Message-ID: <882uBBX5J7984S05.1454457429@web05.cms.usa.net> (raw)
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 having
various line-ending related problems, particularly from <bash> and <less>.
I reported that here under the subject line of this message, a week or so ago.
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=0,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 <mount>
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" option,
which had some effect on how line endings were handled. I am not sure it was
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 needed,
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
next reply other threads:[~2016-02-02 23:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 23:57 KARL BOTTS [this message]
[not found] <190uaVPZ59120S08.1453476416@web08.cms.usa.net>
2016-01-22 18:50 ` Marco Atzeri
[not found] ` <20160122221927.042AA9E0.helmut.karlowski@ish.de>
2016-01-23 0:04 ` Helmut Karlowski
-- strict thread matches above, loose matches on Subject: below --
2016-01-20 21:02 KARL BOTTS
2016-01-21 15:11 ` Marco Atzeri
2016-01-23 3:49 ` KARL BOTTS
2016-09-08 13:07 ` staffanu
2016-09-08 13:38 ` Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=882uBBX5J7984S05.1454457429@web05.cms.usa.net \
--to=kdbotts@usa.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).