As some of us remember this commercial. Predicting the future. Note that
Ethernet is a bus topology at this point.
Anyway, Allen Kay recently uploaded a copy of the wonderful and futurist
“Xerox Information Outlet TV commercial to YouTube.” A number of us think it
aired in the late 70s’, early ‘80s* i.e. *around the time of
DEC/Xerox/Intel “Blue Book” definition of Ethernet.
I understand the back story on the commercial is this:
The PARC guys did the drawing on the wall with a pale blue pencil so the
actor would see it, but the camera wouldn’t. All he had to do was trace the
lines.
Take 1. His delivery was perfect in but his drawing looked like a giant
smashed spider.
Take 2. Again, a flawless reading. This time his work of art was about
11”x17”. You had to squint to see it. The director yelled, cut! Then he
said to the actor, “Come here for a second.” He came forward. “Turn
around,” said the director. The actor did an about-face. They both stared
at the wall. Like talking to a 4-year old, the director said,
“Look...what... you... did.” “Whoops!” said the talent.
Take 3. The drawing was great but he flubbed the last. .. ah damn…
Take 4. Started out fine. We held our breath. Good...good...good.
“...and...Cut!! Perfect!” The director shouted.
https://www.youtube.com/watch?v=m2WgFpyL2Pk
On 7/6/20 7:30 PM, Greg 'groggy' Lehey wrote:
> People (not just Clem), when you change the topic, can you please
> modify the Subject: to match? I'm not overly interested in uucp,
> but editors are a completely different matter. I'm sure I'm not the
> only one, so many interested parties will miss these replies.
I see this type of change happen — in my not so humble opinion — /way/
/too/ /often/.
So, I'm wondering if people are interested in configuring TUHS and / or
COFF mailing list (Mailman) with topics. That way people could
subscribe to the topics that they are interested in and not receive
copies of topics they aren't interested in.
I'm assuming that TUHS and COFF are still on Mailman mailing lists and
that Warren would be amicable to such.
To clarify, it would still be the same mailing list(s) as they exist
today. They would just have the to be utilized option of picking
interesting topics. Where topics would be based on keywords in the
message body.
I'm just trying to gauge people's interest in this idea.
--
Grant. . . .
unix || die
On Wed, 8 Jul 2020, Jacob Goense wrote:
> When I have tuned out of a long running thread and the topic drifts
> significantly I'm always grateful to the kind soul that tags..:
>
> Subject: Re: new [was: old]
Yeah, I try and remember to do that...
-- Dave
The Internet's original graphics trio of "*Booth, Beatty, and Barsky*" (who
had been affectionately dubbed the graphics industries' "*Killer Bs*") lost
one for their greats minds and personalities this last week. With great
sadden in my heart, I regret to inform you that John Beatty has passed
away. I was informed this AM by his partner is so many enterprises, Kelly
Booth, that John died peacefully in his sleep in the early morning on
Thursday, July 2, 2020.
When we look at the wonders of the Internet's growth in the use of computer
graphics, we view his legacy. But more than that, John was a good friend of
many of us and, of course, we all miss him.
Kelly tells me that the obituary with further information is being prepared
by John’s sister, Jean Beatty, and well as others. We'll be sure to try to pass
on a copy (or a link if it is on the web) when it has been released.
Clem
Does anyone have any experience with UUCP on macOS or *BSD systems that
would be willing to help me figure something out?
I'm working on adding a macOS X system to my micro UUCP network and
running into some problems.
- uuto / uucp copy files from my non-root / non-(_)uucp user to the
UUCP spool. But the (demand based) ""call (pipe over SSH) is failing.
- running "uucico -r1 -s <remote system name> -f" as the (_)uucp user
(via sudo) works.
- I'm using the pipe port type and running things over an SSH connection.
- The (_)uucp user can ssh to the remote system as expected
without any problems or being prompted for a password. (Service
specific keys w/ forced command.)
I noticed that the following files weren't set UID or GID like they are
on Linux. But I don't know if that's a macOS and / or *BSD difference
when compared to Linux.
/usr/bin/uucp
/usr/bin/uuname
/usr/bin/uustat
/usr/bin/uux
/usr/sbin/uucico
/usr/sbin/uuxqt
Adding the set UID & GID bits allowed things to mostly work.
Aside: Getting the contemporary macOS so that I could edit the
(/usr/share/uucp/) sys & port files was a treat.
I figured that it was worth inquiring if anyone had any more experience
/ tips / gotchas before I go bending ~> breaking things even more.
Thank you.
--
Grant. . . .
unix || die
In 1966, Engineers at IBM invented a method of speeding up execution
without adding a lot of very expensive memory. They called their
invention the muffer. The name did not catch on so they picked another
name and submitted an article to the IBM System J. The editor noted
that their second name was heavily overused and suggested a third name,
which the engineers accepted. The third name was cache.
(Muffer was short for memory buffer.)
This from "IBM's 360 and Early 370 Systems", MIT Press. I found this
an amusing tidbit of history -- hopefully so may others.
N.
