From: cgf AT cygnus DOT com (Christopher Faylor) Subject: Re: BUG: mount point/mount errors in B19 and B20 alphas 18 Oct 1998 12:01:43 -0700 Message-ID: <19981018143312.A17756.cygnus.cygwin32.developers@cygnus.com> References: <19981018041035 DOT 6085 DOT qmail AT hotmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: Corinna Vinschen , Ron Parker , cygwin32-developers AT cygnus DOT com On Sun, Oct 18, 1998 at 12:48:57PM +0200, Corinna Vinschen wrote: >Ron Parker wrote: >> >> I have D:\unix mounted as root the directory /usr exists and D:\usr is >> mounted as /usr. If archive.tar contains usr/file.txt, when I "cd /" >> and "tar xf archive.tar" then file.txt is extracted to D:\unix\usr not >> D:\usr. This is the mount point not the mount. >> >> This occurs with B19 and the B20 alphas. >> >> I cannot currently investigate this, but I thought it should be >> reported. > >Imagine same directory structure. Additionally, for nicer effect, >in /usr exists a symlink named `X11', which points to /usr/X11R6.3: > > bash$ cd /usr; ls > X11 X11R6.3 bin include lib local > >Ok, now, if a directory `usr' in the root mount exists: > > bash$ cd /; cd usr; ls > ls: X11: No such file or directory > X11 X11R6.3 bin include lib local > > bash$ cd /; ls usr > > ^^^ > nothing! > >or, if no such directory `usr' exists: > > bash$ cd /; cd usr; ls > usr: No such file or directory > > bash$ cd /; ls usr > ls: usr: No such file or directory I think we can all generate failing scenarios. This particular problem has been in cygwin for some time. If anyone wants to submit a patch we'd welcome including it in b20. -- cgf AT cygnus DOT com http://www.cygnus.com/