Re: text / binary mounts (sorry)

Re: text / binary mounts (sorry)

[Chris Faylor]

On Fri, Jun 02, 2000 at 12:30:31PM -0500, Parker, Ron wrote:
>> > > set CYGWIN=binmode causes even unmounted directories and 
>> files to be
>> > > accessed in binary mode.  You can set this in autoexec.bat 
>> > for Win9x or in
>> > > the System Control Panel applet for NT/2000.
>> > > 
>> > 
>> > Are you sure of this, Ron?  AFAIK CYGWIN=binmode only affects 
>> > the pipes and
>> > redirection and not file I/O.  BTW CYGWIN=binmode is the default.
>> 
>> ITIWTW, I thought it worked that way, however a quick test 
>> shows I am wrong.  I would have sworn CYGWIN=binmode used to 
>> apply to all file opens.
>> 
>> Sorry for the confusion.
>
>So is there anyway to have 'echo Hello>//h/junk' produce a 6-byte file?

Yes.  You use the mount command that was mentioned previously in this thread.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: text / binary mounts (sorry)

[David Bolen]

Chris Faylor [cgf@cygnus.com]:

> Ok.  I simplified too much.  To be precise, if a cygwin application is
> invoked from a non-cygwin application then CYGWIN=binmode controls the
> text mode endings of stdin/stdout/stderr.

Right, but the point I had hoped to help clarify with my earlier comments,
since it bit me when first moving to the net release, is that the default
for stdin/stdout/stderr in the net release changed (versus b20.1) to
textmode and not binmode.  So if you don't have CYGWIN set to anything, the
standard handles are textmode in the net releases.

Which is ok - just something I thought helpful to note in the previous
thread about CYGWIN.

-- David

/-----------------------------------------------------------------------\
 \               David Bolen            \   E-mail: db3l@fitlinxx.com  /
  |             FitLinxx, Inc.            \  Phone: (203) 708-5192    |
 /  860 Canal Street, Stamford, CT  06902   \  Fax: (203) 316-5150     \
\-----------------------------------------------------------------------/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: text / binary mounts (sorry)

[Chris Faylor]

On Mon, Jun 05, 2000 at 09:41:38AM -0400, Jason Tishler wrote:
>Since we are discussing the mount command...
>
>Both,
>
>    mount --help
>
>and
>
>    http://sourceware.cygnus.com/cygwin/cygwin-ug-net/using-utils.html#MOUNT
>
>indicate that the '--change-cygdrive-prefix' option can be used with
>the '-s' option.  I assume that this would change the drive prefix on
>a system-wide instead of just a user-wide basis.
>
>Unfortunately, when I try
>
>    mount -b -s --change-cygdrive-prefix /mnt
>
>and look in the registry.  I see that
>
>    HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
>
>changes and that
>
>    HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2
>
>remains unchanged.
>
>Is this a documentation or programming bug?

Dunno.  How about checking out the sources and finding out?

cgf
(Who wonders if this thread will ever die)

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: text / binary mounts (sorry)

[Jason Tishler]

Since we are discussing the mount command...

Both,

    mount --help

and

    http://sourceware.cygnus.com/cygwin/cygwin-ug-net/using-utils.html#MOUNT

indicate that the '--change-cygdrive-prefix' option can be used with
the '-s' option.  I assume that this would change the drive prefix on
a system-wide instead of just a user-wide basis.

Unfortunately, when I try

    mount -b -s --change-cygdrive-prefix /mnt

and look in the registry.  I see that

    HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2

changes and that

    HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2

remains unchanged.

Is this a documentation or programming bug?

Thanks,
Jason

-- 
Jason Tishler
Director, Software Engineering       Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corporation         Fax:   +1 (732) 264-8798
82 Bethany Road, Suite 7             Email: Jason.Tishler@dothill.com
Hazlet, NJ 07730 USA                 WWW:   http://www.dothill.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: text / binary mounts (sorry)

[Chris Faylor]

On Fri, Jun 02, 2000 at 10:45:00PM -0400, David Bolen wrote:
>Chris Faylor [cgf@cygnus.com] writes:
>
>> It only affects stdin/stdout behavior when the program is run from the
>> Windows command shell.
>
>Well, it also happens for me when a process is started up from an NT service
>(that is not a Cygwin service) which has no bearing on a command shell, or
>actually any NT application (even if while the application was started from
>a shell, the process it is creating will have no interaction with that
>shell)  (That might be synonymous with what you mean by "command shell" I'm
>not sure).

Ok.  I simplified too much.  To be precise, if a cygwin application is
invoked from a non-cygwin application then CYGWIN=binmode controls the
text mode endings of stdin/stdout/stderr.

