procfs(5) or pwd(1) bug

[Rostislav Krasny]

--- Rostislav Krasny <rosti_bsd at yahoo.com> wrote:
> Hello.
> 
> I've found a strange behavior of pwd(1) on procfs(5). See following log:
> 
> # uname -a
> FreeBSD vega 5.3-BETA6 FreeBSD 5.3-BETA6 #0: Sat Sep 25 19:41:14 UTC 2004
>  
>   root at wv1u.samsco.home:/usr/obj/usr/src/sys/GENERIC  i386
> vega# mount_procfs . /proc
> vega# cd /proc
> vega# ls
> 0       12      16      21      26      32      367     401     439    
> 45 
>     797
> 1       1244    17      22      27      325     37      41      44     
> 46 
>     8
> 10      1245    172     23      28      33      379     42      440    
> 47 
>     801
> 1012    13      18      230     29      34      38      425     441     5
>  
>     9
> 1013    1366    19      24      3       35      39      43      442     6
>  
>     curproc
> 1014    14      2       25      30      36      4       437     443     7
> 11      15      20      250     31      363     40      438     444    
> 794
> vega# pwd
> /proc
> vega# cd 440
> vega# pwd
> pwd: .: No such file or directory
> vega# pwd -L
> /proc/440
> vega# pwd
> /proc/440
> vega# cd ..
> vega# pwd
> /proc
> vega# cd 440
> vega# pwd
> pwd: .: No such file or directory
> vega# pwd -P
> pwd: .: No such file or directory
> vega# pwd
> pwd: .: No such file or directory
> vega# pwd -L
> /proc/440
> vega# pwd
> /proc/440
> vega# pwd -P
> /proc/440

I've just found that if the shell is sh(1) then there is no such a problem.


		
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail