From: Kenneth Goodwin <kennethgoodwin56@gmail.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: segaloco <segaloco@protonmail.com>,
Paul Ruizendaal <pnr@planet.nl>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Origins of the frame buffer device
Date: Wed, 8 Mar 2023 13:43:45 -0500 [thread overview]
Message-ID: <CAMQbRb0a_se6GR4rY43sCs3VBw+R1SJGKpkKRqFExbrv8fsrGQ@mail.gmail.com> (raw)
In-Reply-To: <20230308182120.GL5993@mcvoy.com>
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
On Wed, Mar 8, 2023, 1:21 PM Larry McVoy <lm@mcvoy.com> wrote:
> I really miss terminal rooms. I learned so much looking over the
> shoulders of more experienced people. Wait, you can run a paragraph of
> text through fmt(1)? How the heck did you do that?
>
> I don't really miss it for me, I'm retired, but I think kids learning
> are sort of at a disadvantage. Not sure there is a youtube video that
> teaches you to say:
>
> :map , !}fmt<CR>
>
You could all create those videos.
How to"s
The histories
Evolution.
Working with the Legends of Computer Science
Insights into working on the R&D side
Give them an insight into the problems you faced and how you approached
finding a solution. Teaches critical thinking, how to approach the
impossible problem
From a personal perspective.
The emotional side of great research
The eureka moments in your lives.
Teach inspire
The olde Geezer Geeks Educational Video Series for Young Minds and New
Hackers.
> On Wed, Mar 08, 2023 at 06:12:48PM +0000, segaloco via TUHS wrote:
> > I've always liked the "Workbench" terminology that AT&T used, it summons
> to mind a more communal environment than the idea of a "workstation" does.
> The former makes me think of my time in the lab.....
> --
> ---
> Larry McVoy Retired to fishing
> http://www.mcvoy.com/lm/boat
>
[-- Attachment #2: Type: text/html, Size: 2407 bytes --]
next prev parent reply other threads:[~2023-03-08 18:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 15:01 [TUHS] " Paul Ruizendaal via TUHS
2023-03-05 17:29 ` [TUHS] " Grant Taylor via TUHS
2023-03-05 18:25 ` Kenneth Goodwin
2023-03-06 8:51 ` Paul Ruizendaal via TUHS
2023-03-06 8:57 ` Rob Pike
2023-03-06 11:09 ` Henry Bent
2023-03-06 16:02 ` Theodore Ts'o
2023-03-06 22:47 ` Paul Ruizendaal via TUHS
2023-03-06 23:10 ` Rob Pike
2023-03-08 12:53 ` Paul Ruizendaal
2023-03-08 14:23 ` Dan Cross
2023-03-08 15:06 ` Paul Ruizendaal
2023-03-08 19:35 ` Dan Cross
2023-03-08 16:55 ` Theodore Ts'o
2023-03-08 17:46 ` Clem Cole
2023-03-08 17:45 ` Clem Cole
2023-03-08 18:12 ` segaloco via TUHS
2023-03-08 18:21 ` Larry McVoy
2023-03-08 18:43 ` Kenneth Goodwin [this message]
2023-03-08 18:45 ` Steffen Nurpmeso
2023-03-08 22:44 ` Clem Cole
2023-03-09 14:42 ` Paul Winalski
2023-03-06 23:20 ` segaloco via TUHS
2023-03-07 1:24 ` Kenneth Goodwin
2023-03-08 3:07 ` Rob Gingell
2023-03-08 12:51 ` Paul Ruizendaal via TUHS
2023-03-08 13:05 ` Warner Losh
2023-03-08 13:17 ` Arno Griffioen via TUHS
2023-03-07 1:54 ` Kenneth Goodwin
2023-03-05 18:52 Noel Chiappa
2023-03-05 20:43 ` Rob Pike
2023-03-06 10:43 ` Jonathan Gray
2023-03-07 1:21 ` Kenneth Goodwin
2023-03-08 5:43 ` Lars Brinkhoff
2023-03-09 23:24 ` emanuel stiebler
2023-03-10 1:44 ` Lawrence Stewart
2023-03-06 23:16 Norman Wilson
2023-03-06 23:24 ` Larry McVoy
2023-03-07 12:08 ` arnold
2023-03-07 16:42 ` Theodore Ts'o
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=CAMQbRb0a_se6GR4rY43sCs3VBw+R1SJGKpkKRqFExbrv8fsrGQ@mail.gmail.com \
--to=kennethgoodwin56@gmail.com \
--cc=lm@mcvoy.com \
--cc=pnr@planet.nl \
--cc=segaloco@protonmail.com \
--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).