This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: File format problem after updatin to 1.7.1


On 1/29/2010 9:07 AM, Andy Koppe wrote:
> Jeremy Bopp:
>> DEWI - N. Zacharias:
>>> i have just updated to 1.7.1 an run in trouble.  During the previous installations there was a switch which sets the used file format Dos/Unix. This switch did not only disappear also the former uses file format (DOS) was set to Unix underhand . The result is that a lot of scripts did not work anymore because they produce  a bunch of lines " bash: $'\r': command not found" instead of the expected output.  I'm not able to filter all the scripts and files to remove the DOS line separator so I have to set the file format correctly.
>>>
>>> As far I can see there is no topic in the user manual which covers this issue also nothing in the FAQ.
>>
>> http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
>>
>> Among other things that section discusses the /etc/fstab file and the
>> mount options available, two of which are "binary" and "text".  You need
>> to add entries to your /etc/fstab file for at least the paths which
>> contain your files, likely /cygdrive/c or something similar, which set
>> the "text" mount option.  Using your cygdrive as an example:
>>
>> none /cygdrive cygdrive text,posix=0,user 0 0
> 
> Also, there's this at the top of http://www.cygwin.com:
> 
> "Please note that the update from Cygwin 1.5.x to Cygwin 1.7.x might
> require some manual changes afterwards. Most notably the mount point
> storage has been moved out of the registry into files. User mount
> points are NOT copied into the new user-specific /etc/fstab.d/$USER
> file. Rather, every user has to call the /bin/copy-user-registry-fstab
> shell script once after the update."

I've not used that script before, but from that text it seems that the
script can only migrate user mounts, not system mounts.  I get the
impression that this problem is resulting from system mounts going binary.

-Jeremy

--
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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]