From: Bob McGowan <rmcgowan@veritas.com>
To: cygwin@sourceware.cygnus.com
Subject: Re: text / binary mounts (sorry)
Date: Fri, 02 Jun 2000 11:50:00 -0000 [thread overview]
Message-ID: <393801F2.491087D5@veritas.com> (raw)
In-Reply-To: <20000602142612.F1589@cygnus.com>
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
next prev parent reply other threads:[~2000-06-02 11:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-02 6:35 Earnie Boyd
2000-06-02 9:02 ` Re[2]: " Egor Duda
2000-06-02 11:26 ` Chris Faylor
2000-06-02 11:50 ` Bob McGowan [this message]
2000-06-02 13:16 ` Chris Faylor
2000-06-02 14:03 ` Jeremy Sheeley
2000-06-02 14:05 ` Chris Faylor
2000-06-05 6:41 ` Jason Tishler
2000-06-05 8:48 ` Chris Faylor
-- strict thread matches above, loose matches on Subject: below --
2000-06-05 9:41 David Bolen
2000-06-02 19:45 David Bolen
2000-06-02 19:50 ` Chris Faylor
[not found] <200006022142.OAA26463@cygnus.com>
2000-06-02 19:33 ` Chris Faylor
2000-06-02 14:42 Parker, Ron
2000-06-02 14:36 David Bolen
2000-06-02 19:33 ` Chris Faylor
[not found] <200006022116.OAA23714@cygnus.com>
2000-06-02 14:29 ` Chris Faylor
2000-06-02 14:53 ` Norman Vine
2000-06-02 14:26 Parker, Ron
2000-06-02 14:16 Parker, Ron
[not found] <200006021734.KAA06876@cygnus.com>
2000-06-02 11:28 ` Chris Faylor
2000-06-02 10:33 Parker, Ron
2000-06-02 10:26 Parker, Ron
2000-06-02 10:13 Earnie Boyd
2000-06-02 10:01 Parker, Ron
2000-06-02 1:01 Matthew Lowther
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=393801F2.491087D5@veritas.com \
--to=rmcgowan@veritas.com \
--cc=cygwin@sourceware.cygnus.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).