The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Arrigo Triulzi <arrigo@alchemistowl.org>
Cc: The Eunuchs Historic Society <tuhs@tuhs.org>
Subject: Re: [TUHS] congratulations to Warner on a great talk
Date: Wed, 25 Sep 2019 09:09:08 -0600	[thread overview]
Message-ID: <CANCZdfoJ1kTa58oUq2RAxVCHM4nRQ1YiOZweLoqSSmgXe7RR3A@mail.gmail.com> (raw)
In-Reply-To: <F0785DDE-F597-4622-AC5E-1D242B749F6B@alchemistowl.org>

[-- Attachment #1: Type: text/plain, Size: 2653 bytes --]

On Wed, Sep 25, 2019 at 8:43 AM Arrigo Triulzi <arrigo@alchemistowl.org>
wrote:

> On 21 Sep 2019, at 16:44, Eric Allman <tuhs@eric.allman.name> wrote:
> > Word this morning was that the recordings will be up in "a couple of
> > days".  Keep an eye on https://2019.eurobsdcon.org/ — at the moment
> > there's a "livestream" pull-down, which I predict will be replaced with
> > a pointer to the recordings (although they could end up elsewhere; I
> > have no inside information).
>
> None of the talks appear to be published and, even more sadly, neither
> have slides appeared with the exception of the keynote on silly Slideshare.
>
> I really hope they don’t disappear without trace.
>

Slides have been published, though maybe not through the EuroBSDCon site. I
wasn't aware that I could publish them there.

https://docs.google.com/presentation/d/177KxOif5oHARyIdZHDq-OO67_GVtMkzIAlDX-cHxgb4/edit?usp=sharing

I'm told it will be a small number of weeks before the bsdtv folks that
taped everything can edit the talks down from the raw footage and post them
to youtube. They have the raw livestream, but a small number of tweaks need
to be made to each talk.

I'll be writing a followup paper, as well as an article for the FreeBSD
Journal. There's a number of small technical errors in the talk owing to
two factors: (1) I couldn't see my speaker notes during the talk so I think
I misspoke or neglected to include a clarifying sentence or two that I'd
planned and (2) I found more original material that helped to clarify
timelines (eg: PWB 1.0 was distributed outside of bell labs: it was V6 +
the "50 changes" based, but still retained features like the V6 TTY driver.
This was in 1978, about a year before V7 was released. PWB 2.0 was fully V7
based and included updates to the tools PWB added, exact details TBD). I
did talk a little about the ambiguity between UNIX/TS and PWB/UNIX 3.0 in
the talk, but the details of that need to be ironed out a bit. I hope to go
through more original sources to figure all that out as different people
remember things slightly differently, and sometimes contemporary
documentation or scholarly papers contradicts the remembrance so I need to
sort that out better, as well as where I can run diffs between supposed
sources of things to find as much of the truth around this that I can.

I hope to give this talk again, with some tweaks, since it was well
received. It's been a while since my talks have provoked that much
enthusiastic energy in the room. Maybe FOSDEM, BSDCan and something Linux
oriented / related in the US.

Warner

Warner

Warner

[-- Attachment #2: Type: text/html, Size: 3465 bytes --]

  reply	other threads:[~2019-09-25 15:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-21 13:32 Eric Allman
2019-09-21 14:08 ` Arrigo Triulzi
2019-09-21 14:44   ` Eric Allman
2019-09-25 14:41     ` Arrigo Triulzi
2019-09-25 15:09       ` Warner Losh [this message]
2019-09-25 15:17         ` Arrigo Triulzi
2019-09-25 15:26           ` Warner Losh
2019-09-25 15:32             ` Arrigo Triulzi
2019-09-25 16:48       ` Eric Allman
2019-09-21 16:39 ` Clem Cole

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=CANCZdfoJ1kTa58oUq2RAxVCHM4nRQ1YiOZweLoqSSmgXe7RR3A@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=arrigo@alchemistowl.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).