File system name space
Sean Fagan
seanf at sco.COM
Mon Oct 29 17:09:08 AEST 1990
Submitted-by: seanf at sco.COM (Sean Fagan)
In article <14014 at cs.utexas.edu> addw at 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 at 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
More information about the Comp.std.unix
mailing list