This is to allow some measure of control over what shows up in the file since
there is no way for cygwin to know if stdout refers to a file on a "binmode"
directory or not when it is started from an application that doesn't honor
cygwin's mount tables.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: text / binary mounts (sorry)

[David Bolen]

Chris Faylor [cgf@cygnus.com] writes:

> It only affects stdin/stdout behavior when the program is run from the
> Windows command shell.

Well, it also happens for me when a process is started up from an NT service
(that is not a Cygwin service) which has no bearing on a command shell, or
actually any NT application (even if while the application was started from
a shell, the process it is creating will have no interaction with that
shell)  (That might be synonymous with what you mean by "command shell" I'm
not sure).

> fork() is a cygwin function which produces an additional copy of a running
> program.  That means that the child has a a cygwin parent and so stdin
should
> be in the same state in the child as in the parent.

Oops, I think I mis-stated - I meant to say is started as a child process
(but my Unix-based brain optimized that phrase with "fork()").  I haven't
tested all cases, but the actual problems I was running into did involve a
parent process (not interactive) that was not Cygwin-based.

I do believe you are correct in the behavior under fork() which was actually
part of the confusing part when I tried to diagnose this originally (which
led to my first note to this list which led off onto a tangent on open
source :-)) - I had thought it was the internally forked child but it was
actually the original stdin/stdout .

-- David

/-----------------------------------------------------------------------\
 \               David Bolen            \   E-mail: db3l@fitlinxx.com  /
  |             FitLinxx, Inc.            \  Phone: (203) 708-5192    |
 /  860 Canal Street, Stamford, CT  06902   \  Fax: (203) 316-5150     \
\-----------------------------------------------------------------------/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: text / binary mounts (sorry)

[Chris Faylor]

On Fri, Jun 02, 2000 at 04:41:27PM -0500, Parker, Ron wrote:
>> Since the //h usage is deprecated, I'm not going to worry too 
>> much about this.
>
>The larger point, IMHO, is that, 'echo Hello>//machine/sharename/filename'
>also produces 7 bytes. This leads me to the question of, "How does one
>default UNC file access to binary mode?"  I know it works if the UNC path is
>mounted and you access it via the mount point, but what should happen when
>going directly to the UNC path?

Right now, the same thing happens as has happened for the last three or
four years with cygwin.  It defaults to text mode.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: text / binary mounts (sorry)

[Chris Faylor]

On Fri, Jun 02, 2000 at 05:35:29PM -0400, David Bolen wrote:
>Earnie Boyd [earnie_boyd@yahoo.com] writes:
>>Are you sure of this, Ron?  AFAIK CYGWIN=binmode only affects the pipes
>>and redirection and not file I/O.  BTW CYGWIN=binmode is the default.
>
>One minor caveat with respect to "default" - the default behavior for
>the stdin/stdout handles changed from b20.1 to the net releases,
>dependent on whether you explicitly had the environment variable or
>not.  If you put CYGWIN=binmode in your environment it also affects
>stdin/stdout default behavior, but if you leave the variable out they
>will default to text mode and not binary.

It only affects stdin/stdout behavior when the program is run from the
Windows command shell.

>It's my understanding this was done for some issues with interactive
>tool use, but unfortunately it also comes into play when utilities
>fork() a copy of themselves to process data on stdin/stdout (I ran into
>this with the rsync utility).

I'm not sure how this could be.  Reading the code, I see this line right
before the part that sets the stdin/stdout based on CYGWIN=binmode.

  if (!parent_alive && NOTSTATE(myself, PID_CYGPARENT))

fork() is a cygwin function which produces an additional copy of a running
program.  That means that the child has a a cygwin parent and so stdin should
be in the same state in the child as in the parent.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: text / binary mounts (sorry)

[Norman Vine]

I am using this mount table on Win98
Cygwin V1.1
with cygwin-inst-20000525.tar.gz overlaid

C:\cygwin\bin  /usr/bin  user    binmode
C:\cygwin\lib  /usr/lib  user    binmode
C:\cygwin  /        user    binmode
c:    /c       user    textmode
d:    /d       user    textmode
e:    /e       user    textmode
f:    /f       user    textmode

While compiling gcc complained about an 
obtuse error in <stdlib.h>
which I knew was not the problem

With much head pounding I discovered that a 
previously included file had DOS line endings.

locally supplied
/usr/local/include/GL/gl.h

On a hunch, applying a Dos2Unix filter sent
gcc merrily on it's way.

My question is.
Are we going to have to ensure that all included  files have 
Unix style line endings ??

BTW
Many thanks to all involved with the V1.1 release
Despite it's <new quirks> it seems to be 
a much improved enviroment :-))

Norman Vine


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: text / binary mounts (sorry)

[Parker, Ron]

> Since the //h usage is deprecated, I'm not going to worry too 
> much about this.

The larger point, IMHO, is that, 'echo Hello>//machine/sharename/filename'
also produces 7 bytes. This leads me to the question of, "How does one
default UNC file access to binary mode?"  I know it works if the UNC path is
mounted and you access it via the mount point, but what should happen when
going directly to the UNC path?

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: text / binary mounts (sorry)

[David Bolen]

Earnie Boyd [earnie_boyd@yahoo.com] writes:

> Are you sure of this, Ron?  AFAIK CYGWIN=binmode only affects the pipes
and
> redirection and not file I/O.  BTW CYGWIN=binmode is the default.

One minor caveat with respect to "default" - the default behavior for the
stdin/stdout handles changed from b20.1 to the net releases, dependent on
whether you explicitly had the environment variable or not.  If you put
CYGWIN=binmode in your environment it also affects stdin/stdout default
behavior, but if you leave the variable out they will default to text mode
and not binary.

It's my understanding this was done for some issues with interactive tool
use, but unfortunately it also comes into play when utilities fork() a copy
of themselves to process data on stdin/stdout (I ran into this with the
rsync utility).

The precise "better" default behavior is arguable, but at a minimum it's
just something to be aware of if you are running without CYGWIN=binmode in
your environment.

-- David

/-----------------------------------------------------------------------\
 \               David Bolen            \   E-mail: db3l@fitlinxx.com  /
  |             FitLinxx, Inc.            \  Phone: (203) 708-5192    |
 /  860 Canal Street, Stamford, CT  06902   \  Fax: (203) 316-5150     \
\-----------------------------------------------------------------------/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: text / binary mounts (sorry)

[Chris Faylor]

On Fri, Jun 02, 2000 at 04:14:29PM -0500, Parker, Ron wrote:
>> >So is there anyway to have 'echo Hello>//h/junk' produce a 
>> 6-byte file?
>> 
>> Yes.  You use the mount command that was mentioned previously 
>> in this thread.
>
>If you are referring to 'mount -b --change-cygdrive-prefix /cygdrive', I
>tested it before I sent the original email and again after I recieved your
>response.  Even after doing so,
>	echo Hello>/cygdrive/h/junk	yields 6 bytes
>	echo Hello>//h/junk		yields 7 bytes
>
>If, on the other hand, you are referring to something like 'mount -b H:\\
>//h', it returns without error, nothing shows up in the output from 'mount',
>and I still get a 7 byte file.
>
>I even tried 'mount -b --change-cygdrive-prefix /' to no avail and 'mount -b
>--change-cygdrive-prefix /' gave a "mount failed: Invalid argument" message.
>
>I may just be thick-headed but I didn't get what mount command you were
>referring to.

I was referring to using the --change-cygdrive-prefix option.  I guess I thought
that it would affect the //h usage too.  But apparently it doesn't.

Since the //h usage is deprecated, I'm not going to worry too much about this.

I don't think that you want to change your cygdrive prefix to /.  That is really
not going to do what you want, I suspect.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: text / binary mounts (sorry)

[Parker, Ron]

> I even tried 'mount -b --change-cygdrive-prefix /' to no 
> avail and 'mount -b
> --change-cygdrive-prefix /' gave a "mount failed: Invalid 
                           ^
                     oops: //
> argument" message.

RE: text / binary mounts (sorry)

[Parker, Ron]

> >So is there anyway to have 'echo Hello>//h/junk' produce a 
> 6-byte file?
> 
> Yes.  You use the mount command that was mentioned previously 
> in this thread.

If you are referring to 'mount -b --change-cygdrive-prefix /cygdrive', I
tested it before I sent the original email and again after I recieved your
response.  Even after doing so,
	echo Hello>/cygdrive/h/junk	yields 6 bytes
	echo Hello>//h/junk		yields 7 bytes

If, on the other hand, you are referring to something like 'mount -b H:\\
//h', it returns without error, nothing shows up in the output from 'mount',
and I still get a 7 byte file.

I even tried 'mount -b --change-cygdrive-prefix /' to no avail and 'mount -b
--change-cygdrive-prefix /' gave a "mount failed: Invalid argument" message.

I may just be thick-headed but I didn't get what mount command you were
referring to.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: text / binary mounts (sorry)

[Chris Faylor]

