This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re[2]: mount command and text/binary mode
At 07:32 PM 4/2/2001, TaKeDa wrote:
>Hi Inc),
>
>Monday, April 02, 2001, 4:06:40 PM, you wrote:
>
> >>$ mount
> >>Device Directory Type Flags
> >>c:\SERVER\Apache\cgi-bin /mnt/cgi user binmode
> >>C:\SERVER\eggdrop\1.5.3 /mnt/egg user binmode
> >>C:\CygWin\home\takeda /home/administrator user binmode
> >>C:\CygWin\bin /usr/bin user binmode
> >>C:\CygWin\lib /usr/lib user binmode
> >>C:\CygWin / user binmode
> >>
> >>$ mount --show-cygdrive-prefixes
> >>Prefix Type Flags
> >>/cygdrive user binmode
> >>
> >>As you see all mounting points are set into binary mode, but I notice
> >>that cygwin still write files in text mode and this is realy anoying.
>
>
>LHRPI> Can you give an example and provide the output of cygcheck -s -r -v on the
>LHRPI> system from which you ran the example?
>
>I just upgrade, and some things change, but problem is still there :/
>
And the example that shows the problem?
<snip>
> 615k 2001/01/31 C:\CygWin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
> "cygwin1.dll" v0.0 ts=2001/1/31 7:08
> Cygwin DLL version info:
> dll major: 1001
> dll minor: 8
> dll epoch: 19
> dll bad signal mask: 19005
> dll old termios: 5
> dll malloc env: 28
> api major: 0
> api minor: 34
> shared data: 3
> dll identifier: cygwin1
> mount registry: 2
> cygnus registry name: Cygnus Solutions
> cygwin registry name: Cygwin
> program options name: Program Options
> cygwin mount registry name: mounts v2
> cygdrive flags: cygdrive flags
> cygdrive prefix: cygdrive prefix
> cygdrive default prefix:
> build date: Wed Jan 31 10:08:38 EST 2001
> shared id: cygwin1S3
>
> 615k 2001/01/31 c:\COMMAND\cygwin1.dll - os=4.0 img=1.0 sys=4.0
> "cygwin1.dll" v0.0 ts=2001/1/31 7:08
> Cygwin DLL version info:
> dll major: 1001
> dll minor: 8
> dll epoch: 19
> dll bad signal mask: 19005
> dll old termios: 5
> dll malloc env: 28
> api major: 0
> api minor: 34
> shared data: 3
> dll identifier: cygwin1
> mount registry: 2
> cygnus registry name: Cygnus Solutions
> cygwin registry name: Cygwin
> program options name: Program Options
> cygwin mount registry name: mounts v2
> cygdrive flags: cygdrive flags
> cygdrive prefix: cygdrive prefix
> cygdrive default prefix:
> build date: Wed Jan 31 10:08:38 EST 2001
> shared id: cygwin1S3
>
>Use -h to see help about each section
Get rid of one of these. Never keep duplicate cygwin1.dlls on your system.
> >>BTW2: Why I can't add mount point to system-wide registry location?
> >>When I trying to use arguments -bs it displays help.
>
>LHRPI> Try mount -b -s <the rest of the line>
>It works, thank you.
>Because of this:
>"usage mount [-bfstux] <win32path> <posixpath>"
>I understand syntax incorrectly.
Yes, this is a "bug".
> >>BTW3: It's normal that when I'm mounting in place of win32patch
> >>Instead of backslashes I need to use shlashes?
> >>ie. C:\WINDOWS I need write as C:/WINDOWS to make mount command
> >>working.
>LHRPI> In bash/sh, yes. If you want to use backslashes, you need to escape them.
>LHRPI> Remember, if you're in a UNIX-like shell, you're in a UNIX-like world!;-)
>
>Ok, I just say that because I was thinking that problem can be there.
Yes, this is a common cockpit error we see on this list.
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple