The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: George Michaelson <ggm@algebras.org>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Usenix: no official Unix 50th celebration, apparently
Date: Wed, 29 Aug 2018 09:37:51 +1000	[thread overview]
Message-ID: <CAKr6gn0jD8CzQDDrvsoztRpKaVAZAgUgN+MZEHEwcq9Dz6weyA@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1808290917190.41601@aneurin.horsfall.org>

sockets broke that. ioctl() always felt like special magic to me, but
sockets+ioctl is not just special magic, its arcane.

I think part of the problem is that a network binding actually isn't
"just like a file" because it incudes things like out of order
delivery, and control (side) channel.

TBF, sparse files and network file systems is another place things
broke down. For some reason, device-special and sparse files wound up
being in the too hard basket for network mounts.

I know Lindsay Marshall of old, so have a soft spot for the newcastle
connections (.../mounthost/path/to/file) syntax. I always liked this.
On Wed, Aug 29, 2018 at 9:30 AM Dave Horsfall <dave@horsfall.org> wrote:
>
> I know that I'll probably get into trouble for writing this (I'm a born
> stirrer, coming from a military family), but...
>
> On Tue, 28 Aug 2018, Kevin Bowling wrote:
>
> > This is all so asinine it sounds like it’s run by a random haughty
> > social club of people far detached from systems and UNIX and especially
> > far from publishing systems papers that actually advance the art.
> > Sometimes it is necessary to let an org know it’s become a joke.  I’d
> > prefer to attend and assist with something not affiliated with Usenix
> > after reading this thread.
>
> I'm having trouble thinking of an OS (still in current use) that has
> remained *mostly* unchanged over 50 years.  Yes, Unix has certainly
> evolved, but is still recognisable as "do one thing, and do it well".
>
> It's just a shame that they seem to have broken the other philosophy of
> "everything looks like a file".
>
> -- Dave

  reply	other threads:[~2018-08-28 23:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-26  0:31 Warren Toomey
2018-08-26  1:04 ` Lyndon Nerenberg
2018-08-26  1:31   ` Larry McVoy
2018-08-26  2:03   ` Clem Cole
2018-08-26  2:34     ` Larry McVoy
2018-08-26  2:47 ` Dave Horsfall
2018-08-26  4:10   ` Theodore Y. Ts'o
2018-09-05 21:31     ` Diomidis Spinellis
2018-09-06  0:23       ` Clem cole
2018-08-26  5:29 ` Kurt H Maier
2018-08-28 11:54   ` Kevin Bowling
2018-08-28 23:30     ` Dave Horsfall
2018-08-28 23:37       ` George Michaelson [this message]
2018-08-31 21:47 ` [TUHS] Usenix: no official Unix 50th celebration, (yet) Clem Cole
2018-12-26 21:49   ` reed

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=CAKr6gn0jD8CzQDDrvsoztRpKaVAZAgUgN+MZEHEwcq9Dz6weyA@mail.gmail.com \
    --to=ggm@algebras.org \
    --cc=dave@horsfall.org \
    --cc=tuhs@tuhs.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).