jaka kranjc wrote:
> From: [EMAIL PROTECTED]
> To: bug-bash@gnu.org
> Subject: Moving $PWD into restricted areas causes trouble with su
>
> Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -
> DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
> -DCONF_VENDOR='pc'
> -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -O2 -march=athlon-xp -
> fomit-frame-pointer
> uname output: Linux lynxlynxsp 2.6.11-gentoo-r6 #1 Thu Apr 14 08:07:59 CEST
> 2005
> i686 AMD Athlon(tm) XP 1700+ AuthenticAMD GNU/Linux
> Machine Type: i686-pc-linux-gnu
>
> Bash Version: 2.05b
> Patch Level: 0
> Release Status: release
>
> Description:
> The example is clear enough, I hope. When you su from a
> non-exsisting folder, the result is not "optimal". I'm not sure
> if this is the
> right place - should I've sent this to the su buglist?
What is the `optimal' behavior? The current directory doesn't
exist, and the shell is printing an error message to that effect.
Since `cd' depends on $PWD to construct the new pathname, it
will generate an error also.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
Live...Laugh...Love
Chet Ramey, ITS, CWRU [EMAIL PROTECTED] http://cnswww.cns.cwru.edu/~chet/
_______________________________________________
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