On Fri, Jun 02, 2000 at 04:03:48PM -0500, Jeremy Sheeley wrote:
>
>
>Chris Faylor wrote:
>> 
>> On Fri, Jun 02, 2000 at 11:50:26AM -0700, Bob McGowan wrote:
>> >Is there any way to determine the current status of the
>> >cygdrive-prefix?  I don't see anything in the normal mount output (not
>> >that I would expect to), but there does not appear to be any way to
>> >check this, short of checking the registry.
>> 
>> There is no way to check this via the mount command currently, no.
>> The only method is the registry.
>
>Instead of going into the registry, you could try:
>
>cygpath -u c:
>
>which should give you /cygdrive-prefix/c
>
>I'm probably missing something (I'm still a newbie at cygwin).

That won't tell you if /cygdrive defaults to text or binary, though.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: text / binary mounts (sorry)

[Jeremy Sheeley]

Chris Faylor wrote:
> 
> On Fri, Jun 02, 2000 at 11:50:26AM -0700, Bob McGowan wrote:
> >Is there any way to determine the current status of the
> >cygdrive-prefix?  I don't see anything in the normal mount output (not
> >that I would expect to), but there does not appear to be any way to
> >check this, short of checking the registry.
> 
> There is no way to check this via the mount command currently, no.
> The only method is the registry.

Instead of going into the registry, you could try:

cygpath -u c:

which should give you /cygdrive-prefix/c

I'm probably missing something (I'm still a newbie at cygwin).

-Jeremy

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: text / binary mounts (sorry)

[Chris Faylor]

On Fri, Jun 02, 2000 at 11:50:26AM -0700, Bob McGowan wrote:
>Is there any way to determine the current status of the
>cygdrive-prefix?  I don't see anything in the normal mount output (not
>that I would expect to), but there does not appear to be any way to
>check this, short of checking the registry.

There is no way to check this via the mount command currently, no.
The only method is the registry.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: text / binary mounts (sorry)

[Bob McGowan]

Is there any way to determine the current status of the
cygdrive-prefix?  I don't see anything in the normal mount output (not
that I would expect to), but there does not appear to be any way to
check this, short of checking the registry.

Thanks.

Chris Faylor wrote:
> 
> On Fri, Jun 02, 2000 at 07:59:15PM +0400, Egor Duda wrote:
> >Friday, 02 June, 2000 Earnie Boyd earnie_boyd@yahoo.com wrote:
> >
> >EB> The command `mount --help' might have helped in this instance.
> >
> >EB> mount -b --change-cygdrive-prefix /cygdrive
> >
> >btw,  i think this should go to the FAQ. I've stumbled over this issue
> >myself some time ago :) Since i all my explicit mounts are binary, and
> >CYGWIN=binmode,  i've got a nice surprise when i added new disk (which
> >mounts  as  /cygdrive/h)  and immediately got all those nice text-mode
> >features. it take me to look at the sources to find out what happened.
> 
> I'm always thrilled when people inspect the sources but this is fairly
> well documented in the Cygwin user's guide.
> 
> I'll see about getting it in the FAQ, though.
> 
> cgf
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com

-- 
Bob McGowan
Staff Software Quality Engineer
VERITAS Software
rmcgowan@veritas.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: text / binary mounts (sorry)

[Chris Faylor]

On Fri, Jun 02, 2000 at 07:59:15PM +0400, Egor Duda wrote:
>Friday, 02 June, 2000 Earnie Boyd earnie_boyd@yahoo.com wrote:
>
>EB> The command `mount --help' might have helped in this instance.
>
>EB> mount -b --change-cygdrive-prefix /cygdrive
>
>btw,  i think this should go to the FAQ. I've stumbled over this issue
>myself some time ago :) Since i all my explicit mounts are binary, and
>CYGWIN=binmode,  i've got a nice surprise when i added new disk (which
>mounts  as  /cygdrive/h)  and immediately got all those nice text-mode
>features. it take me to look at the sources to find out what happened.

I'm always thrilled when people inspect the sources but this is fairly
well documented in the Cygwin user's guide.

I'll see about getting it in the FAQ, though.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: text / binary mounts (sorry)

[Parker, Ron]

> > > set CYGWIN=binmode causes even unmounted directories and 
> files to be
> > > accessed in binary mode.  You can set this in autoexec.bat 
> > for Win9x or in
> > > the System Control Panel applet for NT/2000.
> > > 
> > 
> > Are you sure of this, Ron?  AFAIK CYGWIN=binmode only affects 
> > the pipes and
> > redirection and not file I/O.  BTW CYGWIN=binmode is the default.
> 
> ITIWTW, I thought it worked that way, however a quick test 
> shows I am wrong.  I would have sworn CYGWIN=binmode used to 
> apply to all file opens.
> 
> Sorry for the confusion.
> 

So is there anyway to have 'echo Hello>//h/junk' produce a 6-byte file?

RE: text / binary mounts (sorry)

[Parker, Ron]

