From: Corinna Vinschen <corinna@vinschen.de>
To: cygwin@sourceware.cygnus.com
Subject: Re: New install problems
Date: Fri, 31 Dec 1999 13:28:00 -0000 [thread overview]
Message-ID: <3846D857.78A66799@vinschen.de> (raw)
Message-ID: <19991231132800.Vy14bh4CyI2JSDnsNu5J2Bu1D9YZ42u3g_IGK3Ssy7U@z> (raw)
In-Reply-To: <19991202115637.A1456@cygnus.com>
Chris Faylor wrote:
>
> On Thu, Dec 02, 1999 at 08:09:08AM -0800, Earnie Boyd wrote:
> >--- Chris Faylor <cgf@cygnus.com> wrote:
> >-8<-
> >>
> >> In Cygwin v1.0 (only available on CD, currently <but I'm working on that>)
> >> mount has a "-f" option to force a mount, so you can do this, too:
> >>
> >> mount -f d:\unix /
> >
> >Would that not have to be `mount -f d:\\unix /' if executed in bash? or
> >alternatively `mount -f 'd:\unix' /'?
>
> Yes, but I would suggest that this not be run under bash. It will probably
> work best if you do this standalone.
BTW:
Forward slash works for the native path as well:
mount -f d:/unix /
This is nice for native device paths:
mount -f //./tape0 /dev/st0
instead of
mount -f \\\\.\\tape0
and this works in bash (ash, tcsh, ksh, zsh...), too, if you call mount
with correct path.
Corinna
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-12-31 13:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-02 8:22 Earnie Boyd
1999-12-02 8:56 ` Chris Faylor
1999-12-02 12:37 ` Corinna Vinschen [this message]
1999-12-02 12:48 ` Chris Faylor
1999-12-31 13:28 ` Chris Faylor
1999-12-31 13:28 ` Corinna Vinschen
1999-12-31 13:28 ` Chris Faylor
1999-12-31 13:28 ` Earnie Boyd
-- strict thread matches above, loose matches on Subject: below --
1999-12-02 8:46 New Install Problems Timothy I. McGinnis
1999-12-31 13:28 ` Timothy I. McGinnis
1999-12-02 6:18 New install problems Earnie Boyd
1999-12-02 7:48 ` Chris Faylor
1999-12-31 13:28 ` Chris Faylor
1999-12-31 13:28 ` Earnie Boyd
1999-12-02 5:56 Timothy I. McGinnis
1999-12-04 3:05 ` Michael Hirmke
1999-12-31 13:28 ` Michael Hirmke
1999-12-31 13:28 ` Timothy I. McGinnis
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=3846D857.78A66799@vinschen.de \
--to=corinna@vinschen.de \
--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).