Re: Unable to access forced mounts from /bin/sh

2005-12-25 Thread Eric Blake
> > I've uploaded a test version of bash, 3.0-12, that changes the behavior of > > cd to use realpath() for -P, and to only check existance of the entire > > path (rather than all intermediates) for -L, so that you should be able to > > cd /a/b even in POSIX mode when /a doesn't exist but /a/b is a

Re: Unable to access forced mounts from /bin/sh

2005-12-25 Thread Scott Perlman
Eric Blake byu.net> writes: > I've uploaded a test version of bash, 3.0-12, that changes the behavior of > cd to use realpath() for -P, and to only check existance of the entire > path (rather than all intermediates) for -L, so that you should be able to > cd /a/b even in POSIX mode when /a doesn

Re: Unable to access forced mounts from /bin/sh

2005-08-30 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 8/24/2005 7:03 AM: > > Sure enough, on 'cd -L', bash always checks for the existance of the > entire path, then checks for posixly_correct, then tries chdir(); so bash > succeeds where sh fails when an intermediate path name

Re: Unable to access forced mounts from /bin/sh

2005-08-24 Thread Christopher Faylor
On Wed, Aug 24, 2005 at 07:03:21AM -0600, Eric Blake wrote: >According to Eric Blake on 8/22/2005 6:09 AM: Huh? Strace shows that sh fails when trying to stat /a. Does this, perhaps, have something to do with bash switching to POSIX mode when invoked as "sh"? >> >> Yes it does. I'll

Re: Unable to access forced mounts from /bin/sh

2005-08-24 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 8/22/2005 6:09 AM: >>>Huh? Strace shows that sh fails when trying to stat /a. Does this, >>>perhaps, have something to do with bash switching to POSIX mode when >>>invoked as "sh"? > > Yes it does. I'll have to look into

Re: Unable to access forced mounts from /bin/sh

2005-08-23 Thread Yitzchak Scott-Thoennes
On Mon, Aug 22, 2005 at 06:09:37AM -0600, Eric Blake wrote: > On the other hand, what if the user does: > $ mkdir /a > $ mount -u -f c: /a/b > $ rmdir /a > > This will take some thought and planning for cygwin1.dll and mount(1) to > get sane behavior in all cases. Maybe the best solution for this

Re: Unable to access forced mounts from /bin/sh

2005-08-22 Thread Igor Pechtchanski
On Mon, 22 Aug 2005, Eric Blake wrote: > According to Igor Pechtchanski on 8/20/2005 11:57 PM: > > Here's something weird. I don't know whether this is a problem with the > > latest Cygwin, or bash: > > I don't know if 2-level forced directories would/should ever work. If /a > doesn't exist, the

Re: Unable to access forced mounts from /bin/sh

2005-08-22 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Igor Pechtchanski on 8/20/2005 11:57 PM: > Here's something weird. I don't know whether this is a problem with the > latest Cygwin, or bash: I don't know if 2-level forced directories would/should ever work. If /a doesn't exist, then sh

Unable to access forced mounts from /bin/sh

2005-08-20 Thread Igor Pechtchanski
Here's something weird. I don't know whether this is a problem with the latest Cygwin, or bash: $ /bin/mount -f -u c:/ /a/b $ /bin/sh -c 'cd /a/b && /bin/ls | head -1' sh: line 0: cd: /a/b: No such file or directory $ /bin/bash -c 'cd /a/b && /bin/ls | head -1' AUTOEXEC.BAT $ Some system info: