The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: itz@very.loosely.org (Ian Zimmerman)
Subject: [TUHS] Device special files
Date: Wed, 7 Feb 2018 11:07:59 -0800	[thread overview]
Message-ID: <20180207190759.7sjrf6ta4m7sct3d@matica.foolinux.mooo.com> (raw)
In-Reply-To: <20180207183607.E3NiH%steffen@sdaoden.eu>

On 2018-02-07 19:36, Steffen Nurpmeso wrote:

> Going from ``hardware only changes when the DEC Field engineer is
> here'' to ``my toaster has USB'' has put serious strain on the rather
> crude implementation of the ``devices as files'' concept

Well, if you don't try to connect your toaster to the computer, you
don't have this problem :-)

I had a self-maintained Linux system (ie. no distribution) until about
2000.  I had no problem understanding what the two dozen /dev/ entries
were for.  I even wrote a better (table driven) makedev implementation
and I tried to get it into Debian, but by that time rumors of devfs were
already on the way so it wasn't worth a transition to them.

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

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.


  reply	other threads:[~2018-02-07 19:07 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 [this message]
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=20180207190759.7sjrf6ta4m7sct3d@matica.foolinux.mooo.com \
    --to=itz@very.loosely.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).