From: Derek Fawcus <dfawcus+lists-tuhs@employees.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] 8th Edition and /dev/stdio
Date: Mon, 20 Apr 2020 19:17:13 +0100 [thread overview]
Message-ID: <20200420181713.GB51234@clarinet.employees.org> (raw)
In-Reply-To: <202004201428.03KESrgI032002@freefriends.org>
On Mon, Apr 20, 2020 at 08:28:53AM -0600, arnold@skeeve.com wrote:
> See if there are man pages for /dev/fd/XXX. IIRC /dev/stdin was
> a symlink to /dev/fd/0, /dev/stdout to /dev/fd/1, /dev/stderr to /dev/fd/2,
> and, as a really nice generalization, /dev/tty to /dev/fd/4. For the
> latter, init(1) simply dup'ed the opened tty file descriptor one more
> time before exec-ing login.
So what happened to /dev/fd/3 ?
DF
next prev parent reply other threads:[~2020-04-20 18:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 13:59 Paul Ruizendaal
2020-04-20 14:28 ` arnold
2020-04-20 15:01 ` Paul Ruizendaal
2020-04-20 15:16 ` arnold
2020-04-20 17:58 ` Paul Ruizendaal
2020-04-20 18:17 ` Derek Fawcus [this message]
2020-04-20 18:32 ` arnold
2020-04-22 9:21 ` Rob Pike
2020-04-22 9:33 ` arnold
2020-04-22 9:35 ` Steve Nickolas
2020-04-22 9:41 ` Rob Pike
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200420181713.GB51234@clarinet.employees.org \
--to=dfawcus+lists-tuhs@employees.org \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).