Path: utzoo!attcan!uunet!cs.utexas.edu!jsq
From: seanf@sco.COM (Sean Fagan)
Newsgroups: comp.std.unix
Subject: Re: File system name space
Message-ID: <14101@cs.utexas.edu>
Date: 29 Oct 90 06:09:08 GMT
References: <13878@cs.utexas.edu> <14014@cs.utexas.edu>
Sender: jsq@cs.utexas.edu
Reply-To: seanf@sco.COM (Sean Fagan)
Organization: The Santa Cruz Operation, Inc.
Lines: 32
Approved: jsq@cs.utexas.edu (Moderator, John S. Quarterman)
X-Submissions: std-unix@uunet.uu.net

Submitted-by: seanf@sco.COM (Sean Fagan)

In article <14014@cs.utexas.edu> addw@phcomp.co.uk (Alain Williams) writes:
>What happens if you do an ``ls -l'' on /dev/fd, do you see the fds which are
>open to the ls program or all possible fds, even those which aren't opened ?

You get something that looks like

kithrup 10> ls -l /dev/fd
total 0
crw-rw-rw- 5 bin	bin	46,0	Jun 11 15:48 0
crw-rw-rw- 5 bin	bin	46,1	Jun 11 15:48 1
crw-rw-rw- 2 bin	bin	46,2	Jun 11 15:48 2
crw-rw-rw- 1 bin	bin	46,3	Jun 11 15:48 3
crw-rw-rw- 1 bin	bin	46,4	Jun 11 15:48 4
crw-rw-rw- 1 bin	bin	46,5	Jun 11 15:48 5

And so on.  They are normal device drivers; stat'ing them doesn't do
anything strange, just opening them.

(/dev/stdin.o, /dev/stdin.s, /dev/stdin.c, /dev/stdin, and /dev/fd/0 are all
linked on my system; similarly with /dev/stdout.  /dev/stderr is linked to
/dev/fd/0, and all the others [through 60 on my system] only have one link.)

-- 
-----------------+
Sean Eric Fagan  | "Quoth the raven,"
seanf@sco.COM    | "Eat my shorts!"
uunet!sco!seanf  |     -- Lisa and Bart Simpson
(408) 458-1422   | Any opinions expressed are my own, not my employers'.

Volume-Number: Volume 22, Number 6