> > set CYGWIN=binmode causes even unmounted directories and files to be
> > accessed in binary mode.  You can set this in autoexec.bat 
> for Win9x or in
> > the System Control Panel applet for NT/2000.
> > 
> 
> Are you sure of this, Ron?  AFAIK CYGWIN=binmode only affects 
> the pipes and
> redirection and not file I/O.  BTW CYGWIN=binmode is the default.

ITIWTW, I thought it worked that way, however a quick test shows I am wrong.
I would have sworn CYGWIN=binmode used to apply to all file opens.

Sorry for the confusion.

RE: text / binary mounts (sorry)

[Earnie Boyd]

--- "Parker, Ron" <rdparker@butlermfg.com> wrote:
> > BUT is there anything I can setup to make all drives act as 
> > binary mounts
> > automatically. 
> > The problem is that if a drive isn't mounted at all, then I 
> > get dos line
> > feeds at the end of each line.
> 
> set CYGWIN=binmode causes even unmounted directories and files to be
> accessed in binary mode.  You can set this in autoexec.bat for Win9x or in
> the System Control Panel applet for NT/2000.
> 

Are you sure of this, Ron?  AFAIK CYGWIN=binmode only affects the pipes and
redirection and not file I/O.  BTW CYGWIN=binmode is the default.

Cheers,

=====
---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://www.freeyellow.com/members5/gw32/index.html >
           __Minimalist GNU for Windows__
  Mingw32 List: < http://www.egroups.com/group/mingw32/ >
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Yahoo! Photos -- now, 100 FREE prints!
http://photos.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: text / binary mounts (sorry)

[Parker, Ron]

> BUT is there anything I can setup to make all drives act as 
> binary mounts
> automatically. 
> The problem is that if a drive isn't mounted at all, then I 
> get dos line
> feeds at the end of each line.

set CYGWIN=binmode causes even unmounted directories and files to be
accessed in binary mode.  You can set this in autoexec.bat for Win9x or in
the System Control Panel applet for NT/2000.

Re: text / binary mounts (sorry)

[Earnie Boyd]

The command `mount --help' might have helped in this instance.

mount -b --change-cygdrive-prefix /cygdrive


Cheers,
Earnie.
--- Matthew Lowther <m.lowther@standard-platforms.co.uk> wrote:
> 
> Hullo,
> 	I use cygwin (snapshot 05252000) , mainly to access cvs and make, so
> I can build the same source on NT and unix.
> 
> When I check things out in CVS I don't want lots of Dos Line Feeds being
> added.
> This is OK, so long as I mount the relevant drive as a binary mount.
> 
> BUT is there anything I can setup to make all drives act as binary mounts
> automatically. 
> The problem is that if a drive isn't mounted at all, then I get dos line
> feeds at the end of each line.  So people not accustomed to using bash use
> cvs and unknowingly add dos line feeds to all the source files, this gets
> repeated .... and we end up with lots and lots of horrible dos line feed
> characters in all the source.
> 
> Thanks in advance for any help I may get, I'm scared to send this message
> because I know there's been alot of mail about CR/LF issues, but I'm
> desperatley hoping I can stop these ^M's infiltrating our source code.
> 
> 	Maff.
> 
> P.S. Problem description.
> 
> If I run bash and say change to the t drive
> cd t:/
> echo "bob" >fred
> vi fred
> ->produces
> bob^M
> ie. with a dos line feed thing.
> 
> If I do mount -b t: /t
> and do the above, it produces
> bob
> ie. no dos line feed.
> 
> But can I make echo "bob" > fred produce a file fred with no dos line feed
> without having to make sure I've done the mount?
> 
> Attached is the cygcheck thing
> .. <<cygcheck.out>> 
> 
> 
> 
> --
> Matthew Lowther                   Direct Dial: +44 (0)1252 401033
> Software Consultant               Switchboard: +44 (0)1252 401000
> Standard Platforms Limited        Fax        : +44 (0)1252 336934
> http://www.standard-platforms.co.uk        mailto:maff@bssl.co.uk
> 
> 

> ATTACHMENT part 2 application/octet-stream name=cygcheck.out
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com


__________________________________________________
Do You Yahoo!?
Yahoo! Photos -- now, 100 FREE prints!
http://photos.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

text / binary mounts (sorry)

[Matthew Lowther]

[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]

Hullo,
	I use cygwin (snapshot 05252000) , mainly to access cvs and make, so
I can build the same source on NT and unix.

When I check things out in CVS I don't want lots of Dos Line Feeds being
added.
This is OK, so long as I mount the relevant drive as a binary mount.

BUT is there anything I can setup to make all drives act as binary mounts
automatically. 
The problem is that if a drive isn't mounted at all, then I get dos line
feeds at the end of each line.  So people not accustomed to using bash use
cvs and unknowingly add dos line feeds to all the source files, this gets
repeated .... and we end up with lots and lots of horrible dos line feed
characters in all the source.

Thanks in advance for any help I may get, I'm scared to send this message
because I know there's been alot of mail about CR/LF issues, but I'm
desperatley hoping I can stop these ^M's infiltrating our source code.

	Maff.

P.S. Problem description.

If I run bash and say change to the t drive
cd t:/
echo "bob" >fred
vi fred
->produces
bob^M
ie. with a dos line feed thing.

If I do mount -b t: /t
and do the above, it produces
bob
ie. no dos line feed.

But can I make echo "bob" > fred produce a file fred with no dos line feed
without having to make sure I've done the mount?

Attached is the cygcheck thing
. <<cygcheck.out>> 



--
Matthew Lowther                   Direct Dial: +44 (0)1252 401033
Software Consultant               Switchboard: +44 (0)1252 401000
Standard Platforms Limited        Fax        : +44 (0)1252 336934
http://www.standard-platforms.co.uk        mailto:maff@bssl.co.uk


[-- Attachment #2: cygcheck.out --]
[-- Type: text/x-Algol68, Size: 13577 bytes --]


Cygnus Win95/NT Configuration Diagnostics
Current System Time: Thu Jun  1 17:29:41 2000

WinNT Ver 4.0 build 1381 Service Pack 4

Path:	/WINNT/system32
	/WINNT
	/PROGRAM FILES/INFORMIX/BIN
	/bin
	/usr/local/bin
	/tilcon-test
	/mssdk/BIN/WINNT
	/mssdk/BIN
	%PATH%
	/Program Files/DevStudio/sharedide/bin/ide
	/Program Files/devstudio/sharedide/bin
	/Program Files/DevStudio/vc/bin

SysDir: D:\WINNT\System32
WinDir: D:\WINNT

CYGWIN32 = `binmode ntea tty notitle'
PWD = `/usr/local/home/maff'

!EXITCODE = `00000080'
!I: = `I:\'
BACKUPPATH = `D:\WINNT\system32;D:\WINNT;D:\PROGRAM FILES\INFORMIX\BIN;d:\cygnus\cygwin-b20\H-i586-cygwin32\bin;d:\bin;d:\usr\local\bin;d:\usr\X11R6.4\bin;d:\tilcon-test'
BASEMAKE = `d:\mssdk\INCLUDE\BKOFFICE.MAK'
BATCHDIR = `p:\\batch\winnt'
BKOFFICE = `d:\mssdk\'
BLASTER = `A220 I5 D1 T4'
BSS_BIN_DIR = `d:\tilcon-test'
BSS_RUN_DIR = `d:\tilcon-test'
COMPUTERNAME = `KYLE'
COMSPEC = `D:\WINNT\system32\cmd.exe'
CPU = `i386'
DXSDKROOT = `d:\mssdk'
GETPAGEDIR = `p:\\getpage\winnt'
HOMEDRIVE = `I:'
HOMEPATH = `\'
HOMESHARE = `\\rara\homes'
HOSTNAME = `KYLE'
HOSTTYPE = `i586'
INCLUDE = `d:\mssdk\INCLUDE;d:\program files\devstudio\vc\include;d:\program files\devstudio\vc\atl\include;d:\program files\devstudio\vc\mfc\include'
INCLUDEDIR = `t:\build\heywood-project\src\winnt\include'
INETSDK = `d:\mssdk'
INFORMIXDIR = `D:\Informix'
KOFAXDIR = `u:\progra~1\kofax'
LIB = `d:\mssdk\LIB;d:\program files\devstudio\vc\lib;d:\program files\devstudio\vc\mfc\lib'
LIBDIR = `t:\build\heywood-project\src\winnt\lib'
LIBTOOLDIR = `p:\\libtool\winnt'
LOGNAME = `maff'
LOGONSERVER = `\\CARBON'
MACHTYPE = `i586-pc-cygwin32'
MSDEVDIR = `d:\Program Files\DevStudio\SharedIDE'
MSSDK = `d:\mssdk'
MSTOOLS = `d:\mssdk'
NAVINCDIR = `%NAVDIR%\include'
NAVLIBDIR = `%NAVDIR%\lib'
NUMBER_OF_PROCESSORS = `1'
OLDPWD = `/'
OS2LIBPATH = `D:\WINNT\system32\os2\dll;'
OS = `Windows_NT'
OSTYPE = `cygwin32'
PAGEDIR = `p:\\page\winnt'
PATHEXT = `.COM;.EXE;.BAT;.CMD'
PLDBSDIR = `p:\\pldbs\winnt'
PROCESSOR_ARCHITECTURE = `x86'
PROCESSOR_IDENTIFIER = `x86 Family 6 Model 7 Stepping 3, GenuineIntel'
PROCESSOR_LEVEL = `6'
PROCESSOR_REVISION = `0703'
PROMPT = `$P$G'
SHELL = `/bin/sh'
SHLVL = `1'
STSDIR = `p:\\storeserv\winnt'
SYSTEMDRIVE = `D:'
SYSTEMROOT = `D:\WINNT'
TCPKITDIR = `p:\\tcp\win32client\toolkit'
TEMP = `D:\TEMP'
TERM = `cygwin'
TMP = `D:\TEMP'
USERDOMAIN = `BSSL'
USERNAME = `maff'
USERPROFILE = `D:\WINNT\Profiles\maff'
WINDIR = `D:\WINNT'
_ = `/bin/cygcheck'
_SRCDIR_ = `p:\'
TZ = `GMTST0GMTDT-1,M3.5.0/2,M10.5.0/3'

HKEY_CURRENT_USER\Software\Cygnus Solutions
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
  (default) = `/cygdrive'
  cygdrive flags = 0x00000020
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/
  (default) = `d:'
  flags = 0x00000002
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/t
  (default) = `t:'
  flags = 0x00000002
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\00
  (default) = `D:'
  unix = `/'
  fbinary = 0x00000000
  fsilent = 0x00000000
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\01
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\02
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\03
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\04
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\05
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\06
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\07
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\08
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\09
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0A
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0B
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0C
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0D
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0E
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0F
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\10
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\11
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\12
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\13
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\14
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\15
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\16
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\17
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\18
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\19
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\1A
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\1B
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\1C
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\1D
HKEY_CURRENT_USER\Software\Microsoft\Ftp\Accounts\sourceware.cygnus.com
  (default) = `anonymous'
  Login Attributes = 0x00000002
HKEY_CURRENT_USER\Software\Microsoft\Ftp\Accounts\sourceware.cygnus.com\anonymous
  (default) = `'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Installed Components
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Installed Components\D:/
  (default) = `20000517'
  bash = `0002.0004'
  binutils = `19990818.0001'
  bison = `0000'
  byacc = `0000'
  bzip = `0000'
  clear = `0001.0000'
  cygwin = `0001.0001.0001'
  dejagnu = `0000'
  diff = `0000'
  expect = `0000'
  fileutils = `0000'
  findutils = `0000'
  flex = `0000'
  gawk = `0000'
  gcc = `0002.0095.0002.0001'
  gdb = `20000415'
  gperf = `0000'
  grep = `0000'
  groff = `0001.011a.0001'
  gzip = `0000'
  inetutils = `0001.0003.0002.0002'
  less = `0000'
  libpng = `0001.0000.0006.0001'
  login = `0001.0002'
  m = `0000'
  make = `0000'
  man = `0001.005g.0002'
  patch = `0000'
  sed = `0003.0002.0001'
  shellutils = `0000'
  tar = `0000'
  tcltk = `0000'
  termcap = `0002'
  texinfo = `0000'
  textutils = `0000'
  time = `0000'
  zlib = `0001.0001.0003.0001'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\00
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\01
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\02
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\03
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\04
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\05
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\06
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\07
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\08
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\09
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0A
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0B
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0C
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0D
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0E
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0F
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\10
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\11
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\12
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\13
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\14
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\15
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\16
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\17
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\18
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\19
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\1A
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\1B
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\1C
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\1D
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Cygnus Cygwin B20
  (default) = `D:\WINNT\IsUninst.exe -fd:\cygnus\cygwin-b20\Uninst.isu'
  DisplayName = `Cygwin B20'

