rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Tom Culliton <culliton@clark.net>
To: rc@hawkwind.utcs.toronto.edu
Subject: /dev/fd -> /proc/self/fd
Date: Thu, 6 Mar 1997 21:02:32 -0500	[thread overview]
Message-ID: <199703070202.VAA24056@explorer2.clark.net> (raw)

I seem to have lost the message that someone recently sent about doing
this, can someone give me a clue?  Someone who saved the message?
Someone who has done it?  Whoever sent the original message?  I swear
I'm not hallucinating, although maybe it was on a different mailing
list or news group...

Failing that, what is the behaviour of /dev/fd?  Is it a directory
that "magically" contains numeric filenames corresponding to the
reading processes open fd's like /proc/self/fd?  Somebody had to
understand this to implement the original code. ;-)

BTW - Chris, where are the mailing list archives these days?



             reply	other threads:[~1997-03-07  2:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-03-07  2:02 Tom Culliton [this message]
1997-03-07  2:42 Tom Culliton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199703070202.VAA24056@explorer2.clark.net \
    --to=culliton@clark.net \
    --cc=rc@hawkwind.utcs.toronto.edu \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).