From: random832@fastmail.com (Random832)
Subject: [TUHS] Device special files
Date: Tue, 06 Feb 2018 14:48:19 -0500 [thread overview]
Message-ID: <1517946499.3717582.1261737872.3DC598F2@webmail.messagingengine.com> (raw)
In-Reply-To: <CAP6exYLTp1bOBAaewKuv0VGTAckvR86bjROUic10u64rd3u+DA@mail.gmail.com>
On Tue, Feb 6, 2018, at 10:56, ron minnich wrote:
> these were in by the time I can along but I was wondering when they got it.
>
> They've also always felt a bit like a thing that did not fit to me. I'm
> pretty sure I was not alone, given that the Unix authors worked out a way
> to get rid of them in later efforts. I know what came after, in Plan 9;
> what came before, in Unix, that led to special files?
V3 and earlier still *called* them special files, but it seems they were essentially just magic inode numbers (there was no physical file on disk, just any directory entry with the given inode would be the special file).
http://minnie.tuhs.org/cgi-bin/utree.pl?file=V3/man/man5/fs.5
next prev parent reply other threads:[~2018-02-06 19:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 15:56 ron minnich
2018-02-06 17:56 ` Larry McVoy
2018-02-06 18:03 ` ron minnich
2018-02-06 19:48 ` Random832 [this message]
2018-02-07 1:25 ` Greg 'groggy' Lehey
2018-02-07 1:36 ` Ron Natalie
2018-02-07 1:40 ` Clem Cole
2018-02-07 1:47 ` Henry Bent
2018-02-07 1:48 ` Dave Horsfall
2018-02-07 2:06 ` Dan Cross
2018-02-07 16:24 ` Arthur Krewat
2018-02-07 16:34 ` Dan Cross
2018-02-07 16:34 ` Nemo
2018-02-07 16:59 ` ron minnich
2018-02-08 0:39 ` Dave Horsfall
2018-02-08 16:18 ` Arthur Krewat
2018-02-08 22:47 ` Dave Horsfall
2018-02-07 2:13 ` Bakul Shah
2018-02-07 5:39 ` Dave Horsfall
2018-02-07 18:36 ` Steffen Nurpmeso
2018-02-07 19:07 ` Ian Zimmerman
2018-02-07 22:05 ` Clem Cole
2018-02-07 22:38 ` ron minnich
2018-02-07 22:48 ` Ron Natalie
2018-02-08 18:59 ` Random832
2018-02-07 23:06 ` Bakul Shah
2018-02-08 19:06 ` Steffen Nurpmeso
2018-02-07 22:04 ` Dave Horsfall
2018-02-08 13:03 ` Rafael R Obelheiro
2018-02-08 19:25 ` Steffen Nurpmeso
2018-02-07 1:38 Noel Chiappa
2018-02-09 0:09 Doug McIlroy
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=1517946499.3717582.1261737872.3DC598F2@webmail.messagingengine.com \
--to=random832@fastmail.com \
/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).