a:  fd           N/A    N/A                    
c:  hd  FAT     1027Mb  26% CP    UN           
d:  hd  NTFS    5122Mb  79% CP CS UN PA FC     
e:  cd           N/A    N/A                    
f:  net FAT     2047Mb  82% CP    UN           MS-DOS_6
g:  net NTFS    5294Mb  92%          PA        shared
h:  net NTFS   14428Mb 100%          PA        home
i:  net NTFS   14428Mb 100%          PA        maff
j:  net Samba    962Mb  92% CP    UN           home
k:  net NTFS    5122Mb  76% CP CS UN PA FC     
l:  net NTFS     960Mb  81%          PA        work
m:  net NTFS    1780Mb  88% CP CS UN PA FC     NTFS Disk
o:  net NTFS    5294Mb  86%          PA        tpsoft
p:  net NTFS   13878Mb  88%          PA        products
q:  net Samba   1979Mb  97% CP    UN           PRODUCTS
r:  net NTFS    5294Mb  92%          PA        ntdev
s:  net NTFS    3796Mb  91% CP CS UN PA FC     
t:  net NTFS    4094Mb  74% CP CS UN PA FC     
u:  net FAT     2047Mb  36% CP    UN           WIN 95
v:  net NTFS    7993Mb   2% CP CS UN PA FC     cache
w:  net NTFS     960Mb  81%          PA        work
x:  net NTFS    5122Mb  79% CP CS UN PA FC     

