The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Device special files
Date: Wed, 7 Feb 2018 17:05:05 -0500	[thread overview]
Message-ID: <CAC20D2MLBnHq0nQnrec+-tLuCOhMXQdLNZvwfEd79nPnSxsQ9g@mail.gmail.com> (raw)
In-Reply-To: <20180207190759.7sjrf6ta4m7sct3d@matica.foolinux.mooo.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]

On Wed, Feb 7, 2018 at 2:07 PM, Ian Zimmerman <itz at very.loosely.org> wrote:

>
>
> The real problem with static /dev is on the development side IMO -
> managing the namespace of device names and major/minor numbers.

​And that is the issue I think that Ron is reacting too.

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​


I'll stop here, you get the idea...

Ron is right managing the major/minor number externally which have internal
meaning to the kernel can be quite an issue.   Although, in fairness, it
has worked amazing well for over 40 years.  It was a simple solution and
did not take take up a lot of space in the kernel to implement.  I'm not
sure for the PDP-11, I would have wanted much more.   One might suggest it
was pretty damned elegant for the time.

Clem
ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180207/f48125ec/attachment-0001.html>


  reply	other threads:[~2018-02-07 22:05 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 [this message]
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=CAC20D2MLBnHq0nQnrec+-tLuCOhMXQdLNZvwfEd79nPnSxsQ9g@mail.gmail.com \
    --to=clemc@ccc.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).