From: bakul@bitblocks.com (Bakul Shah)
Subject: [TUHS] Device special files
Date: Wed, 07 Feb 2018 15:06:24 -0800 [thread overview]
Message-ID: <20180207230639.3EE6C156E813@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Wed, 07 Feb 2018 17:05:05 -0500." <CAC20D2MLBnHq0nQnrec+-tLuCOhMXQdLNZvwfEd79nPnSxsQ9g@mail.gmail.com>
On Wed, 07 Feb 2018 17:05:05 -0500 Clem Cole <clemc at ccc.com> wrote:
>
> One of the lines I have had about UNIX development is the number if
> namespaces its has. If you try to develop something like Single System
> Image Clusters (check out OpenSSI.org) you'll hit all of the namespaces.
>
> Let me see how many I can remember quickly..
>
> 1. file system
> 2. per device inumbers for storage
> 3. device major numbers
> 4. per device minor numbers
> 5. pid
> 6. gid
> 7. sockets
> 8. port numbers within sockets per protocol
> 9. system V semaphores
> 10. system V shared memory
Most all of these are intrinsic or unavoidable. You can use
strings instead of table indices but still the same. And some
of these have sub-namespaces. This is why plan9's mountable
namespaces is such a neat solution. Too bad Unix just stole
/proc & /dev/fd.... And this can be added
devfs is too big a sledgehammer (+ it needs /etc/devfs.conf
for permissions and ownership using its own DSL). For example,
names of devices not accessible in a jail still show up there.
next prev parent reply other threads:[~2018-02-07 23:06 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
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 [this message]
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=20180207230639.3EE6C156E813@mail.bitblocks.com \
--to=bakul@bitblocks.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).