d:    /        user    binmode
t:    /t       user    binmode

Found: d:\bin\bash.exe
Found: \bin\bash.exe
Warning: d:\bin\bash.exe hides \bin\bash.exe
Found: d:\bin\cat.exe
Found: \bin\cat.exe
Warning: d:\bin\cat.exe hides \bin\cat.exe
Found: d:\bin\cpp.exe
Found: \bin\cpp.exe
Warning: d:\bin\cpp.exe hides \bin\cpp.exe
Found: d:\bin\find.exe
Found: \bin\find.exe
Warning: d:\bin\find.exe hides \bin\find.exe
Found: d:\bin\gcc.exe
Found: \bin\gcc.exe
Warning: d:\bin\gcc.exe hides \bin\gcc.exe
Found: d:\bin\gdb.exe
Found: \bin\gdb.exe
Warning: d:\bin\gdb.exe hides \bin\gdb.exe
Found: d:\bin\ld.exe
Found: \bin\ld.exe
Warning: d:\bin\ld.exe hides \bin\ld.exe
Found: d:\bin\ls.exe
Found: \bin\ls.exe
Warning: d:\bin\ls.exe hides \bin\ls.exe
Found: d:\bin\make.exe
Found: \bin\make.exe
Warning: d:\bin\make.exe hides \bin\make.exe
Found: d:\bin\sh.exe
Found: \bin\sh.exe
Warning: d:\bin\sh.exe hides \bin\sh.exe

  115k 1999/09/14 d:\bin\cygitcl30.dll - os=4.0 img=1.0 sys=4.0
                  "cygitcl30.dll" v0.0 ts=1999/9/14 3:46
   63k 1999/09/14 d:\bin\cygitk30.dll - os=4.0 img=1.0 sys=4.0
                  "cygitk30.dll" v0.0 ts=1999/9/14 3:47
  474k 1999/09/14 d:\bin\cygtcl80.dll - os=4.0 img=1.0 sys=4.0
                  "cygtcl80.dll" v0.0 ts=1999/9/14 3:31
   19k 1999/09/14 d:\bin\cygtclpip80.dll - os=4.0 img=1.0 sys=4.0
   24k 1999/09/14 d:\bin\cygtclreg80.dll - os=4.0 img=1.0 sys=4.0
                  "cygtclreg80.dll" v0.0 ts=1999/9/14 3:31
  768k 1999/09/14 d:\bin\cygtk80.dll - os=4.0 img=1.0 sys=4.0
                  "cygtk80.dll" v0.0 ts=1999/9/14 3:36
  569k 2000/05/15 d:\bin\cygwin.presnapshot.dll - os=4.0 img=1.0 sys=4.0
                  "cygwin1.dll" v0.0 ts=2000/5/15 4:48
  604k 2000/06/01 d:\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
                  "cygwin1.dll" v0.0 ts=2000/5/26 8:29
  115k 1999/09/14 \bin\cygitcl30.dll - os=4.0 img=1.0 sys=4.0
                  "cygitcl30.dll" v0.0 ts=1999/9/14 3:46
   63k 1999/09/14 \bin\cygitk30.dll - os=4.0 img=1.0 sys=4.0
                  "cygitk30.dll" v0.0 ts=1999/9/14 3:47
  474k 1999/09/14 \bin\cygtcl80.dll - os=4.0 img=1.0 sys=4.0
                  "cygtcl80.dll" v0.0 ts=1999/9/14 3:31
   19k 1999/09/14 \bin\cygtclpip80.dll - os=4.0 img=1.0 sys=4.0
   24k 1999/09/14 \bin\cygtclreg80.dll - os=4.0 img=1.0 sys=4.0
                  "cygtclreg80.dll" v0.0 ts=1999/9/14 3:31
  768k 1999/09/14 \bin\cygtk80.dll - os=4.0 img=1.0 sys=4.0
                  "cygtk80.dll" v0.0 ts=1999/9/14 3:36
  569k 2000/05/15 \bin\cygwin.presnapshot.dll - os=4.0 img=1.0 sys=4.0
                  "cygwin1.dll" v0.0 ts=2000/5/15 4:48
  604k 2000/06/01 \bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
                  "cygwin1.dll" v0.0 ts=2000/5/26 8:29
Use -h to see help about each section