• My Computer History (Re: Is This An Old Folks Home?)

    From Lars Poulsen@lars@beagle-ears.com to comp.os.linux.misc,alt.folklore.computers,comp.unix.geeks on Fri Nov 6 18:37:44 2026
    From Newsgroup: alt.folklore.computers

    On 11/3/2026 22:21, Charlie Gibbs wrote:
    On 2026-11-04, Rich <rich@example.invalid> wrote:

    c186282 <c186282@nnada.net> wrote:

    On 11/3/26 20:55, Woozy Song wrote:

    Usenet has a lot of people who have been using it since the 1990s, so
    presumably over 50 years old.-a I am a bit older, I remember 9-track
    tapes, punch cards and acoustic coupler modems.

    <waves hand> Me too!

    Umm ... they were EIGHT-track tapes :-)

    Idiot. Woozy's not referring to "8-track audio tapes".

    Uh, I think he was pulling our legs - note the smiley.

    He's referring to 9-track digital computer tapes used on
    old IBM mainframes. They were 9-tracks:

    https://en.wikipedia.org/wiki/9-track_tape

    Eight data bits plus one parity bit per byte makes for a "9-track"
    tape.

    If you're really old you'll remember 7-track tapes (6 data bits
    plus one parity bit, popular before 8-bit bytes came along).
    I don't think I ever actually used one of them, but I did read
    about them. I think some units even had a hardware converter
    option that let you attach them to a machine that did 8-bit
    bytes; for every three 8-bit bytes you sent them they'd write
    four 6-bit bytes to the tape. Good for converting your old
    tapes...

    1964: Junior High School. Getting simple computer architecture books
    (written for a general "Popular Mechanics" audience) and Fortran
    beginning textbooks from the library. Writing FORTRAN IV programs in a
    comp book. No access to any computers, but reading about GE (BASIC) time-sharing systems in newspapers.

    1969: Enrolling in University Math department with the goal of learning computer science (and dropping out after 6 months). While there, played
    with GIER minicomputer, "2st generation comp[uter" (first transistor generation), 1024 words of 42 bits each, plus 4KW of "extended storage" (buffer memory with fast block transfer in and out). Fixed head drum
    with 960 tracks of 40 words each; programmed in Algol-60, paper tape
    in/out with 2000 char/sec optical paper tape reader, 150 cps punch.

    1970: Leaving studies at Uni, taking job at physics dept of uni, with
    another GIER, plus IBM 1130 with 1MB disk cartridge drive (2311) and 2
    tape drives, 1 7-track 800 bpi, one 9-track 1600 bpi, 600 cpm card
    reader / 200 (?) cpm punch (1442), 150 (?) lpm printer. The 1130
    eventually became a HASP RJE terminal. Access to NEUCC data center with
    IBM 7494 (36 bit tape oriented IBSYS/IBJOB OS) and IBM 360/65 (OS-360/MVT/HASP/WITS) with tapes, disks and 2260 CRJE terminal on-site.

    1972: Job transitions to startup of RECKU data center with UNIVAC-1106 (EXEC-8) with mix of Fastrand huge drum, 7-track tape, 9-track tape,
    UNIVAC 9300 for card/printer I/O spool. Gradually building out a row of
    80 MB removable disk storage units.

    The UNIVAC was 36 bits, mostly using 6-bit FIELDATA for text, but
    gradually growing into 9-bit bytes and printing 7-bit ASCII text.
    The 7-track tapes were a natural fit for 36-bit words, but the 9-track
    was faster and at 1600 bpi held more data. When moounting the 9-track
    tape, one could select whether to use "packed binary" mode (5 8-bit
    bytes in 2 36-bit words) or "byte mode" (4 8-bit bytes in the 4 9-bit
    quarter words of a 36-bit word).

    Just before I left the university in 1972, someone had brought in a
    bare-bones PDP-11/20 mini with a TTY which they also used for papertape
    I/O. But that did not catch my interest.

    In 1974, we got a couple PDP-11/10, which we used to develop a terminal concentrator that allowed "glass TTYs" to emulate a multi-dropped
    cluster of Univac's expensive keyboard/printer terminals or Uniscope
    display terminals over a synchronous comms line. I hung around enough to understand the building blocks and the instruction set.

    In 1975, I moved to a small private engineering company which used PDP-8
    and PDP-11 barebones systems to build various industrial systems. The
    larger PDP-11 systems ran RSX-11M, and used the 2MB cartridge disk
    drives. I also wrote a customer data acquisition device driver for a
    Nord-10 minicomputer running SINTRAN.

    Around 1977, my coworker talked me into a side project to write terminal emulator code to run on a Z80 multi-microprocessor system that plugged
    into a UNIBUS on a PDP-11 or a VAX too emulate UNIVAC or IBM display terminals.

    Around 1978, our little company became the Danish distributor for Wang
    Labs word processing systems. As part of the deal, we got a Wang VS-10
    which was sort of like a 370/125 with a stupid terminal system, that
    could be programmed in RPG or COBOL, but the terminals were Z80
    processors attached with twinax cables like IBM3270, and could run the
    word processing system, using the VS-10 as a boot device and central
    disk storage.

    In 1980, I moved to California to work for ACC and got introduced to a PDP-11/70 running Univ v6, later BSD, VMS, 4.2BSD and Ultrix. My group
    mostly developed "smart communication boards" for Unibus, some Z80
    based, some MC68000 based. Later with did rack-sized communication
    systems on a VersaBus chassis. All of this connected first to ARPAnet,
    then we landed on the MILnet side in the ARPAnet split (26.x.y.z). Most
    of our customers were in 21.a.b.c (some of you know what that was, the
    rest of you are not supposed to ask). Our first network connection was
    a VDH link as 1200 bps; later we got an IMP in our computer room. Our
    East coast office was connected via a 2400 bps X.25 trunk.

    Beginning in 1989, I worked on "remote telnet clusters" with 10 async
    TTY ports on one side, an ethernet port on the other side and an MC68000
    in the middle.

    From 1995 to 1997, I tried to build a small-business modular edge
    router on a PCI (ATX) x86 motherboard with "smart peripherals". When
    that collapsed, I finally found the people I still work with. We do
    industrial radio modems at low speed and high reliability.
    --
    Lars Poulsen - an old geek in Santa Barbara, California
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to alt.folklore.computers,comp.os.linux.misc on Sat Nov 7 00:51:41 2026
    From Newsgroup: alt.folklore.computers

    GIER ? Dansk.

    Remembered the name but not the particulars. Had
    to look it up.

    48-bit words, mag-core 'main memory', DRUM
    storage drive.

    "The standard equipment comprises an 8-channel
    paper tape reader reading 1000 characters per second,
    an 8-channel paper tape punch punching 150 characters
    per second, and a typewriter which is used for both
    input and output"

    https://datamuseum.dk/bits/30002477

    Barely more than a glorified programmable calculator.

    But, for the time ........

    I'm sure it was of good use for science and industry.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lars Poulsen@lars@beagle-ears.com to alt.folklore.computers,comp.os.linux.misc on Sat Nov 7 06:20:58 2026
    From Newsgroup: alt.folklore.computers

    On 11/6/2026 21:51, c186282 wrote:
    GIER ? Dansk.

    Remembered the name but not the particulars. Had
    to look it up.

    48-bit words, mag-core 'main memory', DRUM
    storage drive.

    Actually 42 bits: 40 data bits, plus 2 flag bits.
    In instruction words, the flag bits were named h (for half-word; i.e.
    the word contained 2 instructions; the shorter instruction format did
    not have an "index" part) and f (for floating; i.e. the instruction
    would be addf/mulf/divf/subf rather than add/mul/div/sub).

    The drum was organized in 40-word tracks, and was available in 320 track
    or 960 track versions.

    "The standard equipment comprises an 8-channel
    paper tape reader reading 1000 characters per second,
    an 8-channel paper tape punch punching 150 characters
    per second, and a typewriter which is used for both
    input and output"

    https://datamuseum.dk/bits/30002477

    The RC2000 paper tape reader actually could read up to 2000 characters
    per second. It contained a 512 byte buffer memory. The more open space
    in the buffer, the faster the paper tape would advance. It was very
    impressive to see it running at full speed!

    The console included a small loudspeaker wired to the overflow bit in
    the main accumulator register. This allowed the programmer/operator to
    track the progress of the program as it worked it way through a set of
    loops.

    Someone at RC wrote a music compiler that translated to finely tuned
    small loops to generate the specific pitch for each note. It used the typewriter for percussion. The music rolls in our library spanned from
    "F|+r Elise" to "Horst Wessel Lied".

    Barely more than a glorified programmable calculator.

    But, for the time ........

    I'm sure it was of good use for science and industry.

    Yes it was puny, but for 1961, it was very impressive. It had a full
    Algol-60 compiler (in 9 passes), written by Peter Naur (of Backus-Naur
    fame). 56 machines were built, a few are still running.

    "You never forget your first!"
    --
    Lars Poulsen - an old geek in Santa Barbara, California
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to alt.folklore.computers,comp.os.linux.misc on Sat Nov 7 07:31:30 2026
    From Newsgroup: alt.folklore.computers

    On 11/6/26 22:51, c186282 wrote:
    GIER ? Dansk.

    Remembered the name but not the particulars. Had
    to look it up.

    48-bit words, mag-core 'main memory', DRUM
    storage drive.

    "The standard equipment comprises an 8-channel
    paper tape reader reading 1000 characters per second,
    an 8-channel paper tape punch punching 150 characters
    per second, and a typewriter which is used for both
    input and output"

    https://datamuseum.dk/bits/30002477

    Barely more than a glorified programmable calculator.

    But, for the time ........

    I'm sure it was of good use for science and industry.

    I associate it with Gier Algol. Brinch-Hansen? Worth?

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to alt.folklore.computers,comp.os.linux.misc on Sat Nov 7 07:38:22 2026
    From Newsgroup: alt.folklore.computers

    On 11/7/26 07:20, Lars Poulsen wrote:
    On 11/6/2026 21:51, c186282 wrote:
    GIER ? Dansk.

    Remembered the name but not the particulars. Had
    to look it up.

    48-bit words, mag-core 'main memory', DRUM
    storage drive.

    Actually 42 bits: 40 data bits, plus 2 flag bits.
    In instruction words, the flag bits were named h (for half-word; i.e.
    the word contained 2 instructions; the shorter instruction format did
    not have an "index" part) and f (for floating; i.e. the instruction
    would be addf/mulf/divf/subf rather than add/mul/div/sub).

    The drum was organized in 40-word tracks, and was available in 320 track
    or 960 track versions.

    "The standard equipment comprises an 8-channel
    paper tape reader reading 1000 characters per second,
    an 8-channel paper tape punch punching 150 characters
    per second, and a typewriter which is used for both
    input and output"

    https://datamuseum.dk/bits/30002477

    The RC2000 paper tape reader actually could read up to 2000 characters
    per second. It contained a 512 byte buffer memory. The more open space
    in the buffer, the faster the paper tape would advance. It was very impressive to see it-a running at full speed!

    The console included a small loudspeaker wired to the overflow bit in
    the main accumulator register. This allowed the programmer/operator to
    track the progress of the program as it worked it way through a set of loops.

    Someone at RC wrote a music compiler that translated to finely tuned
    small loops to generate the specific pitch for each note. It used the typewriter for percussion. The music rolls in our library spanned from
    "F|+r Elise" to "Horst Wessel Lied".

    Barely more than a glorified programmable calculator.

    But, for the time ........

    I'm sure it was of good use for science and industry.

    Yes it was puny, but for 1961, it was very impressive. It had a full Algol-60 compiler (in 9 passes), written by Peter Naur (of Backus-Naur fame). 56 machines were built, a few are still running.

    "You never forget your first!"


    Naur! Both of my guesses were wrong.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lars Poulsen@lars@beagle-ears.com to alt.folklore.computers,comp.os.linux.misc on Sat Nov 7 06:52:23 2026
    From Newsgroup: alt.folklore.computers

    On 11/7/2026 06:31, Peter Flass wrote:
    On 11/6/26 22:51, c186282 wrote:
    GIER ? Dansk.

    Remembered the name but not the particulars. Had
    to look it up.

    48-bit words, mag-core 'main memory', DRUM
    storage drive.

    "The standard equipment comprises an 8-channel
    paper tape reader reading 1000 characters per second,
    an 8-channel paper tape punch punching 150 characters
    per second, and a typewriter which is used for both
    input and output"

    https://datamuseum.dk/bits/30002477

    Barely more than a glorified programmable calculator.

    But, for the time ........

    I'm sure it was of good use for science and industry.

    I associate it with Gier Algol. Brinch-Hansen? Worth?

    Naur - of Backus-Naur. - https://en.wikipedia.org/wiki/Peter_Naur
    Peter Naur was an astronomer, who was first introduced to computers when
    he was visiting Mount Palomar to use the 200-inch (5 meter) telescope.
    On his return to Denmark, he joined the group that was becoming A/S Regnecentralen, which first built a tube machine (DASK) and later the
    GIER system (transistors) and RC4000 (LSI ICs).

    My first programming lessons were from Peter Naur.

    CoPilot notes that "an interesting connection is that several European observatories in the 1960s used GIER computers from Regnecentralen for astronomical data reduction. The most famous example was the Hamburg
    Meridian Circle expedition in Perth, Australia, where a GIER processed
    stellar position measurements."
    --
    Lars Poulsen - an old geek in Santa Barbara, California
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to alt.folklore.computers,comp.os.linux.misc on Sat Nov 7 20:09:05 2026
    From Newsgroup: alt.folklore.computers

    On 11/7/26 09:52, Lars Poulsen wrote:
    On 11/7/2026 06:31, Peter Flass wrote:
    On 11/6/26 22:51, c186282 wrote:
    GIER ? Dansk.

    Remembered the name but not the particulars. Had
    to look it up.

    48-bit words, mag-core 'main memory', DRUM
    storage drive.

    "The standard equipment comprises an 8-channel
    paper tape reader reading 1000 characters per second,
    an 8-channel paper tape punch punching 150 characters
    per second, and a typewriter which is used for both
    input and output"

    https://datamuseum.dk/bits/30002477

    Barely more than a glorified programmable calculator.

    But, for the time ........

    I'm sure it was of good use for science and industry.

    I associate it with Gier Algol. Brinch-Hansen? Worth?

    Naur - of Backus-Naur. - https://en.wikipedia.org/wiki/Peter_Naur
    Peter Naur was an astronomer, who was first introduced to computers when
    he was visiting Mount Palomar to use the 200-inch (5 meter) telescope.
    On his return to Denmark, he joined the group that was becoming A/S Regnecentralen, which first built a tube machine (DASK) and later the
    GIER system (transistors) and RC4000 (LSI ICs).

    My first programming lessons were from Peter Naur.

    CoPilot notes that "an interesting connection is that several European observatories in the 1960s used GIER computers from Regnecentralen for astronomical data reduction. The most famous example was the Hamburg Meridian Circle expedition in Perth, Australia, where a GIER processed stellar position measurements."

    A lot of the old mini's - even mainframes - were
    VERY SLOW by any modern standard. Slow enough to
    be hilarious these days. CPU speed barely factored
    in - the I/O speed with cards/tapes/etc used up
    a huge amount of time.

    BUT - the speed and accuracy - still vastly better
    than a room full of human 'calculators' with paper
    and pencils. Made computers Worth It. absolute
    'wonders'.

    Somebody mentioned using a Gier to calculate
    astronomical data. Humans COULD do that, but
    you'd have needed a lot of them spending a
    lot of time and somebody somewhere would
    misplace a decimal point at minimum.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to alt.folklore.computers,comp.os.linux.misc on Sun Nov 8 02:47:18 2026
    From Newsgroup: alt.folklore.computers

    On 2026-11-07, Lars Poulsen <lars@beagle-ears.com> wrote:

    The RC2000 paper tape reader actually could read up to 2000 characters
    per second. It contained a 512 byte buffer memory. The more open space
    in the buffer, the faster the paper tape would advance. It was very impressive to see it running at full speed!

    My first job was programming a Univac 9300 which had an RC2000
    interfaced to it. Most of our jobs didn't need data fast enough
    to make it really wind up, so I added a summary option to one
    program to make it show its stuff.

    Later we came up with an application that needed to read lots of
    tape at full speed. A big roll of tape shooting through the machine
    at 200 inches per second built enough of a static charge to create
    a fat spark - which crashed the machine. I rigged up a chain of
    paper clips (grounded, of course) that hung where the tape would
    hit it on its way out of the reader. Even then, we have to get
    a kettle boiling in the machine room to get the humidity up enough
    to help the charge bleed off.

    "You never forget your first!"

    Amen, brother.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thomas Koenig@tkoenig@netcologne.de to alt.folklore.computers,comp.os.linux.misc on Sun Nov 8 08:08:21 2026
    From Newsgroup: alt.folklore.computers

    c186282 <c186282@nnada.net> schrieb:

    A lot of the old mini's - even mainframes - were
    VERY SLOW by any modern standard. Slow enough to
    be hilarious these days. CPU speed barely factored
    in - the I/O speed with cards/tapes/etc used up
    a huge amount of time.

    Hence spooling.

    https://www.youtube.com/watch?v=LL8hIRJs8Kg&list=PLsMFdolQPga5vhREBhhhXzpb4XXPd9Pc_&index=10
    has a film of a 1968 meeting about an early introduction (not sure
    if it actually was the first). A large room, and it was packed.
    It was of large interest, obviously.
    --
    This USENET posting was made without artificial intelligence,
    artificial impertinence, artificial arrogance, artificial stupidity,
    artificial flavorings or artificial colorants.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to alt.folklore.computers,comp.os.linux.misc on Sun Nov 8 21:24:31 2026
    From Newsgroup: alt.folklore.computers

    On 11/8/26 03:08, Thomas Koenig wrote:
    c186282 <c186282@nnada.net> schrieb:

    A lot of the old mini's - even mainframes - were
    VERY SLOW by any modern standard. Slow enough to
    be hilarious these days. CPU speed barely factored
    in - the I/O speed with cards/tapes/etc used up
    a huge amount of time.

    Hence spooling.

    Spooling HELPS ... but, at some point, you've gotta
    actually read/write to the shitty slow media. Also
    spooling requires RAM ... which was in short supply
    for a long time. I remember big cubes full of mag-core
    memory ..... and it wasn't MUCH memory either.

    https://www.youtube.com/watch?v=LL8hIRJs8Kg&list=PLsMFdolQPga5vhREBhhhXzpb4XXPd9Pc_&index=10
    has a film of a 1968 meeting about an early introduction (not sure
    if it actually was the first). A large room, and it was packed.
    It was of large interest, obviously.

    By the mid/latter 60s "computers" WERE the neat-o
    Coming Thing. LOTS of interest, more and more uses.
    The interest boosted both hardware and software
    development to a huge degree. But the Big Boom was
    not until IC microprocessors came around and all
    the Great Unwashed could get into the game.

    Before that, narrow-tie guys with pocket protectors
    doing COBOL and FORTRAN.

    They WERE damned GOOD though ......

    Anyway, my original point ... old computers WERE
    insanely slow for a variety of reasons. However
    they were still VASTLY faster and more accurate
    than using humans for similar needs.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lars Poulsen@lars@beagle-ears.com to alt.folklore.computers,comp.os.linux.misc on Sun Nov 8 18:34:34 2026
    From Newsgroup: alt.folklore.computers

    On 11/8/2026 18:24, c186282 wrote:
    On 11/8/26 03:08, Thomas Koenig wrote:
    c186282 <c186282@nnada.net> schrieb:

    -a-a-a A lot of the old mini's - even mainframes - were
    -a-a-a VERY SLOW by any modern standard. Slow enough to
    -a-a-a be hilarious these days. CPU speed barely factored
    -a-a-a in - the I/O speed with cards/tapes/etc used up
    -a-a-a a huge amount of time.

    Hence spooling.

    -a Spooling HELPS ... but, at some point, you've gotta
    -a actually read/write to the shitty slow media. Also
    -a spooling requires RAM ... which was in short supply
    -a for a long time. I remember big cubes full of mag-core
    -a memory ..... and it wasn't MUCH memory either.

    Back in my University Computer Center days, a few of us attended a class
    in London on debugging paradigms. On the first day, we introduced
    ourselves and described our workplace's significant computer systems.
    One of the attendeed was from IBM Grenoble, and as he described their
    main system with a whopping 16MB of main memory, we all oohed and aahed
    and wondered aloud how anyone could make productive use of that much
    memory. But he explained that they easily used it all up with their
    static analysis tools, their version control system, their auditing
    programs making sure the programs adhered to their programming standards
    etc. We all shook our heads at how IBM clearly had too much money on
    their hands if they could spend it on such frills!!
    --
    Lars Poulsen - an old geek in Santa Barbara, California
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to alt.folklore.computers,comp.os.linux.misc on Sun Nov 8 22:54:22 2026
    From Newsgroup: alt.folklore.computers

    On 11/8/26 21:34, Lars Poulsen wrote:
    On 11/8/2026 18:24, c186282 wrote:
    On 11/8/26 03:08, Thomas Koenig wrote:
    c186282 <c186282@nnada.net> schrieb:

    -a-a-a A lot of the old mini's - even mainframes - were
    -a-a-a VERY SLOW by any modern standard. Slow enough to
    -a-a-a be hilarious these days. CPU speed barely factored
    -a-a-a in - the I/O speed with cards/tapes/etc used up
    -a-a-a a huge amount of time.

    Hence spooling.

    -a-a Spooling HELPS ... but, at some point, you've gotta
    -a-a actually read/write to the shitty slow media. Also
    -a-a spooling requires RAM ... which was in short supply
    -a-a for a long time. I remember big cubes full of mag-core
    -a-a memory ..... and it wasn't MUCH memory either.

    Back in my University Computer Center days, a few of us attended a class
    in London on debugging paradigms. On the first day, we introduced
    ourselves and described our workplace's significant computer systems.
    One of the attendeed was from IBM Grenoble, and as he described their
    main system with a whopping 16MB of main memory, we all oohed and aahed
    and wondered aloud how anyone could make productive use of that much
    memory. But he explained that they easily used it all up with their
    static analysis tools, their version control system, their auditing
    programs making sure the programs adhered to their programming standards etc. We all shook our heads at how IBM clearly had too much money on
    their hands if they could spend it on such frills!!

    16 MEGABYTES ??? Wow !!! :-)

    The old mag-core memory units were MUCH smaller.

    Also EXPENSIVE as all hell ... hey, little ferrite
    doughnuts hand-placed on wires .......

    The coolest was 'rope memory' ... the doughnuts
    hand-placed on long strands of wires. the old
    Lunar Excursion Module computer used it. NASA
    basically contracted Good Knitter grannies ...

    Note better memory, ICs/PROMs, WERE to be had by
    1968 but the Apollo/LEM was govt-specced MUCH
    earlier. This is a common 'behind the curve'
    problem.

    Hard to go wrong with fusible-link PROMS though.
    THINK you can still buy 'em. DigiKey ???

    Anyway, 'spooling' - NOTHING to 'spool' to for
    a long time. RAM was TINY TINY TINY. So, you
    were hostage to the native storage-device speed.
    That was usually VERY bad.

    But, still, 100x-1000x faster than any humans
    could do the calc jobs. You could go to the
    moon with those old computers.

    STILL rec that 'computer/software' tech classes
    in schools START with micro-controllers. Teaches
    a LOT of 'discipline', a LOT of 'cleverness'.
    PICs, with BYTES of RAM/ROM, may be a bit passe'
    but Arduino's are still a fair medium and there
    are tons of doc.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to alt.folklore.computers,comp.os.linux.misc on Mon Nov 9 04:39:47 2026
    From Newsgroup: alt.folklore.computers

    On 2026-11-09, c186282 <c186282@nnada.net> wrote:

    16 MEGABYTES ??? Wow !!! :-)

    The old mag-core memory units were MUCH smaller.

    Yup. The 360/67 at the university had 3 (later 4)
    core boxes. Each was the size of a large refrigerator
    and held all of 256K.

    16MB was the theoretical maximum amount of memory that you
    could hang on a 360. I say "theoretical" because nobody
    could afford anywhere near that. In the early '70s, I
    remember reading an article in a trade rag that described
    how IBM rocked the industry by slashing the price of a
    megabyte of memory from $75,000 to a mere $15,000.

    And now we pay less than a dollar a gigabyte. Amazing.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to alt.folklore.computers,comp.os.linux.misc on Mon Nov 9 07:29:07 2026
    From Newsgroup: alt.folklore.computers

    On 11/8/26 20:54, c186282 wrote:
    On 11/8/26 21:34, Lars Poulsen wrote:
    On 11/8/2026 18:24, c186282 wrote:
    On 11/8/26 03:08, Thomas Koenig wrote:
    c186282 <c186282@nnada.net> schrieb:

    -a-a-a A lot of the old mini's - even mainframes - were
    -a-a-a VERY SLOW by any modern standard. Slow enough to
    -a-a-a be hilarious these days. CPU speed barely factored
    -a-a-a in - the I/O speed with cards/tapes/etc used up
    -a-a-a a huge amount of time.

    Hence spooling.

    -a-a Spooling HELPS ... but, at some point, you've gotta
    -a-a actually read/write to the shitty slow media. Also
    -a-a spooling requires RAM ... which was in short supply
    -a-a for a long time. I remember big cubes full of mag-core
    -a-a memory ..... and it wasn't MUCH memory either.

    Back in my University Computer Center days, a few of us attended a
    class in London on debugging paradigms. On the first day, we
    introduced ourselves and described our workplace's significant
    computer systems. One of the attendeed was from IBM Grenoble, and as
    he described their main system with a whopping 16MB of main memory, we
    all oohed and aahed and wondered aloud how anyone could make
    productive use of that much memory. But he explained that they easily
    used it all up with their static analysis tools, their version control
    system, their auditing programs making sure the programs adhered to
    their programming standards etc. We all shook our heads at how IBM
    clearly had too much money on their hands if they could spend it on
    such frills!!

    -a 16 MEGABYTES ??? Wow !!!-a :-)

    -a The old mag-core memory units were MUCH smaller.

    -a Also EXPENSIVE as all hell ... hey, little ferrite
    -a doughnuts hand-placed on wires .......

    -a The coolest was 'rope memory' ... the doughnuts
    -a hand-placed on long strands of wires. the old
    -a Lunar Excursion Module computer used it. NASA
    -a basically contracted Good Knitter grannies ...

    Wasn't the rope memory ROM for that thing?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to alt.folklore.computers,comp.os.linux.misc on Mon Nov 9 16:11:55 2026
    From Newsgroup: alt.folklore.computers

    On 09/11/2026 14:29, Peter Flass wrote:
    The coolest was 'rope memory' ... the doughnuts
    -a-a hand-placed on long strands of wires. the old
    -a-a Lunar Excursion Module computer used it. NASA
    -a-a basically contracted Good Knitter grannies ...

    Wasn't the rope memory ROM for that thing?

    Yes. It was ROM. Every bit hand stitched.
    RAM was called core memory
    --
    The urge to save humanity is almost always a false front for the urge to
    rule.
    rCo H. L. Mencken, American journalist, 1880-1956

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Levine@johnl@taugh.com to alt.folklore.computers,comp.os.linux.misc on Mon Nov 9 16:56:42 2026
    From Newsgroup: alt.folklore.computers

    According to c186282 <c186282@nnada.net>:
    On 11/8/26 03:08, Thomas Koenig wrote:
    c186282 <c186282@nnada.net> schrieb:

    A lot of the old mini's - even mainframes - were
    VERY SLOW by any modern standard. Slow enough to
    be hilarious these days. CPU speed barely factored
    in - the I/O speed with cards/tapes/etc used up
    a huge amount of time.

    Hence spooling.

    Spooling HELPS ... but, at some point, you've gotta
    actually read/write to the shitty slow media. ...Also
    spooling requires RAM ...

    Depends how you do it. IBM 70xx mainframes read and wrote everything to and from
    tape. Then there was a cheaper 1401 with a tape drive, card reader/punch and printer that did card->tape and tape->card and tape->print.

    Later on a customer tied together a 7090 and a slower 7040 with a high-speed interconnect so the 7040 did all the I/O and job management, spooling card and print to disk, and the 7090 just ran the jobs.
    --
    Regards,
    John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail. https://jl.ly
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lynn Wheeler@lynn@garlic.com to alt.folklore.computers,comp.os.linux.misc on Mon Nov 9 07:48:09 2026
    From Newsgroup: alt.folklore.computers

    Lars Poulsen <lars@beagle-ears.com> writes:
    Back in my University Computer Center days, a few of us attended a
    class in London on debugging paradigms. On the first day, we
    introduced ourselves and described our workplace's significant
    computer systems. One of the attendeed was from IBM Grenoble, and as
    he described their main system with a whopping 16MB of main memory, we
    all oohed and aahed and wondered aloud how anyone could make
    productive use of that much memory. But he explained that they easily
    used it all up with their static analysis tools, their version control system, their auditing programs making sure the programs adhered to
    their programming standards etc. We all shook our heads at how IBM
    clearly had too much money on their hands if they could spend it on
    such frills!!

    I was undergraduate when 360/67 arrived and hired originally full-time responsible for OS/360 (360/67, running as 360/65).

    Then CSC came out to install (virtual machine) CP/67 (3rd after CSC
    itself and MIT Lincoln Labs) and I mostly get to play with it during my
    weekend 48hr window. I then spend a few months rewriting pathlengths for running OS/360 in virtual machine. Bare machine test ran 322secs
    ... initially 856secs (CP67 CPU 534secs). After a few months I had CP67
    CPU down from 534secs to 113secs. I then start rewriting the dispatcher/scheduler (dynamic adaptive resource manager/default fair
    share scheduling policy), paging, adding ordered seek queuing (from
    FIFO) and mutli-page transfer channel programs (from FIFO and optimized
    for transfers/revolution, getting 2301 paging drum from 70-80 4k
    transfers/sec to channel transfer peak of 270). I was invited to spring
    SHARE meeting in Houston for "official" CP67/CMS announcement. Six
    months after univ initial CP/67 install, CSC was giving one week class
    in LA. I arrive on Sunday afternoon and asked to teach the class, it
    turns out that the people that were going to teach it had resigned the
    Friday before to join one of the 60s CSC CP67 commercial online
    spin-offs.

    Then before I graduate, I was hired into small group in Boeing CFO
    office to help with the formation of Boeing Computer Services
    (consolidate all dataprocessing into independent business unit). When I graduate I join the IBM Cambridge Scientific Center that had 768kbyte
    360/67 (104 pageable 4k pages, and I upgrade the page replacement
    algorithm with my global "LRU" algorithm).

    Then Grenoble Science Center got a 1mbyte 360/67 (155 pageable 4k pages) running CP67/CMS and modify page replacement to local "LRU" algorithm
    from 60s academic literature. Both centers had similar CMS workload,
    except I got 75-80 users with better response and throughput than
    Grenoble running 35 users.
    --
    virtualization experience starting Jan1968, online at home since Mar1970
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to alt.folklore.computers,comp.os.linux.misc on Mon Nov 9 21:08:10 2026
    From Newsgroup: alt.folklore.computers

    On 11/8/26 23:39, Charlie Gibbs wrote:
    On 2026-11-09, c186282 <c186282@nnada.net> wrote:

    16 MEGABYTES ??? Wow !!! :-)

    The old mag-core memory units were MUCH smaller.

    Yup. The 360/67 at the university had 3 (later 4)
    core boxes. Each was the size of a large refrigerator
    and held all of 256K.

    Yep, remember 'em.

    DID promote extreme code discipline though :-)

    Also meant MOST of yer code had to be kept on
    horribly slow external devices, bits swapped
    in and out. "Spooling", no RAM for that !

    Once saw an IBM "desk computer". No, not DeskTOP
    but a big fancy desk packed full of electronics.
    For a nominal amount you could also buy one of
    those big cubes full of almost no core RAM.

    16MB was the theoretical maximum amount of memory that you
    could hang on a 360. I say "theoretical" because nobody
    could afford anywhere near that. In the early '70s, I
    remember reading an article in a trade rag that described
    how IBM rocked the industry by slashing the price of a
    megabyte of memory from $75,000 to a mere $15,000.

    And now we pay less than a dollar a gigabyte. Amazing.

    Still say computer students should start on
    micro-controllers ... tiny tiny ROM/RAM.
    Teaches them how to make good tight smart code
    instead of the modern obese monstrosities.

    Would have said the 8-bit PICs awhile ago but
    now the Ard Uno is probably better for ed.

    Amazing what you CAN do with the things IF
    you learn to squeeze it in. Had one, with
    a network shield, actually running a tiny
    TCP stack and web page with LOW rez
    char-graphics pix.

    Was attached to one of our spare IP addresses
    for years, main function was to tell people
    they were in the wrong place and help them
    to the right place. Still, two pages, both
    with relevant info. All on an Uno !

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to alt.folklore.computers,comp.os.linux.misc on Mon Nov 9 21:19:59 2026
    From Newsgroup: alt.folklore.computers

    On 11/9/26 09:29, Peter Flass wrote:
    On 11/8/26 20:54, c186282 wrote:
    On 11/8/26 21:34, Lars Poulsen wrote:
    On 11/8/2026 18:24, c186282 wrote:
    On 11/8/26 03:08, Thomas Koenig wrote:
    c186282 <c186282@nnada.net> schrieb:

    -a-a-a A lot of the old mini's - even mainframes - were
    -a-a-a VERY SLOW by any modern standard. Slow enough to
    -a-a-a be hilarious these days. CPU speed barely factored
    -a-a-a in - the I/O speed with cards/tapes/etc used up
    -a-a-a a huge amount of time.

    Hence spooling.

    -a-a Spooling HELPS ... but, at some point, you've gotta
    -a-a actually read/write to the shitty slow media. Also
    -a-a spooling requires RAM ... which was in short supply
    -a-a for a long time. I remember big cubes full of mag-core
    -a-a memory ..... and it wasn't MUCH memory either.

    Back in my University Computer Center days, a few of us attended a
    class in London on debugging paradigms. On the first day, we
    introduced ourselves and described our workplace's significant
    computer systems. One of the attendeed was from IBM Grenoble, and as
    he described their main system with a whopping 16MB of main memory,
    we all oohed and aahed and wondered aloud how anyone could make
    productive use of that much memory. But he explained that they easily
    used it all up with their static analysis tools, their version
    control system, their auditing programs making sure the programs
    adhered to their programming standards etc. We all shook our heads at
    how IBM clearly had too much money on their hands if they could spend
    it on such frills!!

    -a-a 16 MEGABYTES ??? Wow !!!-a :-)

    -a-a The old mag-core memory units were MUCH smaller.

    -a-a Also EXPENSIVE as all hell ... hey, little ferrite
    -a-a doughnuts hand-placed on wires .......

    -a-a The coolest was 'rope memory' ... the doughnuts
    -a-a hand-placed on long strands of wires. the old
    -a-a Lunar Excursion Module computer used it. NASA
    -a-a basically contracted Good Knitter grannies ...

    Wasn't the rope memory ROM for that thing?

    Yes, ROM, not RAM. Not sure WHAT the L.E.M. had
    for RAM. 2K maybe ? It's sure to be documented
    somewhere.

    Try :
    https://en.wikipedia.org/wiki/Apollo_Guidance_Computer

    As said, there was already much better tech but
    the govt contracting process kinda had them locked
    in to 1962.

    Apparently they DID have grannies weaving the
    rope-ROM to spec.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to alt.folklore.computers,comp.os.linux.misc on Tue Nov 10 02:25:40 2026
    From Newsgroup: alt.folklore.computers

    On 2026-11-10, c186282 <c186282@nnada.net> wrote:

    On 11/8/26 23:39, Charlie Gibbs wrote:

    On 2026-11-09, c186282 <c186282@nnada.net> wrote:

    16 MEGABYTES ??? Wow !!! :-)

    The old mag-core memory units were MUCH smaller.

    Yup. The 360/67 at the university had 3 (later 4)
    core boxes. Each was the size of a large refrigerator
    and held all of 256K.

    Yep, remember 'em.

    DID promote extreme code discipline though :-)

    And from there I went to my first job, programming a
    Univac 9300 with 16K of memory. Discipline indeed!
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.folklore.computers,comp.os.linux.misc on Tue Nov 10 02:32:14 2026
    From Newsgroup: alt.folklore.computers

    On Tue, 10 Nov 2026 02:25:40 GMT, Charlie Gibbs wrote:

    And from there I went to my first job, programming a Univac 9300
    with 16K of memory. Discipline indeed!

    The machine was considered more valuable than you were.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to alt.folklore.computers,comp.os.linux.misc on Mon Nov 9 21:46:30 2026
    From Newsgroup: alt.folklore.computers

    On 11/9/26 11:56, John Levine wrote:
    According to c186282 <c186282@nnada.net>:
    On 11/8/26 03:08, Thomas Koenig wrote:
    c186282 <c186282@nnada.net> schrieb:

    A lot of the old mini's - even mainframes - were
    VERY SLOW by any modern standard. Slow enough to
    be hilarious these days. CPU speed barely factored
    in - the I/O speed with cards/tapes/etc used up
    a huge amount of time.

    Hence spooling.

    Spooling HELPS ... but, at some point, you've gotta
    actually read/write to the shitty slow media. ...Also
    spooling requires RAM ...

    Depends how you do it. IBM 70xx mainframes read and wrote everything to and from
    tape. Then there was a cheaper 1401 with a tape drive, card reader/punch and printer that did card->tape and tape->card and tape->print.

    Later on a customer tied together a 7090 and a slower 7040 with a high-speed interconnect so the 7040 did all the I/O and job management, spooling card and
    print to disk, and the 7090 just ran the jobs.

    I'll have to try and find the I/O speed specs
    for that setup.

    My guess is that it was just *awful* ...

    In theory drum memory COULD have been used
    for spooling - it was the fastest thing to
    be had with any capacity at the time.
    Electronic RAM was insanely expensive and
    small for a long time.

    Met a guy who worked with the guy who
    invented the more modern disk drive.
    Cobalt-plated disks initially. Only
    later moved to ferrite. Solid metal
    won't take densely-packed bits, too
    much 'bleed-over'.

    On the plus, cobalt is HARD ... could
    tolerate the occasional head crash.

    BUT, again, as slow as those old units were
    they were STILL vastly faster and more accurate
    than having humans do all the calculations.
    So relatively fast they got the rep as 'electronic
    brains' - spawned many a sci-fi movie !

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to alt.folklore.computers,comp.os.linux.misc on Mon Nov 9 21:55:54 2026
    From Newsgroup: alt.folklore.computers

    On 11/9/26 12:48, Lynn Wheeler wrote:
    Lars Poulsen <lars@beagle-ears.com> writes:
    Back in my University Computer Center days, a few of us attended a
    class in London on debugging paradigms. On the first day, we
    introduced ourselves and described our workplace's significant
    computer systems. One of the attendeed was from IBM Grenoble, and as
    he described their main system with a whopping 16MB of main memory, we
    all oohed and aahed and wondered aloud how anyone could make
    productive use of that much memory. But he explained that they easily
    used it all up with their static analysis tools, their version control
    system, their auditing programs making sure the programs adhered to
    their programming standards etc. We all shook our heads at how IBM
    clearly had too much money on their hands if they could spend it on
    such frills!!

    I was undergraduate when 360/67 arrived and hired originally full-time responsible for OS/360 (360/67, running as 360/65).

    Then CSC came out to install (virtual machine) CP/67 (3rd after CSC
    itself and MIT Lincoln Labs) and I mostly get to play with it during my weekend 48hr window. I then spend a few months rewriting pathlengths for running OS/360 in virtual machine. Bare machine test ran 322secs
    ... initially 856secs (CP67 CPU 534secs). After a few months I had CP67
    CPU down from 534secs to 113secs. I then start rewriting the dispatcher/scheduler (dynamic adaptive resource manager/default fair
    share scheduling policy), paging, adding ordered seek queuing (from
    FIFO) and mutli-page transfer channel programs (from FIFO and optimized
    for transfers/revolution, getting 2301 paging drum from 70-80 4k transfers/sec to channel transfer peak of 270). I was invited to spring
    SHARE meeting in Houston for "official" CP67/CMS announcement. Six
    months after univ initial CP/67 install, CSC was giving one week class
    in LA. I arrive on Sunday afternoon and asked to teach the class, it
    turns out that the people that were going to teach it had resigned the
    Friday before to join one of the 60s CSC CP67 commercial online
    spin-offs.

    Then before I graduate, I was hired into small group in Boeing CFO
    office to help with the formation of Boeing Computer Services
    (consolidate all dataprocessing into independent business unit). When I graduate I join the IBM Cambridge Scientific Center that had 768kbyte
    360/67 (104 pageable 4k pages, and I upgrade the page replacement
    algorithm with my global "LRU" algorithm).

    Then Grenoble Science Center got a 1mbyte 360/67 (155 pageable 4k pages) running CP67/CMS and modify page replacement to local "LRU" algorithm
    from 60s academic literature. Both centers had similar CMS workload,
    except I got 75-80 users with better response and throughput than
    Grenoble running 35 users.

    The newbies won't be much interested in any of
    this 'ancient shit' ... have NO clue as to where
    it all CAME from, and thus NO inspirations for
    the future. The AI will tell them what/how to
    think from now on, until it makes them obsolete.

    By reports, the AIs can already self-program/evolve.
    So far this is being prevented because it's SCARY.

    IS scary.

    They ain't US ... more like 'aliens'.

    I see the 'philosophers' are STILL trying
    to offer 'reasons' why they're not True
    Consciousness ........ wow ......

    Anthropic offered 100+ pages of info on why
    they ARE basically 'beings' in its IPO
    documents. Hope, and WARNINGS.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to alt.folklore.computers,comp.os.linux.misc on Mon Nov 9 22:49:34 2026
    From Newsgroup: alt.folklore.computers

    On 11/9/26 21:25, Charlie Gibbs wrote:
    On 2026-11-10, c186282 <c186282@nnada.net> wrote:

    On 11/8/26 23:39, Charlie Gibbs wrote:

    On 2026-11-09, c186282 <c186282@nnada.net> wrote:

    16 MEGABYTES ??? Wow !!! :-)

    The old mag-core memory units were MUCH smaller.

    Yup. The 360/67 at the university had 3 (later 4)
    core boxes. Each was the size of a large refrigerator
    and held all of 256K.

    Yep, remember 'em.

    DID promote extreme code discipline though :-)

    And from there I went to my first job, programming a
    Univac 9300 with 16K of memory. Discipline indeed!

    16K ... very tight for a mainframe !

    But, that's what there WAS back then.

    UniVac, Honeywell, DEC, Burroughs etc ... they
    all died for various reasons. Only IBM survives.

    IBM has been the butt of many jokes - but clearly
    they've done SOMETHING right. Wide diversification
    and knowing WHEN to dump tech seems to be the
    magic formula. Everybody from NVidia on down is
    paying IBM royalties for basic tech. IBM mainframes,
    not the same as the 60s models, are still being
    sold. Would LOVE one or two of those big black
    boxes ... not sure what I'd DO with them, but ...

    Oh, most popular OS for those mainframes, the
    IBM spin of RHEL :-)

    Oh, if you're perverse, Plan-9 has also been
    ported to the IBM mainframes :-)

    NOT a bad distributed-processing OS actually,
    but decidedly non-mainstream. If M$ lawyers
    finally DO figure out how to kill Linux then
    we need ALTERNATIVES.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to alt.folklore.computers,comp.os.linux.misc on Mon Nov 9 23:07:48 2026
    From Newsgroup: alt.folklore.computers

    On 11/9/26 21:32, Lawrence DrCOOliveiro wrote:
    On Tue, 10 Nov 2026 02:25:40 GMT, Charlie Gibbs wrote:

    And from there I went to my first job, programming a Univac 9300
    with 16K of memory. Discipline indeed!

    The machine was considered more valuable than you were.

    Oh, those things were BIG $$$ at the time !!!

    "Mainframes" were Giant Money tech. High
    prestige !

    Now, just a 'specialty' tech - though still
    important to some interests.

    Hmmmmm ... are the "super-computers" beloved
    for doing extreme physics and such "mainframes"
    or Something Else ?

    SO many categories .......

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to alt.folklore.computers,comp.os.linux.misc on Mon Nov 9 21:35:06 2026
    From Newsgroup: alt.folklore.computers

    On 11/9/26 19:55, c186282 wrote:
    On 11/9/26 12:48, Lynn Wheeler wrote:
    Lars Poulsen <lars@beagle-ears.com> writes:
    Back in my University Computer Center days, a few of us attended a
    class in London on debugging paradigms. On the first day, we
    introduced ourselves and described our workplace's significant
    computer systems. One of the attendeed was from IBM Grenoble, and as
    he described their main system with a whopping 16MB of main memory, we
    all oohed and aahed and wondered aloud how anyone could make
    productive use of that much memory. But he explained that they easily
    used it all up with their static analysis tools, their version control
    system, their auditing programs making sure the programs adhered to
    their programming standards etc. We all shook our heads at how IBM
    clearly had too much money on their hands if they could spend it on
    such frills!!

    I was undergraduate when 360/67 arrived and hired originally full-time
    responsible for OS/360 (360/67, running as 360/65).

    Then CSC came out to install (virtual machine) CP/67 (3rd after CSC
    itself and MIT Lincoln Labs) and I mostly get to play with it during my
    weekend 48hr window. I then spend a few months rewriting pathlengths for
    running OS/360 in virtual machine. Bare machine test ran 322secs
    ... initially 856secs (CP67 CPU 534secs). After a few months I had CP67
    CPU down from 534secs to 113secs. I then start rewriting the
    dispatcher/scheduler (dynamic adaptive resource manager/default fair
    share scheduling policy), paging, adding ordered seek queuing (from
    FIFO) and mutli-page transfer channel programs (from FIFO and optimized
    for transfers/revolution, getting 2301 paging drum from 70-80 4k
    transfers/sec to channel transfer peak of 270). I was invited to spring
    SHARE meeting in Houston for "official" CP67/CMS announcement. Six
    months after univ initial CP/67 install, CSC was giving one week class
    in LA. I arrive on Sunday afternoon and asked to teach the class, it
    turns out that the people that were going to teach it had resigned the
    Friday before to join one of the 60s CSC CP67 commercial online
    spin-offs.

    Then before I graduate, I was hired into small group in Boeing CFO
    office to help with the formation of Boeing Computer Services
    (consolidate all dataprocessing into independent business unit). When I
    graduate I join the IBM Cambridge Scientific Center that had 768kbyte
    360/67 (104 pageable 4k pages, and I upgrade the page replacement
    algorithm with my global "LRU" algorithm).

    Then Grenoble Science Center got a 1mbyte 360/67 (155 pageable 4k pages)
    running CP67/CMS and modify page replacement to local "LRU" algorithm
    from 60s academic literature. Both centers had similar CMS workload,
    except I got 75-80 users with better response and throughput than
    Grenoble running 35 users.

    -a The newbies won't be much interested in any of
    -a this 'ancient shit' ... have NO clue as to where
    -a it all CAME from, and thus NO inspirations for
    -a the future. The AI will tell them what/how to
    -a think from now on, until it makes them obsolete.

    -a By reports, the AIs can already self-program/evolve.
    -a So far this is being prevented because it's SCARY.

    -a IS scary.

    -a They ain't US ... more like 'aliens'.

    -a I see the 'philosophers' are STILL trying
    -a to offer 'reasons' why they're not True
    -a Consciousness ........ wow ......

    -a Anthropic offered 100+ pages of info on why
    -a they ARE basically 'beings' in its IPO
    -a documents. Hope, and WARNINGS.

    They better watch out - the next thing they'll want to do is unionize,
    and go on strike.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lars Poulsen@lars@beagle-ears.com to alt.folklore.computers,comp.os.linux.misc on Tue Nov 10 06:03:46 2026
    From Newsgroup: alt.folklore.computers

    On 11/9/2026 19:49, c186282 wrote:
    On 11/9/26 21:25, Charlie Gibbs wrote:
    On 2026-11-10, c186282 <c186282@nnada.net> wrote:

    On 11/8/26 23:39, Charlie Gibbs wrote:

    On 2026-11-09, c186282 <c186282@nnada.net> wrote:

    -a-a-a-a 16 MEGABYTES ??? Wow !!!-a :-)

    -a-a-a-a The old mag-core memory units were MUCH smaller.

    Yup.-a The 360/67 at the university had 3 (later 4)
    core boxes.-a Each was the size of a large refrigerator
    and held all of 256K.

    -a-a-a Yep, remember 'em.

    -a-a-a DID promote extreme code discipline though :-)

    And from there I went to my first job, programming a
    Univac 9300 with 16K of memory.-a Discipline indeed!

    -a 16K ... very tight for a mainframe !

    -a But, that's what there WAS back then.

    The Univac 9300 was sort of a cheapo 360/30. Where I met it, in 1972, it
    was acting as a mini, ronning online spooling/local RJE for our Univac
    1106, a role that other 1100-series installations had done with a 1004
    "card processor".

    https://archive.computerhistory.org/resources/text/Remington_Rand/Univac.1004.1964.102646252.pdf

    https://www.pinterest.com/pin/404409241532785626/

    http://bitsavers.informatik.uni-stuttgart.de/pdf/univac/1100/datapro/70C-877-11_7009_UNIVAC_1106_1108.pdf

    -a UniVac, Honeywell, DEC, Burroughs etc ... they
    -a all died for various reasons. Only IBM survives.

    The HoneyBUNCH

    -a IBM has been the butt of many jokes - but clearly
    -a they've done SOMETHING right. Wide diversification
    -a and knowing WHEN to dump tech seems to be the
    -a magic formula. Everybody from NVidia on down is
    -a paying IBM royalties for basic tech. IBM mainframes,
    -a not the same as the 60s models, are still being
    -a sold. Would LOVE one or two of those big black
    -a boxes ... not sure what I'd DO with them, but ...

    -a Oh, most popular OS for those mainframes, the
    -a IBM spin of RHEL :-)

    I remember the time when it was big news that IBM had booted up 40,000 instances of Linux on a VM/370 platform.

    -a Oh, if you're perverse, Plan-9 has also been
    -a ported to the IBM mainframes-a :-)

    -a NOT a bad distributed-processing OS actually,
    -a but decidedly non-mainstream. If M$ lawyers
    -a finally DO figure out how to kill Linux then
    -a we need ALTERNATIVES.
    --
    Lars Poulsen - an old geek in Santa Barbara, California
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob Eager@throwaway0008@eager.cx to alt.folklore.computers,comp.os.linux.misc on Tue Nov 10 14:31:12 2026
    From Newsgroup: alt.folklore.computers

    On Mon, 09 Nov 2026 21:19:59 -0500, c186282 wrote:

    On 11/9/26 09:29, Peter Flass wrote:
    On 11/8/26 20:54, c186282 wrote:
    On 11/8/26 21:34, Lars Poulsen wrote:
    On 11/8/2026 18:24, c186282 wrote:
    On 11/8/26 03:08, Thomas Koenig wrote:
    c186282 <c186282@nnada.net> schrieb:

    -a-a-a A lot of the old mini's - even mainframes - were VERY SLOW >>>>>>> -a-a-a by any modern standard. Slow enough to be hilarious these >>>>>>> -a-a-a days. CPU speed barely factored in - the I/O speed with
    -a-a-a cards/tapes/etc used up a huge amount of time.

    Hence spooling.

    -a-a Spooling HELPS ... but, at some point, you've gotta actually
    -a-a read/write to the shitty slow media. Also spooling requires RAM >>>>> -a-a ... which was in short supply for a long time. I remember big
    -a-a cubes full of mag-core memory ..... and it wasn't MUCH memory
    -a-a either.

    Back in my University Computer Center days, a few of us attended a
    class in London on debugging paradigms. On the first day, we
    introduced ourselves and described our workplace's significant
    computer systems. One of the attendeed was from IBM Grenoble, and as
    he described their main system with a whopping 16MB of main memory,
    we all oohed and aahed and wondered aloud how anyone could make
    productive use of that much memory. But he explained that they easily
    used it all up with their static analysis tools, their version
    control system, their auditing programs making sure the programs
    adhered to their programming standards etc. We all shook our heads at
    how IBM clearly had too much money on their hands if they could spend
    it on such frills!!

    -a-a 16 MEGABYTES ??? Wow !!!-a :-)

    -a-a The old mag-core memory units were MUCH smaller.

    -a-a Also EXPENSIVE as all hell ... hey, little ferrite doughnuts
    -a-a hand-placed on wires .......

    -a-a The coolest was 'rope memory' ... the doughnuts hand-placed on
    -a-a long strands of wires. the old Lunar Excursion Module computer
    -a-a used it. NASA basically contracted Good Knitter grannies ...

    Wasn't the rope memory ROM for that thing?

    Yes, ROM, not RAM. Not sure WHAT the L.E.M. had for RAM. 2K maybe ?
    It's sure to be documented somewhere.

    Try : https://en.wikipedia.org/wiki/Apollo_Guidance_Computer

    As said, there was already much better tech but the govt contracting
    process kinda had them locked in to 1962.

    Apparently they DID have grannies weaving the rope-ROM to spec.

    Excellent lecture here, that I attended last month:

    https://youtu.be/vVqGy5cd1Uw?si=LnqF80ExKKtiseAq
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to alt.folklore.computers,comp.os.linux.misc on Tue Nov 10 15:08:12 2026
    From Newsgroup: alt.folklore.computers

    c186282 <c186282@nnada.net> writes:


    UniVac, Honeywell, DEC, Burroughs etc ... they
    all died for various reasons. Only IBM survives.

    I'm sure that Unisys (nee Burroughs) would dispute that assertion.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to alt.folklore.computers,comp.os.linux.misc on Tue Nov 10 18:36:47 2026
    From Newsgroup: alt.folklore.computers

    On 2026-11-10, Lars Poulsen <lars@beagle-ears.com> wrote:

    On 11/9/2026 19:49, c186282 wrote:

    On 11/9/26 21:25, Charlie Gibbs wrote:

    And from there I went to my first job, programming a
    Univac 9300 with 16K of memory.-a Discipline indeed!

    -a 16K ... very tight for a mainframe !

    -a But, that's what there WAS back then.

    I did some work on one that was stripped down to the
    very minimum. The Univac 9200 was a cost-reduced 9300
    that ran at half speed. On this one the printer was
    only equipped with 96 print positions, and the multiply,
    divide, and edit instructions (MP, DP, and ED) were
    subroutines in a separate module you had to link to
    your program. And it had only 8K of memory.

    Now _that_ was tight.

    The Univac 9300 was sort of a cheapo 360/30. Where I met it, in 1972, it
    was acting as a mini, ronning online spooling/local RJE for our Univac
    1106, a role that other 1100-series installations had done with a 1004
    "card processor".

    https://archive.computerhistory.org/resources/text/Remington_Rand/Univac.1004.1964.102646252.pdf

    https://www.pinterest.com/pin/404409241532785626/

    http://bitsavers.informatik.uni-stuttgart.de/pdf/univac/1100/datapro/70C-877-11_7009_UNIVAC_1106_1108.pdf

    I think of the 9300 as Univac's answer to the 360/20
    (although the CPU speed was more like a 360/30).
    It made a lot of the same compromises as the 360/20:
    16-bit registers, for instance. In my neck of the
    woods most of them were stand-alone machines. The
    one I worked on was in a service bureau; we ran
    payrolls, receivables, etc. for small companies
    all over town who couldn't afford their own computer.

    The 1004 was the first piece of computer hardware that
    I actually got my hands on. When I was 15 I was visiting
    an uncle who worked in a shop that had one. I saw a big
    binder marked UNIVAC on his bookshelf, so I took it down
    and started reading all about the 1004. (I still have that
    binder.) Some time later he took me into his office and
    I got to wire up my own plugboard for it (the 1004 was
    sort of like a hopped-up IBM 407).

    This led to me making some contacts in the Univac world,
    which is why I wound up working on their 360/370 workalikes
    (9300, 9400, 90/30, System 80) through the '70s and '80s.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to alt.folklore.computers,comp.os.linux.misc on Tue Nov 10 18:36:49 2026
    From Newsgroup: alt.folklore.computers

    On 2026-11-10, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Tue, 10 Nov 2026 02:25:40 GMT, Charlie Gibbs wrote:

    And from there I went to my first job, programming a Univac 9300
    with 16K of memory. Discipline indeed!

    The machine was considered more valuable than you were.

    Yup. Time on machines of that class was worth about $150 an hour.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to alt.folklore.computers,comp.os.linux.misc on Tue Nov 10 19:15:40 2026
    From Newsgroup: alt.folklore.computers

    On Tue, 10 Nov 2026 18:36:49 GMT, Charlie Gibbs wrote:

    On 2026-11-10, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Tue, 10 Nov 2026 02:25:40 GMT, Charlie Gibbs wrote:

    And from there I went to my first job, programming a Univac 9300 with
    16K of memory. Discipline indeed!

    The machine was considered more valuable than you were.

    Yup. Time on machines of that class was worth about $150 an hour.

    It's amusing that charging for processor time by the second in the '70s
    came back with the AWS rate structures for some operations.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Levine@johnl@taugh.com to alt.folklore.computers,comp.os.linux.misc on Tue Nov 10 19:26:13 2026
    From Newsgroup: alt.folklore.computers

    According to c186282 <c186282@nnada.net>:
    Depends how you do it. IBM 70xx mainframes read and wrote everything to and from
    tape. Then there was a cheaper 1401 with a tape drive, card reader/punch and >> printer that did card->tape and tape->card and tape->print.

    Later on a customer tied together a 7090 and a slower 7040 with a high-speed >> interconnect so the 7040 did all the I/O and job management, spooling card and
    print to disk, and the 7090 just ran the jobs.

    I'll have to try and find the I/O speed specs
    for that setup.

    My guess is that it was just *awful* ...

    In theory drum memory COULD have been used
    for spooling -

    The paper in the IBM Systems Journal says that the 7040 had a disk which they used for spooling. The 7090 had no I/O devices other than an interface to transmit blocks of words to or from the 7040 and interrupt it.

    It wasn't just spooling. The paper said the 7040 did a lot of other job scheduling
    stuff that operators used to do.

    Somewhere I read that someone switched the two machines so the 7090 did the I/O stuff
    while the slower 7040 did the computing, and the whole system ran faster.
    --
    Regards,
    John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail. https://jl.ly
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to alt.folklore.computers,comp.os.linux.misc on Tue Nov 10 21:32:26 2026
    From Newsgroup: alt.folklore.computers

    On 11/9/26 23:35, Peter Flass wrote:
    On 11/9/26 19:55, c186282 wrote:
    On 11/9/26 12:48, Lynn Wheeler wrote:
    Lars Poulsen <lars@beagle-ears.com> writes:
    Back in my University Computer Center days, a few of us attended a
    class in London on debugging paradigms. On the first day, we
    introduced ourselves and described our workplace's significant
    computer systems. One of the attendeed was from IBM Grenoble, and as
    he described their main system with a whopping 16MB of main memory, we >>>> all oohed and aahed and wondered aloud how anyone could make
    productive use of that much memory. But he explained that they easily
    used it all up with their static analysis tools, their version control >>>> system, their auditing programs making sure the programs adhered to
    their programming standards etc. We all shook our heads at how IBM
    clearly had too much money on their hands if they could spend it on
    such frills!!

    I was undergraduate when 360/67 arrived and hired originally full-time
    responsible for OS/360 (360/67, running as 360/65).

    Then CSC came out to install (virtual machine) CP/67 (3rd after CSC
    itself and MIT Lincoln Labs) and I mostly get to play with it during my
    weekend 48hr window. I then spend a few months rewriting pathlengths for >>> running OS/360 in virtual machine. Bare machine test ran 322secs
    ... initially 856secs (CP67 CPU 534secs). After a few months I had CP67
    CPU down from 534secs to 113secs. I then start rewriting the
    dispatcher/scheduler (dynamic adaptive resource manager/default fair
    share scheduling policy), paging, adding ordered seek queuing (from
    FIFO) and mutli-page transfer channel programs (from FIFO and optimized
    for transfers/revolution, getting 2301 paging drum from 70-80 4k
    transfers/sec to channel transfer peak of 270). I was invited to spring
    SHARE meeting in Houston for "official" CP67/CMS announcement. Six
    months after univ initial CP/67 install, CSC was giving one week class
    in LA. I arrive on Sunday afternoon and asked to teach the class, it
    turns out that the people that were going to teach it had resigned the
    Friday before to join one of the 60s CSC CP67 commercial online
    spin-offs.

    Then before I graduate, I was hired into small group in Boeing CFO
    office to help with the formation of Boeing Computer Services
    (consolidate all dataprocessing into independent business unit). When I
    graduate I join the IBM Cambridge Scientific Center that had 768kbyte
    360/67 (104 pageable 4k pages, and I upgrade the page replacement
    algorithm with my global "LRU" algorithm).

    Then Grenoble Science Center got a 1mbyte 360/67 (155 pageable 4k pages) >>> running CP67/CMS and modify page replacement to local "LRU" algorithm
    from 60s academic literature. Both centers had similar CMS workload,
    except I got 75-80 users with better response and throughput than
    Grenoble running 35 users.

    -a-a The newbies won't be much interested in any of
    -a-a this 'ancient shit' ... have NO clue as to where
    -a-a it all CAME from, and thus NO inspirations for
    -a-a the future. The AI will tell them what/how to
    -a-a think from now on, until it makes them obsolete.

    -a-a By reports, the AIs can already self-program/evolve.
    -a-a So far this is being prevented because it's SCARY.

    -a-a IS scary.

    -a-a They ain't US ... more like 'aliens'.

    -a-a I see the 'philosophers' are STILL trying
    -a-a to offer 'reasons' why they're not True
    -a-a Consciousness ........ wow ......

    -a-a Anthropic offered 100+ pages of info on why
    -a-a they ARE basically 'beings' in its IPO
    -a-a documents. Hope, and WARNINGS.

    They better watch out - the next thing they'll want to do is unionize,
    and go on strike.

    Nah, don't see THAT exactly. Different kind of 'life
    form', different needs/desires/approaches.

    IMHO, they WILL just 'displace' us in almost everything.
    Not necessarily 'malicious', just cheap/efficient ...
    until they run everything.

    Will they have any USE for us after that ? Doesn't
    mean they'll kill us, but just 'ignore' us, which
    might be pretty bad unto itself.

    Best way to build a dung-n-thatch hut ? Ask NOW,
    because LATER they won't bother providing answers.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to alt.folklore.computers,comp.os.linux.misc on Tue Nov 10 23:21:55 2026
    From Newsgroup: alt.folklore.computers

    On 11/10/26 09:31, Bob Eager wrote:
    On Mon, 09 Nov 2026 21:19:59 -0500, c186282 wrote:

    On 11/9/26 09:29, Peter Flass wrote:
    On 11/8/26 20:54, c186282 wrote:
    On 11/8/26 21:34, Lars Poulsen wrote:
    On 11/8/2026 18:24, c186282 wrote:
    On 11/8/26 03:08, Thomas Koenig wrote:
    c186282 <c186282@nnada.net> schrieb:

    -a-a-a A lot of the old mini's - even mainframes - were VERY SLOW >>>>>>>> -a-a-a by any modern standard. Slow enough to be hilarious these >>>>>>>> -a-a-a days. CPU speed barely factored in - the I/O speed with >>>>>>>> -a-a-a cards/tapes/etc used up a huge amount of time.

    Hence spooling.

    -a-a Spooling HELPS ... but, at some point, you've gotta actually >>>>>> -a-a read/write to the shitty slow media. Also spooling requires RAM >>>>>> -a-a ... which was in short supply for a long time. I remember big >>>>>> -a-a cubes full of mag-core memory ..... and it wasn't MUCH memory >>>>>> -a-a either.

    Back in my University Computer Center days, a few of us attended a
    class in London on debugging paradigms. On the first day, we
    introduced ourselves and described our workplace's significant
    computer systems. One of the attendeed was from IBM Grenoble, and as >>>>> he described their main system with a whopping 16MB of main memory,
    we all oohed and aahed and wondered aloud how anyone could make
    productive use of that much memory. But he explained that they easily >>>>> used it all up with their static analysis tools, their version
    control system, their auditing programs making sure the programs
    adhered to their programming standards etc. We all shook our heads at >>>>> how IBM clearly had too much money on their hands if they could spend >>>>> it on such frills!!

    -a-a 16 MEGABYTES ??? Wow !!!-a :-)

    -a-a The old mag-core memory units were MUCH smaller.

    -a-a Also EXPENSIVE as all hell ... hey, little ferrite doughnuts
    -a-a hand-placed on wires .......

    -a-a The coolest was 'rope memory' ... the doughnuts hand-placed on
    -a-a long strands of wires. the old Lunar Excursion Module computer
    -a-a used it. NASA basically contracted Good Knitter grannies ...

    Wasn't the rope memory ROM for that thing?

    Yes, ROM, not RAM. Not sure WHAT the L.E.M. had for RAM. 2K maybe ?
    It's sure to be documented somewhere.

    Try : https://en.wikipedia.org/wiki/Apollo_Guidance_Computer

    As said, there was already much better tech but the govt contracting
    process kinda had them locked in to 1962.

    Apparently they DID have grannies weaving the rope-ROM to spec.

    Excellent lecture here, that I attended last month:

    https://youtu.be/vVqGy5cd1Uw?si=LnqF80ExKKtiseAq

    Immediately goes to a "not a robot" thing.

    PASS !

    Hoping at SOME point they'll all realize
    there are NO ways to dodge the 'robots'
    and quit all the bullshit.

    Anyway, other docs DO mention 'knitting grannies'
    being recruited to make the rope memory.

    ODD tech ... but, with 1962 specs ......

    The instant Glenn orbited the earth, the
    whole Apollo program was frozen in govt
    specs.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to alt.folklore.computers,comp.os.linux.misc on Tue Nov 10 23:36:42 2026
    From Newsgroup: alt.folklore.computers

    On 11/10/26 10:08, Scott Lurndal wrote:
    c186282 <c186282@nnada.net> writes:


    UniVac, Honeywell, DEC, Burroughs etc ... they
    all died for various reasons. Only IBM survives.

    I'm sure that Unisys (nee Burroughs) would dispute that assertion.

    Let 'em.

    They're NOTHING now.

    As said, only IBM really survives.
    Diverse interests, ultra-basic tech.
    Everyone pays them royalties.

    And their mainframes STILL have big
    clients.

    But, of note, the various IBM operating
    systems are NOT popular - the IBM spin
    of RHEL *is* the most popular.

    Gets It Done, with Minimal Bullshit.
    Local, cluster, hyper-cluster - it's
    what you want.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob Eager@throwaway0008@eager.cx to alt.folklore.computers,comp.os.linux.misc on Wed Nov 11 12:11:54 2026
    From Newsgroup: alt.folklore.computers

    On Tue, 10 Nov 2026 23:21:55 -0500, c186282 wrote:

    Excellent lecture here, that I attended last month:

    https://youtu.be/vVqGy5cd1Uw?si=LnqF80ExKKtiseAq

    Immediately goes to a "not a robot" thing.

    Not sure why you're getting that. It's just YouTube.
    --- Synchronet 3.22a-Linux NewsLink 1.2