From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Device special files
Date: Tue, 6 Feb 2018 20:40:05 -0500 [thread overview]
Message-ID: <CAC20D2PPmbsJ8D2cW1Cx+QRw1BUm9F-tB1J6EpsSH4ZJLQ=eaw@mail.gmail.com> (raw)
In-Reply-To: <007f01d39fb4$12524eb0$36f6ec10$@ronnatalie.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
Are you refering to specdev when Solaris when file system crazy and
everything was it's own file system.
ᐧ
On Tue, Feb 6, 2018 at 8:36 PM, Ron Natalie <ron at ronnatalie.com> wrote:
> Speaking of all this. .. Didn't Solaris symlink the device files into some
> magic file system path rather than using the older major/minor special of
> the traditional UNIX?
>
>
>
> \
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180206/37b018af/attachment.html>
next prev parent reply other threads:[~2018-02-07 1:40 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 [this message]
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='CAC20D2PPmbsJ8D2cW1Cx+QRw1BUm9F-tB1J6EpsSH4ZJLQ=eaw@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).