> > Possibly I should add that I am comparing the behavior of > version 1.5.10 to a much older version that I was using > before.
It wasn't by chance... oh... say... B20? ;-) > So whatever is causing this odd behavior on my system > may not be a feature that was new to version 1.5.10. I am > thinking somehow that it might in fact have something to do > with how mounts are handled differently in more recent > versions. Previously I did not have to mount any directories, Yikes. I can't recall a time when you didn't have to mount directories, and I've been round these parts forever. That must be some *old* Cygwin! > now though I am having trouble finding any set of mount > commands that will allow me to open files in text mode by > default, which was how the earlier version of cygwin I had > worked. Nor does setting the CYGWIN environment variable to > nobinmode seem to have any effect. Don't worry about the CYGWIN var anymore, it's all mounts these days. "mount --help" and "umount --help" is what you want. Set up your mount table like this: C:\unix\bin on /usr/bin type system (textmode) C:\unix\lib on /usr/lib type system (textmode) C:\unix on / type system (textmode) c: on /cygdrive/c type user (textmode,noumount) d: on /cygdrive/d type user (textmode,noumount) e: on /cygdrive/e type user (textmode,noumount) And you're all set. You have to umount before mounting if any of the directories are already mounted unfortunately (last I checked anyway). -- 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/ > -- 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/
