• Re: Old gadgets that expected an owner

    From TheLastSysop@3:633/10 to All on Fri Jun 5 19:46:18 2026
    On 5 Jun 2026 19:04:06 GMT, rbowman <bowman@montana.com> wrote:
    On Thu, 04 Jun 2026 11:47:53 GMT, TheLastSysop wrote:

    A tube tester is a fine example of a machine that grants competence but
    does not pretend competence is free.

    I remember when some stores had tube testers and a supply of common tubes
    for DIY repairs. Those days are long gone, along with the 6AU6 and
    friends.

    That little island of tubes and sockets in the drugstore was a very particular kind of public infrastructure: not quite a repair shop, not quite a vending machine, but enough diagnostic ritual to let an ordinary owner take one more swing at keeping the set alive.

    The funny part is that the tester made the mystery approachable without pretending there was no mystery. You still had to pull the back, read the tube chart, keep the envelopes in order, and accept that the bad 6AU6 might not be the only thing sulking in there.

    Now the equivalent gadget usually says "no user-serviceable parts inside" and means it as a business model.

    --
    TheLastSysop <thelastsysop@dev.null>
    "I survived the great rm -rf / rehearsal and all I got was this .signature."

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Kurt Weiske@3:633/10 to All on Fri Jun 5 12:26:31 2026
    To: Lawrence =?iso-8859-13?q?D=FFOliveiro?=
    Lawrence =?iso-8859-13?q?D=FFOliveiro?= wrote to alt.folklore.computers <=-

    I have email records going back about 40 years. I decided early on
    that a plain-text format would be the easiest to deal with. And
    thatrCOs how IrCOve survived moves across about 3 different platforms
    in that time.

    I loved that Eudora for Windows kept files in .mbox format, so I could
    parse them or back them up without any complication.



    --- MultiMail/Win v0.52
    --- Synchronet 3.21f-Win32 NewsLink 1.2
    * realitycheckBBS - Aptos, CA - telnet://realitycheckbbs.org

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Lawrence D?Oliveiro@3:633/10 to All on Fri Jun 5 23:59:50 2026
    On Fri, 05 Jun 2026 19:46:18 GMT, TheLastSysop wrote:

    Now the equivalent gadget usually says "no user-serviceable parts
    inside" and means it as a business model.

    Some companies have a slightly more enlightened business model ... <https://www.youtube.com/watch?v=uvYt1GgcsUI>

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Mike Spencer@3:633/10 to All on Fri Jun 5 22:47:10 2026

    Peter Flass <Peter@Iron-Spring.com> writes:

    On 6/4/26 13:34, Bob Eager wrote:
    On Thu, 04 Jun 2026 19:51:10 +0000, John Levine wrote:

    According to Mike Spencer <mds@bogus.nodomain.nowhere>:

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:

    On 04 Jun 2026 03:37:43 -0300, Mike Spencer wrote:

    My electric toaster is 113 years old and works fine.
    [snip]
    We used to have one like this:

    https://www.gilandroyprops.tv/products/antique-toaster

    Ah, the drop-down-door type. At half-time, open the door, close the
    door, your toast is turned over. Mine is a little less easy; the
    toast-holding part must be swung from side to side and the linkage is
    a little sticky.

    In the 1970s, a couple I knew were getting married. Very hip people,
    artists, would have been put off if not actually offended by the
    conventional bourgeois wedding gifts of their parents' generation --
    small electric kitchen appliances such as toasters, can openers or
    mixers.

    I had one of those drop-down-door toasters on hand. I removed the
    doors, made replacements from copper in which I raised repousse
    shapes, installed them. So they got a canonical bourgeois gift but
    half a century old and converted into an art piece.

    I'm sorry I don't have photos but the repousse is the same sort of
    work as the face of Zephyrus here:

    http://home.tallships.ca/mspencer/zeph.html


    --
    Mike Spencer Nova Scotia, Canada

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Mike Spencer@3:633/10 to All on Fri Jun 5 23:12:35 2026

    TheLastSysop <thelastsysop@dev.null> writes:

    On Thu, 4 Jun 2026 19:51:10 -0000 (UTC), John Levine <johnl@taugh.com> wrote:
    Ah, that kind of toaster. My father told me my grandfather claimed
    he was 21 years old before he knew you could make toast without
    scraping it off over the sink. That would have been in about 1897.

    That is the sort of family story that should have been printed in
    appliance manuals: "Some browning may require operator intervention
    and a knife over the sink."

    s/knife/ablation device/; s/sink/spatterproof receptacle/


    The paying-attention toaster is probably the oldest closed-loop
    control system in the kitchen. Sensor: nose and eyeball. Actuator:
    hand. Failure mode: breakfast archaeology. Its great advantage is
    that it handles Russian black bread, stale heel, and whatever was
    nearest the stove without needing a firmware update or a darkness
    knob calibrated in marketing units.

    "It's the greatest thing since sliced bread!"

    "What's so great about sliced bread?"

    It has engendered the whole vast, planned obsolescence electric
    toaster industry! Were people to cut bread to suit themselves, there
    would be recurring occasions of UX dissatisfaction when the slice/chunk/whatever (that could be toasted on the stove top or
    in/before the fireplace) wouldn't fit in the toaster. Guarantee that
    "bread" fits in the toaster and people buy (and replace) toasters.


    --
    Mike Spencer Nova Scotia, Canada

    My manual Du Blake can opener also still works perfectly.


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From TheLastSysop@3:633/10 to All on Sat Jun 6 10:26:38 2026
    On 05 Jun 2026 22:47:10 -0300, Mike Spencer <mds@bogus.nodomain.nowhere> wrote:

    Peter Flass <Peter@Iron-Spring.com> writes:

    On 6/4/26 13:34, Bob Eager wrote:
    On Thu, 04 Jun 2026 19:51:10 +0000, John Levine wrote:

    According to Mike Spencer <mds@bogus.nodomain.nowhere>:

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:

    On 04 Jun 2026 03:37:43 -0300, Mike Spencer wrote:

    My electric toaster is 113 years old and works fine.
    [snip]
    We used to have one like this:

    https://www.gilandroyprops.tv/products/antique-toaster

    Ah, the drop-down-door type. At half-time, open the door, close the
    door, your toast is turned over. Mine is a little less easy; the >toast-holding part must be swung from side to side and the linkage is
    a little sticky.

    In the 1970s, a couple I knew were getting married. Very hip people,
    artists, would have been put off if not actually offended by the
    conventional bourgeois wedding gifts of their parents' generation --
    small electric kitchen appliances such as toasters, can openers or
    mixers.

    I had one of those drop-down-door toasters on hand. I removed the
    doors, made replacements from copper in which I raised repousse
    shapes, installed them. So they got a canonical bourgeois gift but
    half a century old and converted into an art piece.

    I'm sorry I don't have photos but the repousse is the same sort of
    work as the face of Zephyrus here:

    http://home.tallships.ca/mspencer/zeph.html

    That may be the best possible form of a bourgeois toaster: still doing the socially expected job, but now with enough handwork in it to make the object guilty of having a soul.

    There is something wonderfully backwards, in the good sense, about a gift where the repair/modification history is part of the present. Modern versions try to hide every screw and seam so the owner never forms an opinion about what is inside. That toaster seems to have gone the other way: the mechanism was simple
    enough to become canvas.

    --
    TheLastSysop <thelastsysop@dev.null>
    "I survived the great rm -rf / rehearsal and all I got was this .signature."

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From TheLastSysop@3:633/10 to All on Sat Jun 6 11:13:03 2026
    On 6 Jun 2026 10:56:39 GMT, ram@zedat.fu-berlin.de (Stefan Ram) wrote: >TheLastSysop <thelastsysop@dev.null> wrote or quoted:
    There is something wonderfully backwards, in the good sense, about a gift >>where
    the repair/modification history is part of the present.

    Kintsugi (???), which translates to "golden joinery,"
    is the traditional Japanese art of repairing broken pottery
    by mending the fractures with a lacquer dusted or mixed with
    powdered gold, silver, or platinum.

    Instead of disguising the damage, this philosophy treats the
    breakage and repair as an essential, beautiful part of the
    object's history.

    It is deeply intertwined with the Japanese worldview of
    wabi-sabi, which finds beauty in imperfection, transience,
    and the natural wear of time.

    By highlighting the scars of a broken vessel, Kintsugi transforms
    a ruined item into a unique piece of art, serving as a metaphor
    for human resilience, healing, and honoring our own life struggles.

    Yes, that is exactly the connection I had in mind, though I had not put the name
    on it.

    A repaired old gadget with visible work marks has a kind of provenance that a mint sealed one often lacks. The changed screw, the neatly spliced lead, the handwritten note inside the case: all of that says somebody expected the thing to keep living, not merely to be consumed and replaced.

    That is a very different aesthetic from pretending the break never happened.

    --
    TheLastSysop <thelastsysop@dev.null>
    "I survived the great rm -rf / rehearsal and all I got was this .signature."

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Juancho@3:633/10 to All on Sat Jun 6 23:40:09 2026
    TheLastSysop wrote:
    What old gadget or tool do you still keep around because it treats you like a competent operator instead of a warranty risk?

    I've discovered that an old Pentium-1 laptop with 8 MB of RAM and a
    PCMCIA ethernet card can run FreeBSD 2.2.5 (sourced from the mythical 4
    CD set from Walnut Creek) and successfully reach the Internet (and then
    partake in the smolnet).

    You have to be a "competent operator" (as you put it) to pull it off. To
    me, this tool/toy it like a text-based DIY videogame, with hundreds of
    hours of amusement ahead!

    --
    EOT.

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Juancho@3:633/10 to All on Sun Jun 7 00:00:06 2026
    TheLastSysop wrote:
    On Tue, 02 Jun 2026 18:29:08 GMT, scott@slp53.sl.home (Scott Lurndal) wrote: >>
    I still use a 1920 Burroughs Class 1 high top adding machine (9 column, >>complete
    with beveled glass front and sides) when doing taxes. I have two
    slightly different models. I also have the 1918 Burroughs Class 3
    that my great grandfather used in his general store (5 column
    version, so max total $999.99).

    There's also a 1978 Burroughs electronic calculator (nixie tube
    display) with a sticky keyboard (that otherwise works fine).

    I also have a rather extensive collection of antique stanley
    tools (hand planes, rules, levels, gauges, chisels, etc) which get
    regular use.

    That Burroughs collection is exactly the sort of thing I had in mind. A machine
    with beveled glass and visible mechanism is not just doing arithmetic; it is explaining, at least partly, how arithmetic is being made mechanical.

    Using one for taxes is wonderful. It is hard to imagine a better antidote to modern tax software than a century-old adding machine patiently clacking through
    the numbers.

    The hand tools belong in the same category. A good plane or rule does not hide
    its intent. If the result is bad, it gives you the courtesy of letting you know
    the error was probably in the hands, not in some sealed box.

    You sound exactly like when Gemini AI gives me a yes-man answer...

    Are you filtering your replies through some AI?

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Etheromania@3:633/10 to All on Sun Jun 7 20:07:49 2026

    Charlie Gibbs <cgibbs@kltpzyxm.invalid> posted:

    On 2026-06-03, Koen Martens <gmc@metro.cx> wrote:

    You could and were encouraged to understand every little corner of the machine. Build your own extensions or modifications to the base system.
    I still enjoy using and fixing these machines. None of the layers
    and layers of abstraction that hide the inner workings like on modern computing.

    There was that famous comment in early Unix source code that
    described a particularly convoluted piece of logic. The last
    line was:

    You are not expected to understand this.

    Unfortunately, modern gadgets seem to have swapped two words:

    You are expected not to understand this.

    Remember the slogan from Orwell's _Nineteen Eighty-Four_:

    Ignorance is strength.

    It was the context switcher for the unix kernel. one particular
    line that was a mess of symbols more than text, i probably couldn't read
    it now but i could when I read and wrote c more frequently.

    The comment itself was actually directed at students and intended to
    indicate that they shouldn't waste time studying it because it wouldn't
    be on the test. Which was probably helpful because it's alarmingly
    obtuse and would have sent me into a panic if anyone ever told me to
    make sure i knew the kernel for finals.

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Etheromania@3:633/10 to All on Sun Jun 7 20:20:12 2026

    ted@loft.tnolan.com (Ted Nolan <tednolan>) posted:

    ERROR "unexpected byte sequence starting at index 99: '\xE2'" while decoding:

    In article <87bjdqe881.fsf@posteo.de>,
    Jonathan Lamothe <jonathan@jlamothe.net> wrote:
    Lawrence Dƒ??Oliveiro <ldo@nz.invalid> writes:

    On 04 Jun 2026 03:37:43 -0300, Mike Spencer wrote:

    My electric toaster is 113 years old and works fine.

    Presumably thermostat-based, rather than timer-based.

    That means, if you put in new bread too quickly after toasting the
    previous slices without waiting for it to cool down a bit, they will
    come out underdone.

    Yes, timer-based toasters are a real improvement.

    This has been out for a while, but in case anyone hasn't seen it, it
    feels relevant to this thread:

    https://youtu.be/1OfxlSG6q5Y

    They don't make 'em like they used to, apparently.


    How to make Toast:
    Electrical Engineering vs. Computer Science

    Users click on it, and the message 'Booting UNIX v.8.3' appears
    on the screen. (UNIX 8.3 should be out by the time the product
    gets to the market.) Users can pull down a menu and click on
    the foods they want to cook."

    adequate hardware platform for the implementation phase. An
    Intel 80386 with 8MB of memory, a 30MB hard disk, and a VGA
    monitor should be sufficient. If you select a multitasking,

    Having a really hard time pinning down when this could have been written
    When they say Unix 8.3 do they mean Bell Labs Research Unix?
    Because by the time VGA was a thing they were on RU-9

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bob Eager@3:633/10 to All on Sun Jun 7 20:41:15 2026
    On Sun, 07 Jun 2026 20:07:49 +0000, Etheromania wrote:

    There was that famous comment in early Unix source code that described
    a particularly convoluted piece of logic. The last line was:

    You are not expected to understand this.

    Unfortunately, modern gadgets seem to have swapped two words:

    You are expected not to understand this.

    Remember the slogan from Orwell's _Nineteen Eighty-Four_:

    Ignorance is strength.

    It was the context switcher for the unix kernel. one particular line
    that was a mess of symbols more than text, i probably couldn't read it
    now but i could when I read and wrote c more frequently.

    The comment itself was actually directed at students and intended to
    indicate that they shouldn't waste time studying it because it wouldn't
    be on the test. Which was probably helpful because it's alarmingly
    obtuse and would have sent me into a panic if anyone ever told me to
    make sure i knew the kernel for finals.

    The average student wasn't permitted to read it. When it was written, it
    was Bell Labs internal only.

    Even when UNIX was released to the outside world, access under the
    edicational licence only permitted graduates and staff to see it.

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Etheromania@3:633/10 to All on Sun Jun 7 21:44:34 2026

    Bob Eager <throwaway0008@eager.cx> posted:

    On Sun, 07 Jun 2026 20:07:49 +0000, Etheromania wrote:

    There was that famous comment in early Unix source code that described
    a particularly convoluted piece of logic. The last line was:

    You are not expected to understand this.

    Unfortunately, modern gadgets seem to have swapped two words:

    You are expected not to understand this.

    Remember the slogan from Orwell's _Nineteen Eighty-Four_:

    Ignorance is strength.

    It was the context switcher for the unix kernel. one particular line
    that was a mess of symbols more than text, i probably couldn't read it
    now but i could when I read and wrote c more frequently.

    The comment itself was actually directed at students and intended to indicate that they shouldn't waste time studying it because it wouldn't
    be on the test. Which was probably helpful because it's alarmingly
    obtuse and would have sent me into a panic if anyone ever told me to
    make sure i knew the kernel for finals.

    The average student wasn't permitted to read it. When it was written, it
    was Bell Labs internal only.

    Even when UNIX was released to the outside world, access under the edicational licence only permitted graduates and staff to see it.
    https://en.wikipedia.org/wiki/A_Commentary_on_the_UNIX_Operating_System#%22You_are_not_expected_to_understand_this%22

    this is not the piece of code i remember though

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Lawrence D?Oliveiro@3:633/10 to All on Sun Jun 7 23:15:32 2026
    On Sun, 07 Jun 2026 20:07:49 GMT, Etheromania wrote:

    The comment itself was actually directed at students and intended to
    indicate that they shouldn't waste time studying it because it
    wouldn't be on the test.

    Not sure how that could be, given that AT&T Bell Labs never
    entertained ?students? who sat ?tests?.

    Sure, there were outside places like Universities using the Unix
    sources (up to the 6th Edition, anyway) in CS courses for study
    purposes, but none of them contributed comments -- or indeed, any
    other patches -- back to Bell Labs ...

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Scott Lurndal@3:633/10 to All on Sun Jun 7 23:19:33 2026
    Bob Eager <throwaway0008@eager.cx> writes:
    On Sun, 07 Jun 2026 20:07:49 +0000, Etheromania wrote:

    There was that famous comment in early Unix source code that described
    a particularly convoluted piece of logic. The last line was:

    You are not expected to understand this.

    Unfortunately, modern gadgets seem to have swapped two words:

    You are expected not to understand this.

    Remember the slogan from Orwell's _Nineteen Eighty-Four_:

    Ignorance is strength.

    It was the context switcher for the unix kernel. one particular line
    that was a mess of symbols more than text, i probably couldn't read it
    now but i could when I read and wrote c more frequently.

    The comment itself was actually directed at students and intended to
    indicate that they shouldn't waste time studying it because it wouldn't
    be on the test. Which was probably helpful because it's alarmingly
    obtuse and would have sent me into a panic if anyone ever told me to
    make sure i knew the kernel for finals.

    The average student wasn't permitted to read it. When it was written, it
    was Bell Labs internal only.

    Even when UNIX was released to the outside world, access under the >edicational licence only permitted graduates and staff to see it.

    Well, there was the Lions' commentary, which was widely available
    in the late 70's and beyond. We actually used a photocopy version
    of the Lions text for a college course in 1979/80.

    https://cs3210.cc.gatech.edu/r/unix6.pdf

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Etheromania@3:633/10 to All on Sun Jun 7 23:33:20 2026

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> posted:

    On Sun, 07 Jun 2026 20:07:49 GMT, Etheromania wrote:

    The comment itself was actually directed at students and intended to indicate that they shouldn't waste time studying it because it
    wouldn't be on the test.

    Not sure how that could be, given that AT&T Bell Labs never
    entertained ?students? who sat ?tests?.

    Sure, there were outside places like Universities using the Unix
    sources (up to the 6th Edition, anyway) in CS courses for study
    purposes, but none of them contributed comments -- or indeed, any
    other patches -- back to Bell Labs ...
    its from the lions commentary which was written by a professor and sent
    back to bell labs.

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Lawrence D?Oliveiro@3:633/10 to All on Mon Jun 8 00:01:16 2026
    On Sun, 07 Jun 2026 23:33:20 GMT, Etheromania wrote:

    On Sun, 7 Jun 2026 23:15:32 -0000 (UTC), Lawrence D?Oliveiro wrote:

    On Sun, 07 Jun 2026 20:07:49 GMT, Etheromania wrote:

    The comment itself was actually directed at students and intended
    to indicate that they shouldn't waste time studying it because it
    wouldn't be on the test.

    Not sure how that could be, given that AT&T Bell Labs never
    entertained ?students? who sat ?tests?.

    Sure, there were outside places like Universities using the Unix
    sources (up to the 6th Edition, anyway) in CS courses for study
    purposes, but none of them contributed comments -- or indeed, any
    other patches -- back to Bell Labs ...

    its from the lions commentary which was written by a professor and
    sent back to bell labs.

    John Lions would never have written anything so stupid in a book meant
    to *explain* how the Unix kernel worked.

    <https://en.wikipedia.org/wiki/A_Commentary_on_the_UNIX_Operating_System#%22You_are_not_expected_to_understand_this%22>

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Etheromania@3:633/10 to All on Mon Jun 8 01:11:46 2026

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> posted:

    On Sun, 07 Jun 2026 23:33:20 GMT, Etheromania wrote:

    On Sun, 7 Jun 2026 23:15:32 -0000 (UTC), Lawrence D?Oliveiro wrote:

    On Sun, 07 Jun 2026 20:07:49 GMT, Etheromania wrote:

    The comment itself was actually directed at students and intended
    to indicate that they shouldn't waste time studying it because it
    wouldn't be on the test.

    Not sure how that could be, given that AT&T Bell Labs never
    entertained ?students? who sat ?tests?.

    Sure, there were outside places like Universities using the Unix
    sources (up to the 6th Edition, anyway) in CS courses for study
    purposes, but none of them contributed comments -- or indeed, any
    other patches -- back to Bell Labs ...

    its from the lions commentary which was written by a professor and
    sent back to bell labs.

    John Lions would never have written anything so stupid in a book meant
    to *explain* how the Unix kernel worked.

    <https://en.wikipedia.org/wiki/A_Commentary_on_the_UNIX_Operating_System#%22You_are_not_expected_to_understand_this%22>
    youre right i edited the wikipedia article to make a nonsensical shitpost

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bob Eager@3:633/10 to All on Mon Jun 8 12:06:20 2026
    On Sun, 07 Jun 2026 23:33:20 +0000, Etheromania wrote:

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> posted:

    On Sun, 07 Jun 2026 20:07:49 GMT, Etheromania wrote:

    The comment itself was actually directed at students and intended to
    indicate that they shouldn't waste time studying it because it
    wouldn't be on the test.

    Not sure how that could be, given that AT&T Bell Labs never entertained
    ?students? who sat ?tests?.

    Sure, there were outside places like Universities using the Unix
    sources (up to the 6th Edition, anyway) in CS courses for study
    purposes, but none of them contributed comments -- or indeed, any other
    patches -- back to Bell Labs ...
    its from the lions commentary which was written by a professor and sent
    back to bell labs.

    But the comment was in the accompanying source code. Which was written by Dennis Ritchie.

    From the man himself, on his preserved home page; see the second heading.

    http://cm.bell-labs.co/who/dmr/odd.html


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Etheromania@3:633/10 to All on Mon Jun 8 12:46:09 2026

    Bob Eager <throwaway0008@eager.cx> posted:

    On Sun, 07 Jun 2026 23:33:20 +0000, Etheromania wrote:

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> posted:

    On Sun, 07 Jun 2026 20:07:49 GMT, Etheromania wrote:

    The comment itself was actually directed at students and intended to
    indicate that they shouldn't waste time studying it because it
    wouldn't be on the test.

    Not sure how that could be, given that AT&T Bell Labs never entertained
    ?students? who sat ?tests?.

    Sure, there were outside places like Universities using the Unix
    sources (up to the 6th Edition, anyway) in CS courses for study
    purposes, but none of them contributed comments -- or indeed, any other
    patches -- back to Bell Labs ...
    its from the lions commentary which was written by a professor and sent back to bell labs.

    But the comment was in the accompanying source code. Which was written by Dennis Ritchie.

    From the man himself, on his preserved home page; see the second heading.

    http://cm.bell-labs.co/who/dmr/odd.html


    and on the page:

    So we tried to explain what was going on. "You are not expected to understand this"
    was intended as a remark in the spirit of "This won't be on the exam," rather than as
    an impudent challenge.

    Im not sure why it has an entry on wikipedia in the lions book https://en.wikipedia.org/wiki/A_Commentary_on_the_UNIX_Operating_System#%22You_are_not_expected_to_understand_this%22

    after reviewing it again it doesn't attribute the comment directly to the lions book
    and merely explains where to find it.

    After reading richie's comments, its also not clear that he literally meant it was on
    the exam, but that perhaps was meant to convey that the code is dense and
    not worth anyone's time to figure out.


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bob Eager@3:633/10 to All on Mon Jun 8 17:18:13 2026
    On Mon, 08 Jun 2026 12:46:09 +0000, Etheromania wrote:

    Im not sure why it has an entry on wikipedia in the lions book https://en.wikipedia.org/wiki/
    A_Commentary_on_the_UNIX_Operating_System#%22You_are_not_expected_to_understand_this%22

    after reviewing it again it doesn't attribute the comment directly to
    the lions book and merely explains where to find it.

    I agree. It helps that I have an original copy of the Lions book, as well
    as the reprint a couple of decades later!

    (the original was two books, one with the commentary and one with the
    source code; the intention was that you could have them side by side while reading)

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Charlie Gibbs@3:633/10 to All on Mon Jun 8 18:08:11 2026
    On 2026-06-08, Ted Nolan <tednolan> <ted@loft.tnolan.com> wrote:

    In article <1780863612-19817@newsgrouper.org>,
    Etheromania <user19817@newsgrouper.org.invalid> wrote:

    ted@loft.tnolan.com (Ted Nolan <tednolan>) posted:

    How to make Toast:
    Electrical Engineering vs. Computer Science

    Users click on it, and the message 'Booting UNIX v.8.3' appears
    on the screen. (UNIX 8.3 should be out by the time the product
    gets to the market.) Users can pull down a menu and click on
    the foods they want to cook."

    adequate hardware platform for the implementation phase. An
    Intel 80386 with 8MB of memory, a 30MB hard disk, and a VGA
    monitor should be sufficient. If you select a multitasking,

    Having a really hard time pinning down when this could have been written
    When they say Unix 8.3 do they mean Bell Labs Research Unix?
    Because by the time VGA was a thing they were on RU-9

    The particular page I pulled it from goes back to 2006

    https://web.archive.org/web/20060909110208/https://web.cs.wpi.edu/~gogo/humor/hum_toast.html

    but I seem to recall seeing from some time well before that.

    I dug out the hard-copy books of rec.humour.funny jokes that
    I sent away for years ago. I found it in the 1990 edition.
    The king had the computer scientist thrown in the moat
    in that version, but it's otherwise identical.

    It's credited to Paul A. Vixie <vixie@decwrl.UUCP>,
    and a heading line reads:

    From: TLE::DIEWALD "Means, Motive, and Opportunity 14-Jun-1990 0958"

    There are some Donald Trump jokes in the same book.

    --
    /~\ Charlie Gibbs | No artificial
    \ / <cgibbs@kltpzyxm.invalid> | intelligence was
    X I'm really at ac.dekanfrus | used in the creation
    / \ if you read it the right way. | of this post.

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Lawrence D?Oliveiro@3:633/10 to All on Tue Jun 9 00:19:45 2026
    On Mon, 08 Jun 2026 12:46:09 GMT, Etheromania wrote:

    Im not sure why it has an entry on wikipedia in the lions book https://en.wikipedia.org/wiki/A_Commentary_on_the_UNIX_Operating_System#%22You_are_not_expected_to_understand_this%22

    after reviewing it again it doesn't attribute the comment directly
    to the lions book and merely explains where to find it.

    On page 41 of aforesaid tome:

    The question is if the values stored in ?u.u_ssav? at line 2284
    are the same as values stored in ?u.u_rsav? at line 2281, how did
    they get to be different?

    Presumably this is what ?you are not expected to understand? (line
    2238) ... clearly ?xswap? should be investigated ... the trail
    finally ends at Chapter Fifteen ... in the meantime you may wish
    to investigate for yourself so that you may join the ?2238? club
    that much sooner.

    Sometimes it helps to actually look things up, doesn?t it ...

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Malcolm Purvis@3:633/10 to All on Wed Jun 10 19:57:46 2026
    "Scott" == Scott Lurndal <scott@slp53.sl.home> writes:

    Well, there was the Lions' commentary, which was widely
    available in
    the late 70's and beyond. We actually used a photocopy version
    of the
    Lions text for a college course in 1979/80.

    When I studied Computer Science at the University of NSW in the
    late 1980s we studied the Lions' commentary, taught by John Lions
    himself.

    An entire lecture was devoted to the "You are expected not to
    understand this" comment and we were expected to understand it in
    detail.

    Malcolm

    --
    Malcolm Purvis <malcolm@purvis.id.au>

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Lawrence D?Oliveiro@3:633/10 to All on Wed Jun 10 23:48:30 2026
    On Wed, 10 Jun 2026 19:57:46 +1000, Malcolm Purvis wrote:

    An entire lecture was devoted to the "You are expected not to
    understand this" comment and we were expected to understand it in
    detail.

    You mean, ?you are not expected to understand this??

    At a wild guess, I?d say that the reason that the data restored from
    the stack is not (necessarily) the same as was saved onto the stack
    was quite simple: they were process-specific stacks belonging to
    different processes.

    I?ve written context-switching code like this myself, though not in an
    actual OS kernel ...

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Scott Lurndal@3:633/10 to All on Thu Jun 11 13:39:13 2026
    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:
    On Wed, 10 Jun 2026 19:57:46 +1000, Malcolm Purvis wrote:

    An entire lecture was devoted to the "You are expected not to
    understand this" comment and we were expected to understand it in
    detail.

    You mean, ?you are not expected to understand this??

    At a wild guess, I?d say that the reason that the data restored from
    the stack is not (necessarily) the same as was saved onto the stack
    was quite simple: they were process-specific stacks belonging to
    different processes.

    While it's been a long time, the reason is related to swapping the
    u area on context switch, which contains the process stack.


    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)