public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@cygnus.com>
To: cygwin@sourceware.cygnus.com
Subject: Re: strange mount behaviour...
Date: Wed, 24 Feb 1999 11:49:00 -0000	[thread overview]
Message-ID: <19990224144437.B26668@cygnus.com> (raw)
In-Reply-To: < 19990224144809.15898.rocketmail@send105.yahoomail.com >; from Earnie Boyd on Wed, Feb 24, 1999 at 06:48:09AM -0800

On Wed, Feb 24, 1999 at 06:48:09AM -0800, Earnie Boyd wrote:
>---Sebastien Barre <Sebastien.Barre@utc.fr> wrote:
>8<
>> Could anyone explain me why mounting D: ou D:/ ou d:/ to /d produce
>these
>> artefacts ? Doing the same thing with C: ou E: will NOT cause any
>problem.
>> Is it impossible to mount the drive where cygwin is located ?
>Installing
>> coolview did not help too. As well as binary mount.
>8<
>
>This is a known bug with the mount filesystem emulation and relative
>paths.  When you do `ls d' you are actually displaying the contents of
>the mount point directory which is empty even on UNIX.  When you do
>`ls /d' the emulation resolves correctly and you see the contents of d:.
>
>This may have been fixed in recent snapshots.  I know that Geoff Noer
>reworked the code for the mounted directories.  Caution, using
>snapshots may cause other problems as snapshots aren't tested.  Please
>read the change log to find out what has changed.

I don't think this has been fixed, actually.

Corrinna submitted a patch that deleted about fifteen lines of code and
caused the correct behavior to miraculously appear but I've been sort of
nervous about applying the patch because I'm not sure what other
ramifications there may be.

cgf

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

WARNING: multiple messages have this Message-ID
From: Christopher Faylor <cgf@cygnus.com>
To: cygwin@sourceware.cygnus.com
Subject: Re: strange mount behaviour...
Date: Sun, 28 Feb 1999 23:02:00 -0000	[thread overview]
Message-ID: <19990224144437.B26668@cygnus.com> (raw)
Message-ID: <19990228230200.Z8L21fRuNKvQh7H70r43ryeOS5pJ0e1DcmE9-Xc3Hps@z> (raw)
In-Reply-To: <19990224144809.15898.rocketmail@send105.yahoomail.com>

On Wed, Feb 24, 1999 at 06:48:09AM -0800, Earnie Boyd wrote:
>---Sebastien Barre <Sebastien.Barre@utc.fr> wrote:
>8<
>> Could anyone explain me why mounting D: ou D:/ ou d:/ to /d produce
>these
>> artefacts ? Doing the same thing with C: ou E: will NOT cause any
>problem.
>> Is it impossible to mount the drive where cygwin is located ?
>Installing
>> coolview did not help too. As well as binary mount.
>8<
>
>This is a known bug with the mount filesystem emulation and relative
>paths.  When you do `ls d' you are actually displaying the contents of
>the mount point directory which is empty even on UNIX.  When you do
>`ls /d' the emulation resolves correctly and you see the contents of d:.
>
>This may have been fixed in recent snapshots.  I know that Geoff Noer
>reworked the code for the mounted directories.  Caution, using
>snapshots may cause other problems as snapshots aren't tested.  Please
>read the change log to find out what has changed.

I don't think this has been fixed, actually.

Corrinna submitted a patch that deleted about fifteen lines of code and
caused the correct behavior to miraculously appear but I've been sort of
nervous about applying the patch because I'm not sure what other
ramifications there may be.

cgf

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


  parent reply	other threads:[~1999-02-24 11:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-24  6:48 Earnie Boyd
     [not found] ` < 19990224144809.15898.rocketmail@send105.yahoomail.com >
1999-02-24 11:49   ` Christopher Faylor [this message]
1999-02-25 13:54     ` Corinna Vinschen
1999-02-28 23:02       ` Corinna Vinschen
1999-02-28 23:02     ` Christopher Faylor
1999-02-28 23:02 ` Earnie Boyd
  -- strict thread matches above, loose matches on Subject: below --
1999-03-04  5:56 Earnie Boyd
     [not found] ` < 19990304135705.27427.rocketmail@send103.yahoomail.com >
1999-03-04  8:10   ` Chris Faylor
1999-03-31 19:45     ` Chris Faylor
1999-03-04 15:14   ` Michael Hirmke
1999-03-31 19:45     ` Michael Hirmke
1999-03-31 19:45 ` Earnie Boyd
     [not found] <Sebastien>
     [not found] ` <Barre's>
     [not found]   ` <message>
     [not found]     ` <of>
     [not found]       ` <"Wed,>
     [not found]         ` <24>
     [not found]           ` <Feb>
     [not found]             ` <1999>
     [not found]               ` <02:14:52>
     [not found]                 ` <+0100>
1999-02-23 17:15                   ` Sebastien Barre
1999-02-24  0:08                     ` Levon Saldamli
     [not found]                       ` < 7wsobw8gql.fsf@sandra.lysator.liu.se >
1999-02-24  0:59                         ` Sebastien Barre
1999-02-28 23:02                           ` Sebastien Barre
1999-02-28 23:02                       ` Levon Saldamli
1999-03-03 13:25                       ` Michael Hirmke
1999-03-31 19:45                         ` Michael Hirmke
1999-02-28 23:02                     ` Sebastien Barre

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=19990224144437.B26668@cygnus.com \
    --to=cgf@cygnus.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).