From: Rob Pike <robpike@gmail.com>
To: Aharon Robbins <arnold@skeeve.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] 8th Edition and /dev/stdio
Date: Wed, 22 Apr 2020 19:21:09 +1000 [thread overview]
Message-ID: <CAKzdPgxVDVmCPiULT9osTFJQjMqSBWvP9HLZAw+_0DxBAfaddQ@mail.gmail.com> (raw)
In-Reply-To: <202004201832.03KIWWeJ008975@freefriends.org>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
I think dmr put them in, at my suggestion. I was bothered by the
inconsistent use of '-' as a name for standard input. Giving stdin a real
name meant we had a consistent mechanism.
8th edition sounds right.
-rob
On Tue, Apr 21, 2020 at 4:33 AM <arnold@skeeve.com> wrote:
> Derek Fawcus <dfawcus+lists-tuhs@employees.org> wrote:
>
> > 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
>
> My bad. I meant /dev/fd/3. What was cute was that /dev/tty was
> no longer a special device of it's own, but just another inherited
> open file descriptor.
>
> Sadly, that generalization never made it out into other *nix systems.
>
> Arnold
>
[-- Attachment #2: Type: text/html, Size: 1649 bytes --]
next prev parent reply other threads:[~2020-04-22 9:21 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
2020-04-20 18:32 ` arnold
2020-04-22 9:21 ` Rob Pike [this message]
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=CAKzdPgxVDVmCPiULT9osTFJQjMqSBWvP9HLZAw+_0DxBAfaddQ@mail.gmail.com \
--to=robpike@gmail.com \
--cc=arnold@skeeve.com \
--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).