scsh-users
[Top] [All Lists]

Re: scsh mis-interacting with FreeBSD procfs??

To: "Daniel Ortmann" <ortmann@vnet.ibm.com>
Subject: Re: scsh mis-interacting with FreeBSD procfs??
From: Steven Jenkins <sjenkins@ms.com>
Date: Tue, 01 Apr 1997 09:36:00 -0500
Cc: scsh-bugs@martigny.ai.mit.edu
Try:
(run (/bin/ls -l /proc/curproc/file))

scsh has a different syntax from what you are expecting.  I believe
the first few sections of the users manual talk about this vaguely, but
that the details are buried in later sections.

In short: scsh was trying to find an executable "/bin/ls -l /proc/curproc/file"
but you meant: call /bin/ls with args of "-l" and "/proc/curproc/file",
which would be 
(run ("/bin/ls" "-l" "exec"))
except for the slick special evaluation that lets us do what I first
suggested.

>(note: this could be due merely to my own 'newbie' user ignorance.) 
>
>Problem: 
>(run ("/bin/ls -l /proc/curproc/file")) appears to fail on FreeBSD with
>/proc being the mount point for the procfs filesystem.  ('curproc' is a
>'link' to the current process number and 'file' is the current load
>image.)  The process number that is printed was completely wrong ... and
>failed. 
>
>Expected: 
>The size of /proc/curproc/file should have been displayed. 
>
>Caveat: 
>I don't know whether this is a problem with scsh, the scshvm, procfs, or
>some combination.  Let me know what you think and I'll try to follow up
>with the appropriate people. 
>
>Daniel Ortmann, Circuit Technology  
>ortmann@vnet.ibm.com or ortmann@rchland  
>HEC/040-2, IBM Rochester, MN  55901-7829 
>507.253.6795, (T/L)8.553.6795 

Steven L. Jenkins

<Prev in Thread] Current Thread [Next in Thread>