• Re: Is This An Old Folks Home?

    From s|b@me@privacy.invalid to comp.os.linux.misc on Thu Nov 5 17:48:47 2026
    From Newsgroup: comp.os.linux.misc

    On Wed, 04 Nov 2026 20:38:16 +0000, Farley Flud wrote:

    Please keep all posts on topic and refrain from assuming that Usenet
    is your personal taproom.

    'netcop' and 'self-proclaimed moderator' come to mind.
    --
    Horum omnium fortissimi sunt Belgae.
    - Julius Caesar
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Robert Riches@spamtrap42@jacob21819.net to comp.os.linux.misc on Thu Nov 5 16:56:38 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-05, s|b <me@privacy.invalid> wrote:
    On Wed, 04 Nov 2026 20:38:16 +0000, Farley Flud wrote:

    Please keep all posts on topic and refrain from assuming that Usenet
    is your personal taproom.

    'netcop' and 'self-proclaimed moderator' come to mind.

    Please don't feed the trolls.
    --
    Robert Riches
    spamtrap42@jacob21819.net
    (Yes, that is one of my email addresses.)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc on Thu Nov 5 20:55:39 2026
    From Newsgroup: comp.os.linux.misc

    On 05/11/2026 16:48, s|b wrote:
    On Wed, 04 Nov 2026 20:38:16 +0000, Farley Flud wrote:

    Please keep all posts on topic and refrain from assuming that Usenet
    is your personal taproom.

    'netcop' and 'self-proclaimed moderator' come to mind.

    I thought Farley was plonked. Seems to have nym shifted
    Re plonked
    --
    "When a true genius appears in the world, you may know him by this sign,
    that the dunces are all in confederacy against him."

    Jonathan Swift.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc on Thu Nov 5 17:29:01 2026
    From Newsgroup: comp.os.linux.misc

    On 11/4/26 23:14, Rich wrote:
    Nuno Silva <nunojsilva@invalid.invalid> wrote:
    On 2026-11-03, Carlos E. R. wrote:

    On 2026-11-03 00:08, Farley Flud wrote:
    Is this group an actual GNU/Linux discussion forum or a sordid
    home for decrepit old folks and faltering has-beens?

    I don't want no useless info on pre-historic tape readers.

    I, and many others, want cutting edge philosophy on GNU/Linux/FOSS.

    Otherwise, go bury yourselves, grandpas.

    Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

    Then why are you here, granny? :-p

    That's actually a load of nonsense in that a very good use of this
    group would be someone looking for advice on using a tape drive on
    GNU/Linux.

    Do keep in mind that Farley is a known troll.

    It is best to just ignore the troll's posts.

    Also, tape drives are STILL in use, to around
    30tb for the more expensive units. Not 'ideal'
    for big storage any more, but still valuable.
    Check Amazon, a number to choose from.

    Now the big reel-2-reel jobbies from all the
    old sci-fi movies .... no ... gone.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Rich@rich@example.invalid to comp.os.linux.misc on Thu Nov 5 22:52:00 2026
    From Newsgroup: comp.os.linux.misc

    c186282 <c186282@nnada.net> wrote:
    On 11/4/26 23:14, Rich wrote:
    Nuno Silva <nunojsilva@invalid.invalid> wrote:
    On 2026-11-03, Carlos E. R. wrote:

    On 2026-11-03 00:08, Farley Flud wrote:
    Is this group an actual GNU/Linux discussion forum or a sordid
    home for decrepit old folks and faltering has-beens?

    I don't want no useless info on pre-historic tape readers.

    I, and many others, want cutting edge philosophy on GNU/Linux/FOSS.

    Otherwise, go bury yourselves, grandpas.

    Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

    Then why are you here, granny? :-p

    That's actually a load of nonsense in that a very good use of this
    group would be someone looking for advice on using a tape drive on
    GNU/Linux.

    Do keep in mind that Farley is a known troll.

    It is best to just ignore the troll's posts.

    Also, tape drives are STILL in use, to around 30tb for the more
    expensive units. Not 'ideal' for big storage any more, but still
    valuable. Check Amazon, a number to choose from.

    Yup, LTO tapes are in wide use for backing up all those Tb's stored on
    all those clouds. The prices, for the latest models, are at
    "enterprise only need apply" levels, but tape is very much alive and
    well.

    Now the big reel-2-reel jobbies from all the old sci-fi movies ....
    no ... gone.

    Yep, except for museums and the occasional sci-fi movie that want's to
    look 'retro'.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc on Thu Nov 5 19:11:21 2026
    From Newsgroup: comp.os.linux.misc

    On 11/5/26 17:52, Rich wrote:
    c186282 <c186282@nnada.net> wrote:
    On 11/4/26 23:14, Rich wrote:
    Nuno Silva <nunojsilva@invalid.invalid> wrote:
    On 2026-11-03, Carlos E. R. wrote:

    On 2026-11-03 00:08, Farley Flud wrote:
    Is this group an actual GNU/Linux discussion forum or a sordid
    home for decrepit old folks and faltering has-beens?

    I don't want no useless info on pre-historic tape readers.

    I, and many others, want cutting edge philosophy on GNU/Linux/FOSS. >>>>>>
    Otherwise, go bury yourselves, grandpas.

    Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

    Then why are you here, granny? :-p

    That's actually a load of nonsense in that a very good use of this
    group would be someone looking for advice on using a tape drive on
    GNU/Linux.

    Do keep in mind that Farley is a known troll.

    It is best to just ignore the troll's posts.

    Also, tape drives are STILL in use, to around 30tb for the more
    expensive units. Not 'ideal' for big storage any more, but still
    valuable. Check Amazon, a number to choose from.

    Yup, LTO tapes are in wide use for backing up all those Tb's stored on
    all those clouds. The prices, for the latest models, are at
    "enterprise only need apply" levels, but tape is very much alive and
    well.

    Now the big reel-2-reel jobbies from all the old sci-fi movies ....
    no ... gone.

    Yep, except for museums and the occasional sci-fi movie that want's to
    look 'retro'.

    Hmm ... one of those "Captain America" movies
    of late. The evil genius had his brain digitized
    and stored on a warehouse full of those tape units.

    Tape is slow - often VERY VERY slow - but it can
    still deliver an acceptable storage-per-dollar
    figure in some applications.

    I wonder how many corps still have a "The backup
    tapes SHALL be stored in the fireproof safe each
    evening" in the Official Rules book ? :-)

    Most of the kiddies don't even know what those
    big tape reels were DOING rolling back and forth
    and how SLOW computing was back in the day.
    "Batch jobs" ? "Code overlays" ? "Temporary
    intermediate storage" ?

    But they DID look Cool !

    Today, a USB dual-drive unit with a couple
    of 16tb magnetics inside - faster and cheaper
    and still small enough to put in the safe.

    But tape isn't dead, not YET anyway.

    Yea yea, we all hoped for petabyte holographic
    crystal mass storage about the size of a thumb
    drive by now, very Trek. Sorry ....

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From TJ@TJ@noneofyour.business to comp.os.linux.misc on Thu Nov 5 20:40:13 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-04 01: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...

    Guess that makes me really old. I was drafted during the Nixon
    administration, and assigned to run a HP 2116 minicomputer system at a research facility. When I got there, it was using a couple of 7-track
    tape drives, and was booted up with a strip of paper tape. Soon after,
    it was upgraded to a then newfangled "moving head disk drive" that had
    one fixed disk and one bay for cartridges about 15 inches in diameter,
    and a revised boot program eliminated the paper tape boot procedure.

    TJ
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Rich@rich@example.invalid to comp.os.linux.misc on Fri Nov 6 02:41:59 2026
    From Newsgroup: comp.os.linux.misc

    c186282 <c186282@nnada.net> wrote:
    On 11/5/26 17:52, Rich wrote:
    c186282 <c186282@nnada.net> wrote:
    On 11/4/26 23:14, Rich wrote:
    Nuno Silva <nunojsilva@invalid.invalid> wrote:
    On 2026-11-03, Carlos E. R. wrote:

    On 2026-11-03 00:08, Farley Flud wrote:
    Is this group an actual GNU/Linux discussion forum or a sordid
    home for decrepit old folks and faltering has-beens?

    I don't want no useless info on pre-historic tape readers.

    I, and many others, want cutting edge philosophy on GNU/Linux/FOSS. >>>>>>>
    Otherwise, go bury yourselves, grandpas.

    Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

    Then why are you here, granny? :-p

    That's actually a load of nonsense in that a very good use of this
    group would be someone looking for advice on using a tape drive on
    GNU/Linux.

    Do keep in mind that Farley is a known troll.

    It is best to just ignore the troll's posts.

    Also, tape drives are STILL in use, to around 30tb for the more
    expensive units. Not 'ideal' for big storage any more, but still
    valuable. Check Amazon, a number to choose from.

    Yup, LTO tapes are in wide use for backing up all those Tb's stored on
    all those clouds. The prices, for the latest models, are at
    "enterprise only need apply" levels, but tape is very much alive and
    well.

    Now the big reel-2-reel jobbies from all the old sci-fi movies ....
    no ... gone.

    Yep, except for museums and the occasional sci-fi movie that want's to
    look 'retro'.

    Hmm ... one of those "Captain America" movies of late. The evil
    genius had his brain digitized and stored on a warehouse full of
    those tape units.

    Tape is slow - often VERY VERY slow - but it can still deliver an
    acceptable storage-per-dollar figure in some applications.

    Yes, although that comes with a very big "it depends" star next to it.
    For random access, yes, very very slow.

    For sequential access, modern LTO-10 drives claim a native 400MB/s
    write speed (https://spectralogic.com/wp-content/uploads/LTO-10-Tape-Drive-Datasheet-Spectra-Logic.pdf)
    400MB/s rivals a good many of the non-super performance SSD's, and out
    ranks many mechanical disks as well. Just don't try to randomly read
    the data back out later....

    I wonder how many corps still have a "The backup
    tapes SHALL be stored in the fireproof safe each
    evening" in the Official Rules book ? :-)

    Since those sorts of rules books are very often never scrutinized for
    "what can we remove", likely nearly all of them that used to have that
    clause in their rule book.

    Today, a USB dual-drive unit with a couple
    of 16tb magnetics inside - faster and cheaper
    and still small enough to put in the safe.

    But tape isn't dead, not YET anyway.

    The big advantage tape gives enterprise customers is 40TB of native
    capacity per LTO-10 tape, and long term storage claims. So their rule
    book can also include: "every fourth backup set is shipped off to Iron Mountan" as their 'offsite' storage aspect, with some reasonable
    expectation they can read the tape in 5 or 10 years (presuming they
    have a compatible drive with which to do so).

    And that 40TB of tape costs way less than two 20TB hard drives to store
    the same 40TB.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc on Thu Nov 5 21:52:26 2026
    From Newsgroup: comp.os.linux.misc

    On 11/5/26 20:40, TJ wrote:
    On 2026-11-04 01: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!

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

    Idiot.-a 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.-a 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.-a 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.-a Good for converting your old
    tapes...

    Guess that makes me really old. I was drafted during the Nixon administration, and assigned to run a HP 2116 minicomputer system at a research facility. When I got there, it was using a couple of 7-track
    tape drives, and was booted up with a strip of paper tape. Soon after,
    it was upgraded to a then newfangled "moving head disk drive" that had
    one fixed disk and one bay for cartridges about 15 inches in diameter,
    and a revised boot program eliminated the paper tape boot procedure.

    Hey, STATE-OF-THE-ART ! :-)

    Kinda miss the drive units with the
    removable platters. Do NOT pull them
    before they stop spinning, saw the
    result of that once !

    Odd fact, had a tour of a US submarine in
    the mid 80s ... the sonar niche had a "mini"
    and one removable-platter drive. Probably
    officially specced a decade before. Govt/mil
    stuff is often like that. The Apollo/LEM
    spacecraft were already well behind the
    curve when it came to computer shit ... but
    it'd all been specced, set in stone, in the
    early 60s. "ROPE MEMORY" for the LEM !

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc on Thu Nov 5 22:31:22 2026
    From Newsgroup: comp.os.linux.misc

    On 11/5/26 21:41, Rich wrote:
    c186282 <c186282@nnada.net> wrote:
    On 11/5/26 17:52, Rich wrote:
    c186282 <c186282@nnada.net> wrote:
    On 11/4/26 23:14, Rich wrote:
    Nuno Silva <nunojsilva@invalid.invalid> wrote:
    On 2026-11-03, Carlos E. R. wrote:

    On 2026-11-03 00:08, Farley Flud wrote:
    Is this group an actual GNU/Linux discussion forum or a sordid >>>>>>>> home for decrepit old folks and faltering has-beens?

    I don't want no useless info on pre-historic tape readers.

    I, and many others, want cutting edge philosophy on GNU/Linux/FOSS. >>>>>>>>
    Otherwise, go bury yourselves, grandpas.

    Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

    Then why are you here, granny? :-p

    That's actually a load of nonsense in that a very good use of this >>>>>> group would be someone looking for advice on using a tape drive on >>>>>> GNU/Linux.

    Do keep in mind that Farley is a known troll.

    It is best to just ignore the troll's posts.

    Also, tape drives are STILL in use, to around 30tb for the more
    expensive units. Not 'ideal' for big storage any more, but still
    valuable. Check Amazon, a number to choose from.

    Yup, LTO tapes are in wide use for backing up all those Tb's stored on
    all those clouds. The prices, for the latest models, are at
    "enterprise only need apply" levels, but tape is very much alive and
    well.

    Now the big reel-2-reel jobbies from all the old sci-fi movies ....
    no ... gone.

    Yep, except for museums and the occasional sci-fi movie that want's to
    look 'retro'.

    Hmm ... one of those "Captain America" movies of late. The evil
    genius had his brain digitized and stored on a warehouse full of
    those tape units.

    Tape is slow - often VERY VERY slow - but it can still deliver an
    acceptable storage-per-dollar figure in some applications.

    Yes, although that comes with a very big "it depends" star next to it.
    For random access, yes, very very slow.

    Kinda forget "RA" ...

    But, back in the day, the CPUs were so slow and
    multi-user so clunky ... even 'temporary' storage
    of intermediate results to tapes was acceptable.

    For sequential access, modern LTO-10 drives claim a native 400MB/s
    write speed (https://spectralogic.com/wp-content/uploads/LTO-10-Tape-Drive-Datasheet-Spectra-Logic.pdf)
    400MB/s rivals a good many of the non-super performance SSD's, and out
    ranks many mechanical disks as well. Just don't try to randomly read
    the data back out later....

    Today, a two-drive USB disk unit can seriously
    out-perform tapes - and it's still pretty compact.

    I wonder how many corps still have a "The backup
    tapes SHALL be stored in the fireproof safe each
    evening" in the Official Rules book ? :-)

    Since those sorts of rules books are very often never scrutinized for
    "what can we remove", likely nearly all of them that used to have that
    clause in their rule book.

    It'd be fun to have a survey of Big Corp IT rule
    books, just to SEE how many still have that rule "-)

    Today, a USB dual-drive unit with a couple
    of 16tb magnetics inside - faster and cheaper
    and still small enough to put in the safe.

    But tape isn't dead, not YET anyway.

    The big advantage tape gives enterprise customers is 40TB of native
    capacity per LTO-10 tape, and long term storage claims. So their rule
    book can also include: "every fourth backup set is shipped off to Iron Mountan" as their 'offsite' storage aspect, with some reasonable
    expectation they can read the tape in 5 or 10 years (presuming they
    have a compatible drive with which to do so).

    As said, tapes DO have some advantages. Good capacity
    for cheap and the modern tapes WILL last a long time.
    Alas nothing 'optical', even Blu-Rays, remotely match
    the capacity.

    HAVE a Blu-Ray unit. Mostly my (home) backups go
    to a little NAS - four-drive USB unit - using NFS.
    However about every six months I burn my most
    important shit to a BR. Even though "home", still
    have to pick and choose carefully just so it'll
    fit on a disk. Make a big ZIP or TAR, burn it.

    Biz uses, even BR-DL is not enough.

    Disappointing.

    And that 40TB of tape costs way less than two 20TB hard drives to store
    the same 40TB.

    True. Tape is CHEAP.

    Also SLOW SLOW SLOW.

    A multi-drive USB unit with some big mag
    drives WOULD cover it ... and still small
    enough for the fireproof safe.

    "Cloud" can be OK too ... but, if smart, DO
    always keep a LOCAL backup (or two or three).
    Vlad or Xi or Kim are gonna disappear all that
    'cloud' shit Real Soon Now. The cyber-war
    is ON. The commiesocialistDems LOVE Xi and Kim,
    won't do a single thing to thwart them.

    Then there will be much crying and screaming
    and gnashing of teeth and infidels burnt at
    the stake and desolation and ...........

    What WOULD happen to global biz if all the
    cloud apps/storage (and backup storage) was
    corrupted at a stroke ? SO many totally
    rely on M$ cloud shit for ALL biz needs.
    But if it Goes Away ... even for a week or
    for months (or forever) ........

    No, they WON'T be 'ready for it' - that much is
    obvious. 'Cloud' has become a religion - faith.

    Anyway, if you want tape, Linux still
    understands tape.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Beej Jorgensen@beej@beej.us to comp.os.linux.misc on Fri Nov 6 05:59:51 2026
    From Newsgroup: comp.os.linux.misc

    In article <ipucna2KmLW-nnD3nZ2dnZfqn_WdnZ2d@giganews.com>,
    c186282 <c186282@nnada.net> wrote:
    Also, tape drives are STILL in use, to around 30tb for the more
    expensive units. Not 'ideal' for big storage any more, but still
    valuable.

    Recent headline: "FUJIFILM to Increase Production Capacity by 5x for
    Magnetic Data Storage Tape". I guess AI is driving demand up again.

    And this is from a recent Tom's Hardware article:

    The current LTO-10 generation stores up to 40TB of uncompressed data
    per cartridge, while HPE and Quantum rCo the companies behind the LTO
    Program rCo now envision LTO-14 cartridges with up to 365TB of native
    capacity.

    IIRC, the data from Arecibo radio telescope used to be shipped back to
    the mainland on tape because that was the only thing that had the
    bandwidth.

    "Never underestimate the bandwidth of a station wagon full of tapes
    hurtling down the highway."

    Now the big reel-2-reel jobbies from all the old sci-fi movies .... no
    ... gone.

    We had one 9-track when I worked as a computer operator in 1992. It was
    used to send financial records to the bank. That was the first and last
    one I saw in use.
    --
    Brian "Beej Jorgensen" Hall | beej@beej.us
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.linux.misc,alt.folklore.computers on Fri Nov 6 06:18:48 2026
    From Newsgroup: comp.os.linux.misc

    On Fri, 6 Nov 2026 05:59:51 -0000 (UTC), Beej Jorgensen wrote:

    We had one 9-track when I worked as a computer operator in 1992. It
    was used to send financial records to the bank. That was the first
    and last one I saw in use.

    A decade earlier, it was a slightly different story.

    Also, back then, it was still the fashion in movies and TV to portray
    a computer as having lots of tape drives with the reels spinning
    busily, as though such heavy tape usage was characteristic of normal
    computer operation. That would have been true a decade before that,
    but by the time the 1980s came along, tapes were primarily used for
    backup and data interchange between installations.

    Furthermore, back then, there was real difficulty in getting data
    between different brands of personal computers, because of
    incompatible floppy disk formats, and many machines not even having
    floppy drives. But there was this open protocol called rCLKermitrCY, which
    ran on serial lines (or modem connections), for which implementations
    were available for just about every kind of computer under the sun,
    big and small.

    And you could get copies free, just by sending a blank reel of tape to
    the University of Columbia; they would put all the latest versions of
    all the releases on that, and send it back.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.os.linux.misc on Fri Nov 6 14:28:05 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-06 03:52, c186282 wrote:
    On 11/5/26 20:40, TJ wrote:
    On 2026-11-04 01:21, Charlie Gibbs wrote:
    On 2026-11-04, Rich <rich@example.invalid> wrote:


    Guess that makes me really old. I was drafted during the Nixon
    administration, and assigned to run a HP 2116 minicomputer system at a
    research facility. When I got there, it was using a couple of 7-track
    tape drives, and was booted up with a strip of paper tape. Soon after,
    it was upgraded to a then newfangled "moving head disk drive" that had
    one fixed disk and one bay for cartridges about 15 inches in diameter,
    and a revised boot program eliminated the paper tape boot procedure.

    -a Hey, STATE-OF-THE-ART !-a :-)

    -a Kinda miss the drive units with the
    -a removable platters. Do NOT pull them
    -a before they stop spinning, saw the
    -a result of that once !

    Please tell!


    -a Odd fact, had a tour of a US submarine in
    -a the mid 80s ... the sonar niche had a "mini"
    -a and one removable-platter drive. Probably
    -a officially specced a decade before. Govt/mil
    -a stuff is often like that. The Apollo/LEM
    -a spacecraft were already well behind the
    -a curve when it came to computer shit ... but
    -a it'd all been specced, set in stone, in the
    -a early 60s. "ROPE MEMORY" for the LEM !

    It is a big problem to maintain those for years, if they are
    industry-obsolete when they start service.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Joel W. Crump@joelcrump@gmail.com to comp.os.linux.misc on Fri Nov 6 12:23:08 2026
    From Newsgroup: comp.os.linux.misc

    On 11/2/2026 6:08 PM, Farley Flud wrote:

    Is this group an actual GNU/Linux discussion forum or a sordid
    home for decrepit old folks and faltering has-beens?

    I don't want no useless info on pre-historic tape readers.


    So why no SSD?


    I, and many others, want cutting edge philosophy on GNU/Linux/FOSS.

    Otherwise, go bury yourselves, grandpas.

    Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!


    Any OS benefits from an SSD.
    --
    Joel W. Crump
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Farley Flud@ff@gnulinux.rocks to comp.os.linux.misc on Fri Nov 6 19:25:00 2026
    From Newsgroup: comp.os.linux.misc

    On Fri, 6 Nov 2026 12:23:08 -0500, Joel W. Crump wrote:

    On 11/2/2026 6:08 PM, Farley Flud wrote:

    Is this group an actual GNU/Linux discussion forum or a sordid
    home for decrepit old folks and faltering has-beens?

    I don't want no useless info on pre-historic tape readers.


    So why no SSD?


    The reasons were explicitly stated many times already.

    Perhaps the surge of endorphins that you experience with each
    dildo that slides up your ass has caused you to forget.

    Ha, ha, ha, ha, ha, ha, ha, ha, ha!

    Degenerate sodomite.



    Any OS benefits from an SSD.


    None whatsoever.

    Unless, for you, SSD = Self-Satisfying Dildo.

    Ha, ha, ha, ha, ha, ha, ha, ha, ha!

    Degenerate sodomite.
    --
    Gentoo/LFS: Is there any-fucking-thing else?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc on Fri Nov 6 20:51:50 2026
    From Newsgroup: comp.os.linux.misc

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

    On 11/5/26 21:41, Rich wrote:

    c186282 <c186282@nnada.net> wrote:

    Tape is slow - often VERY VERY slow - but it can still deliver an
    acceptable storage-per-dollar figure in some applications.

    Yes, although that comes with a very big "it depends" star next to it.
    For random access, yes, very very slow.

    Kinda forget "RA" ...

    But, back in the day, the CPUs were so slow and
    multi-user so clunky ... even 'temporary' storage
    of intermediate results to tapes was acceptable.

    Don't underestimate sequential processing. Sophisticated
    techniques were developed that didn't need random access.
    You make the most of what you have.

    Many tape drives could read tape backwards, which was
    exploited by, e.g., sort programs. This could save the
    minute or two it would take to rewind the tape before
    starting the next pass.

    And that 40TB of tape costs way less than two 20TB hard drives to store
    the same 40TB.

    "Cloud" can be OK too ... but, if smart, DO
    always keep a LOCAL backup (or two or three).
    Vlad or Xi or Kim are gonna disappear all that
    'cloud' shit Real Soon Now. The cyber-war
    is ON. The commiesocialistDems LOVE Xi and Kim,
    won't do a single thing to thwart them.

    Your #1 right-winger seems to like Kim a lot too.

    But we don't need him - a friend lost a lot of
    precious photos due to a screw-up at his cloud
    provider that had nothing to do with Vlad or Xi
    or whoever.

    Then there will be much crying and screaming
    and gnashing of teeth and infidels burnt at
    the stake and desolation and ...........

    As long as we can find a scapegoat...

    What WOULD happen to global biz if all the
    cloud apps/storage (and backup storage) was
    corrupted at a stroke ? SO many totally
    rely on M$ cloud shit for ALL biz needs.
    But if it Goes Away ... even for a week or
    for months (or forever) ........

    Maybe Lord Bill will decide to pull the plug.
    Temporarily, anyway. There are lots of ransom
    opportunities.

    No, they WON'T be 'ready for it' - that much is
    obvious. 'Cloud' has become a religion - faith.

    I should get one of those T-shirts that says,

    There is no Cloud.
    It's just someone else's computer.
    --
    /~\ Charlie Gibbs | Too many people have become
    \ / <cgibbs@kltpzyxm.invalid> | dependent on the Internet.
    X I'm really at ac.dekanfrus | It Clouds their thinking.
    / \ if you read it the right way. |
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Joel W. Crump@joelcrump@gmail.com to comp.os.linux.misc on Fri Nov 6 15:59:30 2026
    From Newsgroup: comp.os.linux.misc

    On 11/6/2026 2:25 PM, Farley Flud wrote:

    Is this group an actual GNU/Linux discussion forum or a sordid
    home for decrepit old folks and faltering has-beens?

    I don't want no useless info on pre-historic tape readers.

    So why no SSD?

    The reasons were explicitly stated many times already.

    Perhaps the surge of endorphins that you experience with each
    dildo that slides up your ass has caused you to forget.

    Ha, ha, ha, ha, ha, ha, ha, ha, ha!

    Degenerate sodomite.

    Any OS benefits from an SSD.

    None whatsoever.

    Unless, for you, SSD = Self-Satisfying Dildo.

    Ha, ha, ha, ha, ha, ha, ha, ha, ha!

    Degenerate sodomite.


    I saw Linux on a four-core machine with a SATA SSD, and on a six-core/12-thread and a four-core/four-thread both with NVMe storage,
    it matters plenty if one wants more than your unserviceable rig.
    --
    Joel W. Crump
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • 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: comp.os.linux.misc

    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 rbowman@bowman@montana.com to comp.os.linux.misc on Sat Nov 7 02:41:20 2026
    From Newsgroup: comp.os.linux.misc

    On Fri, 06 Nov 2026 20:51:50 GMT, Charlie Gibbs wrote:

    I should get one of those T-shirts that says,

    There is no Cloud.
    It's just someone else's computer.

    I got some funny looks when I said we were already using a private cloud.
    Most of the companies that were touting a cloud solution for emergency services software backed off. Some of the security requirements assumed
    the computer would be surrounded by armed responders,
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc on Sat Nov 7 02:50:54 2026
    From Newsgroup: comp.os.linux.misc

    On Fri, 6 Nov 2026 15:59:30 -0500, Joel W. Crump wrote:

    I saw Linux on a four-core machine with a SATA SSD, and on a six-core/12-thread and a four-core/four-thread both with NVMe storage,
    it matters plenty if one wants more than your unserviceable rig.

    I replaced the HDDs on a couple of older machines with SATA SSDs. The most noticeable improvement was on reboot since I don't do any disk intensive stuff. Starting individual programs wasn't appreciably faster. SSDs
    allowed SATA to achieve its maximum performance, something I don't think
    even the best HDDs could.

    It's still slower than NVMe but not a show stopper.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc on Fri Nov 6 23:00:23 2026
    From Newsgroup: comp.os.linux.misc

    On 11/6/26 14:25, Farley Flud wrote:
    On Fri, 6 Nov 2026 12:23:08 -0500, Joel W. Crump wrote:

    On 11/2/2026 6:08 PM, Farley Flud wrote:

    Is this group an actual GNU/Linux discussion forum or a sordid
    home for decrepit old folks and faltering has-beens?

    I don't want no useless info on pre-historic tape readers.


    So why no SSD?


    The reasons were explicitly stated many times already.

    Perhaps the surge of endorphins that you experience with each
    dildo that slides up your ass has caused you to forget.

    Ha, ha, ha, ha, ha, ha, ha, ha, ha!

    Degenerate sodomite.
    Well THIS conversation has gone down
    the toilet ........

    SSDs are good, but the price-per-TB is still
    not so good - even worse now that AI has been
    sucking up all the memory chips in the world.

    Have some SSDs, and like 'em, but the last drive
    I bought was a magnetic ... more cap for the $$$
    by a good margin and fast enough for MY need.

    Tape, as said, still has a place. USB disk units
    with magnetics are better though these days. Tape
    will fade away, but it's not gone yet.

    Linux "gets" tape - good thing.

    Hmm ... ".tar' ... means "TAPE Archive" :-)

    --- 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: comp.os.linux.misc

    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 Nuno Silva@nunojsilva@invalid.invalid to comp.os.linux.misc on Sat Nov 7 09:03:46 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-07, rbowman wrote:

    On Fri, 6 Nov 2026 15:59:30 -0500, Joel W. Crump wrote:

    I saw Linux on a four-core machine with a SATA SSD, and on a
    six-core/12-thread and a four-core/four-thread both with NVMe storage,
    it matters plenty if one wants more than your unserviceable rig.

    I replaced the HDDs on a couple of older machines with SATA SSDs. The most noticeable improvement was on reboot since I don't do any disk intensive stuff. Starting individual programs wasn't appreciably faster. SSDs
    allowed SATA to achieve its maximum performance, something I don't think even the best HDDs could.

    It's still slower than NVMe but not a show stopper.

    I guess in a decent OS without anything hogging all memory (I see you,
    Webapp Platform which calls itself "Browser"), the visible improvement
    is expected to be on first load of something, unless you're really
    accessing a *lot* of stuff.

    RAM-cached filesystem data are probably faster than SSDs or NVMe?
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.os.linux.misc,alt.folklore.computers on Sat Nov 7 18:40:54 2026
    From Newsgroup: comp.os.linux.misc

    On 11/6/2026 2:18 PM, Lawrence DrCOOliveiro wrote:
    On Fri, 6 Nov 2026 05:59:51 -0000 (UTC), Beej Jorgensen wrote:

    We had one 9-track when I worked as a computer operator in 1992. It
    was used to send financial records to the bank. That was the first
    and last one I saw in use.

    A decade earlier, it was a slightly different story.

    Also, back then, it was still the fashion in movies and TV to portray
    a computer as having lots of tape drives with the reels spinning
    busily, as though such heavy tape usage was characteristic of normal
    computer operation. That would have been true a decade before that,
    but by the time the 1980s came along, tapes were primarily used for
    backup and data interchange between installations.

    Furthermore, back then, there was real difficulty in getting data
    between different brands of personal computers, because of
    incompatible floppy disk formats, and many machines not even having
    floppy drives. But there was this open protocol called rCLKermitrCY, which ran on serial lines (or modem connections), for which implementations
    were available for just about every kind of computer under the sun,
    big and small.

    And you could get copies free, just by sending a blank reel of tape to
    the University of Columbia; they would put all the latest versions of
    all the releases on that, and send it back.

    Now now Lawrence, don't act like it's all gone. You can still get it,
    and use it, at

    https://www.kermitproject.org/index.html

    and

    https://davidrg.github.io/ckwin/

    to transfer files with all kinds of protocols. I used it in recent
    years to transfer files between FreeDOS computer and Windows 10, so
    it's definitely still useful.

    Information and download links for MS-DOS Kermit can be found here,

    https://www.kermitproject.org/mskermit.html

    and you can even download and read the book /Using MS-DOS Kermit/, 2nd
    edition from that website.

    I'm sure someone in the retrocomputing hobby at alt.folklore.computers
    can make use of these software packages, perhaps after two hundred
    years; so it's definitely worth mentioning.


    Best wishes and happy Kermit!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- 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: comp.os.linux.misc

    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: comp.os.linux.misc

    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 comp.os.linux.misc,alt.folklore.computers on Sat Nov 7 07:33:42 2026
    From Newsgroup: comp.os.linux.misc

    On 11/7/26 03:40, Johann 'Myrkraverk' Oskarsson wrote:

    Now now Lawrence, don't act like it's all gone.-a You can still get it,
    and use it, at

    -a https://www.kermitproject.org/index.html

    and

    -a https://davidrg.github.io/ckwin/

    to transfer files with all kinds of protocols.-a I used it in recent
    years to transfer files between FreeDOS computer and Windows 10, so
    it's definitely still useful.


    I just used it the other day to transfer files from my Multics system to Linux.

    --- 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: comp.os.linux.misc

    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 comp.os.linux.misc on Sat Nov 7 06:39:57 2026
    From Newsgroup: comp.os.linux.misc

    On 11/6/2026 18:41, rbowman wrote:
    On Fri, 06 Nov 2026 20:51:50 GMT, Charlie Gibbs wrote:

    I should get one of those T-shirts that says,

    There is no Cloud.
    It's just someone else's computer.

    I got some funny looks when I said we were already using a private cloud. Most of the companies that were touting a cloud solution for emergency services software backed off. Some of the security requirements assumed
    the computer would be surrounded by armed responders,

    As I understand it, that is a reasonable assumption in your local
    region? (Even for a "private cloud".)
    --
    Lars Poulsen - an old geek in Santa Barbara, California
    --- 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: comp.os.linux.misc

    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 Joel W. Crump@joelcrump@gmail.com to comp.os.linux.misc on Sat Nov 7 13:01:11 2026
    From Newsgroup: comp.os.linux.misc

    On 11/6/2026 9:50 PM, rbowman wrote:

    I saw Linux on a four-core machine with a SATA SSD, and on a
    six-core/12-thread and a four-core/four-thread both with NVMe storage,
    it matters plenty if one wants more than your unserviceable rig.

    I replaced the HDDs on a couple of older machines with SATA SSDs. The most noticeable improvement was on reboot since I don't do any disk intensive stuff. Starting individual programs wasn't appreciably faster. SSDs
    allowed SATA to achieve its maximum performance, something I don't think
    even the best HDDs could.

    It's still slower than NVMe but not a show stopper.


    Larry gets performance from an HDD because there's barely anything being loaded/swapped.
    --
    Joel W. Crump
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc on Sat Nov 7 18:01:27 2026
    From Newsgroup: comp.os.linux.misc

    On Sat, 07 Nov 2026 09:03:46 +0000, Nuno Silva wrote:

    I guess in a decent OS without anything hogging all memory (I see you,
    Webapp Platform which calls itself "Browser"), the visible improvement
    is expected to be on first load of something, unless you're really
    accessing a *lot* of stuff.

    I would need better timing but on the Fedora box with a SATA SSD and the Ubuntu with a NMVe applications launch in about 3 seconds. Snaps are a
    little slower.

    The Ubuntu box is a AMD Ryzen 7 4700U from 2020, the Fedora box is a Core i5-4590 from 2014.

    I can't pinpoint an exact date but there was a watershed where PCs went
    from painfully slow to acceptable and unless you're doing CPU or drive
    intense tasks the UX has changed very little.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,alt.folklore.computers on Sat Nov 7 13:12:12 2026
    From Newsgroup: comp.os.linux.misc

    On 11/7/26 09:33, Peter Flass wrote:
    On 11/7/26 03:40, Johann 'Myrkraverk' Oskarsson wrote:

    Now now Lawrence, don't act like it's all gone.-a You can still get it,
    and use it, at

    -a-a https://www.kermitproject.org/index.html

    and

    -a-a https://davidrg.github.io/ckwin/

    to transfer files with all kinds of protocols.-a I used it in recent
    years to transfer files between FreeDOS computer and Windows 10, so
    it's definitely still useful.


    I just used it the other day to transfer files from my Multics system to Linux.

    Still rockin' Multics ???

    Thought that had totally faded away.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc on Sat Nov 7 18:30:00 2026
    From Newsgroup: comp.os.linux.misc

    On Sat, 7 Nov 2026 06:39:57 -0800, Lars Poulsen wrote:

    On 11/6/2026 18:41, rbowman wrote:
    On Fri, 06 Nov 2026 20:51:50 GMT, Charlie Gibbs wrote:

    I should get one of those T-shirts that says,

    There is no Cloud.
    It's just someone else's computer.

    I got some funny looks when I said we were already using a private
    cloud.
    Most of the companies that were touting a cloud solution for emergency
    services software backed off. Some of the security requirements assumed
    the computer would be surrounded by armed responders,

    As I understand it, that is a reasonable assumption in your local
    region? (Even for a "private cloud".)

    Yes. Interfacing with the NCIC carries a number of requirements.

    https://en.wikipedia.org/wiki/National_Crime_Information_Center

    In addition state CJIN (Criminal Justice Information Network) impose their requirements. Even our support people had to be vetted and finger printed before accessing a site. In theory I could look over their shoulder but couldn't access the sites myself. I carefully avoided the certification to maintain separation from the support tasks.

    The theory broke down when the support people brought back logs but we
    didn't talk about that. I'll admit I saw some juicy stuff.

    NCIC tried to respond to the implications of off-premises clouds. HIPAA
    also had an oar in the water.

    https://www.hhs.gov/hipaa/index.html

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From L Thorpe@lt666@sixsixsix.net to comp.os.linux.misc on Sat Nov 7 18:31:11 2026
    From Newsgroup: comp.os.linux.misc

    On Sat, 07 Nov 2026 09:03:46 +0000, Nuno Silva wrote:


    I guess in a decent OS without anything hogging all memory (I see you,
    Webapp Platform which calls itself "Browser"), the visible improvement
    is expected to be on first load of something, unless you're really
    accessing a *lot* of stuff.


    Joel, the degenerate sodomite, only has a paltry 2G of RAM and
    therefore his system must be swapping intensively. In such a
    case, an SSD could be beneficial.

    But with a normal 32/64G of RAM, swapping will be nonexistent
    and essentially all I/O will be buffered in RAM. In such a
    case, an HDD drive is more than sufficient and it possesses
    a much greater longevity to boot.

    SSDs are for ignorant losers.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Joel W. Crump@joelcrump@gmail.com to comp.os.linux.misc on Sat Nov 7 13:39:54 2026
    From Newsgroup: comp.os.linux.misc

    On 11/7/2026 1:31 PM, L Thorpe wrote:
    On Sat, 07 Nov 2026 09:03:46 +0000, Nuno Silva wrote:

    I guess in a decent OS without anything hogging all memory (I see you,
    Webapp Platform which calls itself "Browser"), the visible improvement
    is expected to be on first load of something, unless you're really
    accessing a *lot* of stuff.

    Joel, the degenerate sodomite,


    What I like in my ass is irrelevant.


    only has a paltry 2G of RAM and
    therefore his system must be swapping intensively. In such a
    case, an SSD could be beneficial.


    I have 16 GB with about 13 available after the GPU takes some.


    But with a normal 32/64G of RAM, swapping will be nonexistent
    and essentially all I/O will be buffered in RAM. In such a
    case, an HDD drive is more than sufficient and it possesses
    a much greater longevity to boot.

    SSDs are for ignorant losers.


    You just project weirdness onto others.
    --
    Joel W. Crump
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From L Thorpe@lt666@sixsixsix.net to comp.os.linux.misc on Sat Nov 7 19:07:04 2026
    From Newsgroup: comp.os.linux.misc

    On Sat, 7 Nov 2026 13:39:54 -0500, Joel W. Crump wrote:


    What I like in my ass is irrelevant.


    If it is so fucking "irrelevant" then why have you repeatedly
    decided to self-confess your despicable perversion to the world
    on Usenet?

    Huh? Why?

    Ha, ha, ha, ha, ha, ha, ha, ha, ha!

    What a stupid fucking loser!

    Ha, ha, ha, ha, ha, ha, ha, ha, ha!

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Joel W. Crump@joelcrump@gmail.com to comp.os.linux.misc on Sat Nov 7 14:30:58 2026
    From Newsgroup: comp.os.linux.misc

    On 11/7/2026 2:07 PM, L Thorpe wrote:

    What I like [trans women's cocks] in my ass is irrelevant.

    If it is so fucking "irrelevant" then why have you repeatedly
    decided to self-confess your despicable perversion to the world
    on Usenet?

    Huh? Why?

    Ha, ha, ha, ha, ha, ha, ha, ha, ha!

    What a stupid fucking loser!

    Ha, ha, ha, ha, ha, ha, ha, ha, ha!


    You're just being transphobic.
    --
    Joel W. Crump
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc on Sat Nov 7 15:54:41 2026
    From Newsgroup: comp.os.linux.misc

    On 11/7/26 13:01, Joel W. Crump wrote:
    On 11/6/2026 9:50 PM, rbowman wrote:

    I saw Linux on a four-core machine with a SATA SSD, and on a
    six-core/12-thread and a four-core/four-thread both with NVMe storage,
    it matters plenty if one wants more than your unserviceable rig.

    I replaced the HDDs on a couple of older machines with SATA SSDs. The
    most
    noticeable improvement was on reboot since I don't do any disk intensive
    stuff. Starting individual programs wasn't appreciably faster. SSDs
    allowed SATA to achieve its maximum performance, something I don't think
    even the best HDDs could.

    It's still slower than NVMe but not a show stopper.


    Larry gets performance from an HDD because there's barely anything being loaded/swapped.

    Yet another case of "What Do YOU Need ?"

    I much appreciated what the Samsung did for a
    slightly older lap (had a WD Blue originally)
    especially for the boot-up. Fatter apps start
    up a bit quicker too. But my uses are
    all "home" now and I don't do much you'd
    really call "disk intensive". My "NAS" is
    an external 4-dr USB unit linked with NFS - the
    wifi/USB latency negates any speed advantage
    of SSDs.

    So, I can save money with magnetic drives.

    Now for an office server with a bunch of cat-6
    wires going everywhere, NOW you may feel the
    need for speed.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc on Sat Nov 7 21:55:56 2026
    From Newsgroup: comp.os.linux.misc

    On 07/11/2026 18:01, rbowman wrote:
    I can't pinpoint an exact date but there was a watershed where PCs went
    from painfully slow to acceptable
    For me, that was when I installed Linux :-)
    --
    In theory, there is no difference between theory and practice.
    In practice, there is.
    -- Yogi Berra

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lars Poulsen@lars@beagle-ears.com to comp.os.linux.misc on Sat Nov 7 15:26:09 2026
    From Newsgroup: comp.os.linux.misc

    On 11/7/2026 10:30, rbowman wrote:
    On Sat, 7 Nov 2026 06:39:57 -0800, Lars Poulsen wrote:

    On 11/6/2026 18:41, rbowman wrote:
    On Fri, 06 Nov 2026 20:51:50 GMT, Charlie Gibbs wrote:

    I should get one of those T-shirts that says,

    There is no Cloud.
    It's just someone else's computer.

    I got some funny looks when I said we were already using a private
    cloud.
    Most of the companies that were touting a cloud solution for emergency
    services software backed off. Some of the security requirements assumed
    the computer would be surrounded by armed responders,

    As I understand it, that is a reasonable assumption in your local
    region? (Even for a "private cloud".)

    Yes. Interfacing with the NCIC carries a number of requirements.

    https://en.wikipedia.org/wiki/National_Crime_Information_Center

    In addition state CJIN (Criminal Justice Information Network) impose their requirements. Even our support people had to be vetted and finger printed before accessing a site. In theory I could look over their shoulder but couldn't access the sites myself. I carefully avoided the certification to maintain separation from the support tasks.

    The theory broke down when the support people brought back logs but we
    didn't talk about that. I'll admit I saw some juicy stuff.

    NCIC tried to respond to the implications of off-premises clouds. HIPAA
    also had an oar in the water.

    https://www.hhs.gov/hipaa/index.html

    My comment was mean to be snarky: I think you live in either Montana and Wyoming, in a rural county with lots of survivalists running around, so
    a goodly number of employees of any company can be expected to armed at
    their workplaces.
    --
    Lars Poulsen - an old geek in Santa Barbara, California
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc on Sun Nov 8 01:01:03 2026
    From Newsgroup: comp.os.linux.misc

    On Sat, 7 Nov 2026 21:55:56 +0000, The Natural Philosopher wrote:

    On 07/11/2026 18:01, rbowman wrote:
    I can't pinpoint an exact date but there was a watershed where PCs went
    from painfully slow to acceptable
    For me, that was when I installed Linux :-)

    Linux certainly helped but it went from start a build and go to lunch
    around 2000 to start a build and answer a couple of emails somewhere along
    the way.

    Meanwhile Windows was still start a Patch Tuesday update and go to lunch
    on good days. On bad days it was start the update and hope the machine
    would be usable the next morning. I still haven't done last month's patch
    on the Win 11 laptop. I wonder how screwed I'll be next week?
    --- 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: comp.os.linux.misc

    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 rbowman@bowman@montana.com to comp.os.linux.misc on Sun Nov 8 01:15:20 2026
    From Newsgroup: comp.os.linux.misc

    On Sat, 7 Nov 2026 15:26:09 -0800, Lars Poulsen wrote:

    My comment was mean to be snarky: I think you live in either Montana and Wyoming, in a rural county with lots of survivalists running around, so
    a goodly number of employees of any company can be expected to armed at
    their workplaces.

    I think there was something in the employee handbook about that but there
    were no metal detectors. I never felt the need.

    That said the programming department did have a yearly day at the range as sort of a bonding exercise. There was everything from muzzle loaders on
    up.




    --- 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: comp.os.linux.misc

    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 Robert Riches@spamtrap42@jacob21819.net to comp.os.linux.misc on Sun Nov 8 04:23:01 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-08, Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
    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.

    A piece of (grounded) anti-ESD foam from an integrated circuit
    order might have drained off the charge with perhaps less risk of
    even small sparks. One of the advantages of the carbon-based
    black back-coating Ampex put on their higher-end audio recording
    tapes back in the day was prevention of static build-up.

    Within a few years either side of 1980, a professor in an EE
    class told a story from early in his career. He was hired by GE
    to work on _BIG_ (as in 8 feet to 16 feet diameter) motors and
    generators. He said GE would hire EEs and teach them mechanical
    stuff, because that worked better than hiring MEs and teaching
    them electrical stuff.

    He was tasked with solving a problem with premature bearing
    failure. When a failed machine was torn down, basically all the
    failed bearings were found to be coated with varnish. It turns
    out the moving parts within the bearing assembly were building up
    a static electric charge, which would eventually arc through the
    oil, creating a small spot of varnish. Eventually, the varnish
    would build up, and the bearing would fail.

    The solution was to add something to the oil to make it slightly
    conductive to electricity. Management told him he had just
    earned his salary for his entire career--and to go do it again.

    The professor's last name was Clegg. He taught at Brigham Young
    University.
    --
    Robert Riches
    spamtrap42@jacob21819.net
    (Yes, that is one of my email addresses.)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc on Sun Nov 8 05:00:42 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-08, Robert Riches <spamtrap42@jacob21819.net> wrote:

    On 2026-11-08, Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:

    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.

    A piece of (grounded) anti-ESD foam from an integrated circuit
    order might have drained off the charge with perhaps less risk of
    even small sparks. One of the advantages of the carbon-based
    black back-coating Ampex put on their higher-end audio recording
    tapes back in the day was prevention of static build-up.

    We didn't think of that. Hmmm...

    Speaking of back-coated tapes, we had a few back-coated 9-track
    tapes in our shop. A customer who was leaving us asked to have
    his data written onto a tape, and we happened to grab one of the
    back-coated tapes. A few days later we got an angry call from
    said [ex-]customer accusing us of sabotaging them. They didn't
    know about back-coated tapes, so they automatically assumed that
    the back of the tape was always shiny Mylar. When they saw the
    dull backing of the back-coated tape, they assumed we had wound it
    onto a spool back-to-front to screw them up. Without even trying
    to read the tape first, they-respooled it so it really was on the
    reel back-to-front. Naturally, it didn't read too well. Once we
    got them to re-spool it properly (i.e. they way we gave it to them)
    all went well.

    Within a few years either side of 1980, a professor in an EE
    class told a story from early in his career. He was hired by GE
    to work on _BIG_ (as in 8 feet to 16 feet diameter) motors and
    generators. He said GE would hire EEs and teach them mechanical
    stuff, because that worked better than hiring MEs and teaching
    them electrical stuff.

    Interesting. As part of my commercial pilot course, our instructor
    arranged a tour of our local area control center. We were shown all
    the computer equipment (mostly DEC in those days). Our tour guide
    said much the same thing: it was easier to teach controllers about
    computers than to teach computer people about air traffic control.
    --
    /~\ 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 Joel W. Crump@joelcrump@gmail.com to comp.os.linux.misc,comp.os.linux.advocacy on Sun Nov 8 00:33:38 2026
    From Newsgroup: comp.os.linux.misc

    On 11/7/2026 3:54 PM, c186282 wrote:
    On 11/7/26 13:01, Joel W. Crump wrote:
    On 11/6/2026 9:50 PM, rbowman wrote:

    I saw Linux on a four-core machine with a SATA SSD, and on a
    six-core/12-thread and a four-core/four-thread both with NVMe storage, >>>> it matters plenty if one wants more than your unserviceable rig.

    I replaced the HDDs on a couple of older machines with SATA SSDs. The
    most
    noticeable improvement was on reboot since I don't do any disk intensive >>> stuff. Starting individual programs wasn't appreciably faster. SSDs
    allowed SATA to achieve its maximum performance, something I don't think >>> even the best HDDs could.

    It's still slower than NVMe but not a show stopper.

    Larry gets performance from an HDD because there's barely anything
    being loaded/swapped.

    -a Yet another case of "What Do YOU Need ?"

    -a I much appreciated what the Samsung did for a
    -a slightly older lap (had a WD Blue originally)
    -a especially for the boot-up. Fatter apps start
    -a up a bit quicker too. But my uses are
    -a all "home" now and I don't do much you'd
    -a really call "disk intensive". My "NAS" is
    -a an external 4-dr USB unit linked with NFS - the
    -a wifi/USB latency negates any speed advantage
    -a of SSDs.

    -a So, I can save money with magnetic drives.

    -a Now for an office server with a bunch of cat-6
    -a wires going everywhere, NOW you may feel the
    -a need for speed.


    From my point of view, certain things have simply become obsolete.
    Making a Mini PC replace my huge-by-comparison self-assembled system
    means that they are serious gear.
    --
    Joel W. Crump
    --- 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: comp.os.linux.misc

    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 The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc on Sun Nov 8 11:28:04 2026
    From Newsgroup: comp.os.linux.misc

    On 07/11/2026 23:26, Lars Poulsen wrote:
    ...in either Montana and Wyoming, in a rural county with lots of survivalists running around, so a goodly number of employees of any
    company can be expected to armed at their workplaces.

    Interesting correlation you make.
    Why would survivalists (so called) be especially armed *at work* ?
    --
    There is nothing a fleet of dispatchable nuclear power plants cannot do
    that cannot be done worse and more expensively and with higher carbon emissions and more adverse environmental impact by adding intermittent renewable energy.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Kerr-Mudd, John@admin@127.0.0.1 to comp.os.linux.misc,alt.folklore.computers on Sun Nov 8 14:32:12 2026
    From Newsgroup: comp.os.linux.misc

    On Sat, 7 Nov 2026 18:40:54 +0800
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    On 11/6/2026 2:18 PM, Lawrence DrCOOliveiro wrote:
    On Fri, 6 Nov 2026 05:59:51 -0000 (UTC), Beej Jorgensen wrote:

    We had one 9-track when I worked as a computer operator in 1992. It
    was used to send financial records to the bank. That was the first
    and last one I saw in use.

    A decade earlier, it was a slightly different story.

    Also, back then, it was still the fashion in movies and TV to portray
    a computer as having lots of tape drives with the reels spinning
    busily, as though such heavy tape usage was characteristic of normal computer operation. That would have been true a decade before that,
    but by the time the 1980s came along, tapes were primarily used for
    backup and data interchange between installations.

    Furthermore, back then, there was real difficulty in getting data
    between different brands of personal computers, because of
    incompatible floppy disk formats, and many machines not even having
    floppy drives. But there was this open protocol called rCLKermitrCY, which ran on serial lines (or modem connections), for which implementations
    were available for just about every kind of computer under the sun,
    big and small.

    And you could get copies free, just by sending a blank reel of tape to
    the University of Columbia; they would put all the latest versions of
    all the releases on that, and send it back.

    Now now Lawrence, don't act like it's all gone. You can still get it,
    and use it, at

    https://www.kermitproject.org/index.html


    Rivetting stuff!

    and

    https://davidrg.github.io/ckwin/

    to transfer files with all kinds of protocols. I used it in recent
    years to transfer files between FreeDOS computer and Windows 10, so
    it's definitely still useful.

    I trust it supports Xmodem?

    Procomm plus is the only way!

    Information and download links for MS-DOS Kermit can be found here,

    https://www.kermitproject.org/mskermit.html

    and you can even download and read the book /Using MS-DOS Kermit/, 2nd edition from that website.

    I'm sure someone in the retrocomputing hobby at alt.folklore.computers
    can make use of these software packages, perhaps after two hundred
    years; so it's definitely worth mentioning.


    Best wishes and happy Kermit!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --
    Bah, and indeed Humbug.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc on Sun Nov 8 18:14:48 2026
    From Newsgroup: comp.os.linux.misc

    On Sun, 8 Nov 2026 11:28:04 +0000, The Natural Philosopher wrote:

    On 07/11/2026 23:26, Lars Poulsen wrote:
    ...in either Montana and Wyoming, in a rural county with lots of
    survivalists running around, so a goodly number of employees of any
    company can be expected to armed at their workplaces.

    Interesting correlation you make.
    Why would survivalists (so called) be especially armed *at work* ?

    Open carry has always been legal in this state except for court houses, saloons, and a few other places. While I've seen people carrying in the library or market they are very, very rare. They're also the people that
    cause me to formulate a plan in case the situation goes south.

    There may be more concealed firearms but concealment is rather the point.

    My original statement concerned PSAPs

    https://en.wikipedia.org/wiki/Public_safety_answering_point

    They aren't necessarily in police stations but often are. Even if they are
    not access is restricted. By their nature they are privy to sensitive
    criminal and medical information.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc on Sun Nov 8 20:50:06 2026
    From Newsgroup: comp.os.linux.misc

    On 11/8/26 00:00, Charlie Gibbs wrote:
    On 2026-11-08, Robert Riches <spamtrap42@jacob21819.net> wrote:

    On 2026-11-08, Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:

    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.

    A piece of (grounded) anti-ESD foam from an integrated circuit
    order might have drained off the charge with perhaps less risk of
    even small sparks. One of the advantages of the carbon-based
    black back-coating Ampex put on their higher-end audio recording
    tapes back in the day was prevention of static build-up.

    We didn't think of that. Hmmm...


    Um ... when was anti-static foam INVENTED ?

    As I recall the original stuff was quite stiff
    and brittle.

    Anyway, you sort of re-invented a van-DeGraff
    generator with yer fast-moving tape :-)


    Speaking of back-coated tapes, we had a few back-coated 9-track
    tapes in our shop. A customer who was leaving us asked to have
    his data written onto a tape, and we happened to grab one of the
    back-coated tapes. A few days later we got an angry call from
    said [ex-]customer accusing us of sabotaging them. They didn't
    know about back-coated tapes, so they automatically assumed that
    the back of the tape was always shiny Mylar. When they saw the
    dull backing of the back-coated tape, they assumed we had wound it
    onto a spool back-to-front to screw them up. Without even trying
    to read the tape first, they-respooled it so it really was on the
    reel back-to-front. Naturally, it didn't read too well. Once we
    got them to re-spool it properly (i.e. they way we gave it to them)
    all went well.

    Within a few years either side of 1980, a professor in an EE
    class told a story from early in his career. He was hired by GE
    to work on _BIG_ (as in 8 feet to 16 feet diameter) motors and
    generators. He said GE would hire EEs and teach them mechanical
    stuff, because that worked better than hiring MEs and teaching
    them electrical stuff.

    Interesting. As part of my commercial pilot course, our instructor
    arranged a tour of our local area control center. We were shown all
    the computer equipment (mostly DEC in those days). Our tour guide
    said much the same thing: it was easier to teach controllers about
    computers than to teach computer people about air traffic control.

    Huge generators/motors are nothing new. My dad used
    to wire those up, some SIX-phase, in the early 40s.
    Then the Japanese showed up one Sunday and blew up
    a lot of them .......

    They wouldn't let him join the mil, they needed
    everything on Hawaii re/over-built FAST. He was
    not even allowed to leave the island until '45.

    As for the who-is-easier-to-teach thing, I kinda agree
    with your observations/experiences. The "theory" people
    tend to have no practical sense, but the practical people
    can be taught ENOUGH theory.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc,comp.os.linux.advocacy on Sun Nov 8 21:05:54 2026
    From Newsgroup: comp.os.linux.misc

    On 11/8/26 00:33, Joel W. Crump wrote:
    On 11/7/2026 3:54 PM, c186282 wrote:
    On 11/7/26 13:01, Joel W. Crump wrote:
    On 11/6/2026 9:50 PM, rbowman wrote:

    I saw Linux on a four-core machine with a SATA SSD, and on a
    six-core/12-thread and a four-core/four-thread both with NVMe storage, >>>>> it matters plenty if one wants more than your unserviceable rig.

    I replaced the HDDs on a couple of older machines with SATA SSDs.
    The most
    noticeable improvement was on reboot since I don't do any disk
    intensive
    stuff. Starting individual programs wasn't appreciably faster. SSDs
    allowed SATA to achieve its maximum performance, something I don't
    think
    even the best HDDs could.

    It's still slower than NVMe but not a show stopper.

    Larry gets performance from an HDD because there's barely anything
    being loaded/swapped.

    -a-a Yet another case of "What Do YOU Need ?"

    -a-a I much appreciated what the Samsung did for a
    -a-a slightly older lap (had a WD Blue originally)
    -a-a especially for the boot-up. Fatter apps start
    -a-a up a bit quicker too. But my uses are
    -a-a all "home" now and I don't do much you'd
    -a-a really call "disk intensive". My "NAS" is
    -a-a an external 4-dr USB unit linked with NFS - the
    -a-a wifi/USB latency negates any speed advantage
    -a-a of SSDs.

    -a-a So, I can save money with magnetic drives.

    -a-a Now for an office server with a bunch of cat-6
    -a-a wires going everywhere, NOW you may feel the
    -a-a need for speed.


    From my point of view, certain things have simply become obsolete.
    Making a Mini PC replace my huge-by-comparison self-assembled system
    means that they are serious gear.

    The mini-PCs ... BMax and BeeLink of note ... are VERY
    nice units, esp for Linux. Have four of the 'cheap-laptop'
    power ones. MORE than enough for Linux, speedy, WERE
    cheap before the tariff wars and AI memory grab. Versions
    with more CPU are (were?) to be had.

    I do have a high-end i5 with plenty of mem and a SSD.
    Assembled it ... but it's still sitting in the back
    room doing nothing. Laptops, with Linux, perform Well
    Enough for everything I'm doing now.

    IF you are doing lots of GIS or engineering/physics
    or cutting-edge games then you DO need a super-
    powerful PC. But for MOST stuff ....

    --- 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: comp.os.linux.misc

    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 c186282@c186282@nnada.net to comp.os.linux.misc,alt.folklore.computers on Sun Nov 8 21:31:30 2026
    From Newsgroup: comp.os.linux.misc

    On 11/8/26 09:32, Kerr-Mudd, John wrote:
    On Sat, 7 Nov 2026 18:40:54 +0800
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    On 11/6/2026 2:18 PM, Lawrence DrCOOliveiro wrote:
    On Fri, 6 Nov 2026 05:59:51 -0000 (UTC), Beej Jorgensen wrote:

    We had one 9-track when I worked as a computer operator in 1992. It
    was used to send financial records to the bank. That was the first
    and last one I saw in use.

    A decade earlier, it was a slightly different story.

    Also, back then, it was still the fashion in movies and TV to portray
    a computer as having lots of tape drives with the reels spinning
    busily, as though such heavy tape usage was characteristic of normal
    computer operation. That would have been true a decade before that,
    but by the time the 1980s came along, tapes were primarily used for
    backup and data interchange between installations.

    Furthermore, back then, there was real difficulty in getting data
    between different brands of personal computers, because of
    incompatible floppy disk formats, and many machines not even having
    floppy drives. But there was this open protocol called rCLKermitrCY, which >>> ran on serial lines (or modem connections), for which implementations
    were available for just about every kind of computer under the sun,
    big and small.

    And you could get copies free, just by sending a blank reel of tape to
    the University of Columbia; they would put all the latest versions of
    all the releases on that, and send it back.

    Now now Lawrence, don't act like it's all gone. You can still get it,
    and use it, at

    https://www.kermitproject.org/index.html


    Rivetting stuff!

    and

    https://davidrg.github.io/ckwin/

    to transfer files with all kinds of protocols. I used it in recent
    years to transfer files between FreeDOS computer and Windows 10, so
    it's definitely still useful.

    I trust it supports Xmodem?

    Procomm plus is the only way!


    Used Procomm a LOT. Great app !!!

    Kermit IS pretty good though.

    --- 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: comp.os.linux.misc

    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 Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc on Mon Nov 9 03:53:27 2026
    From Newsgroup: comp.os.linux.misc

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

    On 11/8/26 00:00, Charlie Gibbs wrote:

    On 2026-11-08, Robert Riches <spamtrap42@jacob21819.net> wrote:

    On 2026-11-08, Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:

    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.

    A piece of (grounded) anti-ESD foam from an integrated circuit
    order might have drained off the charge with perhaps less risk of
    even small sparks. One of the advantages of the carbon-based
    black back-coating Ampex put on their higher-end audio recording
    tapes back in the day was prevention of static build-up.

    We didn't think of that. Hmmm...

    Um ... when was anti-static foam INVENTED ?

    As I recall the original stuff was quite stiff
    and brittle.

    Anyway, you sort of re-invented a van-DeGraff
    generator with yer fast-moving tape :-)

    That's the way I thought of it. :-)
    --
    /~\ 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 c186282@c186282@nnada.net to alt.folklore.computers,comp.os.linux.misc on Sun Nov 8 22:54:22 2026
    From Newsgroup: comp.os.linux.misc

    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: comp.os.linux.misc

    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: comp.os.linux.misc

    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: comp.os.linux.misc

    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: comp.os.linux.misc

    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: comp.os.linux.misc

    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: comp.os.linux.misc

    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: comp.os.linux.misc

    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: comp.os.linux.misc

    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: comp.os.linux.misc

    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: comp.os.linux.misc

    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: comp.os.linux.misc

    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: comp.os.linux.misc

    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: comp.os.linux.misc

    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: comp.os.linux.misc

    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 Joel W. Crump@joelcrump@gmail.com to comp.os.linux.misc,comp.os.linux.advocacy on Tue Nov 10 05:30:01 2026
    From Newsgroup: comp.os.linux.misc

    On 11/8/2026 9:05 PM, c186282 wrote:

    -aFrom my point of view, certain things have simply become obsolete.
    Making a Mini PC replace my huge-by-comparison self-assembled system
    means that they are serious gear.

    -a The mini-PCs ... BMax and BeeLink of note ... are VERY
    -a nice units, esp for Linux. Have four of the 'cheap-laptop'
    -a power ones. MORE than enough for Linux, speedy, WERE
    -a cheap before the tariff wars and AI memory grab. Versions
    -a with more CPU are (were?) to be had.

    -a I do have a high-end i5 with plenty of mem and a SSD.
    -a Assembled it ... but it's still sitting in the back
    -a room doing nothing. Laptops, with Linux, perform Well
    -a Enough for everything I'm doing now.

    -a IF you are doing lots of GIS or engineering/physics
    -a or cutting-edge games then you DO need a super-
    -a powerful PC. But for MOST stuff ....


    Linux can run on all of them, yes, but I'm even getting perfectly
    adequate performance from Win11, eight-thread CPU with 13 GB usable RAM,
    seems a good realistic minimum and all I really need.
    --
    Joel W. Crump
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to comp.os.linux.misc on Tue Nov 10 15:01:41 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-08 05:23, Robert Riches wrote:
    On 2026-11-08, Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
    On 2026-11-07, Lars Poulsen <lars@beagle-ears.com> wrote:


    Within a few years either side of 1980, a professor in an EE
    class told a story from early in his career. He was hired by GE
    to work on _BIG_ (as in 8 feet to 16 feet diameter) motors and
    generators. He said GE would hire EEs and teach them mechanical
    stuff, because that worked better than hiring MEs and teaching
    them electrical stuff.

    He was tasked with solving a problem with premature bearing
    failure. When a failed machine was torn down, basically all the
    failed bearings were found to be coated with varnish. It turns
    out the moving parts within the bearing assembly were building up
    a static electric charge, which would eventually arc through the
    oil, creating a small spot of varnish. Eventually, the varnish
    would build up, and the bearing would fail.

    The solution was to add something to the oil to make it slightly
    conductive to electricity. Management told him he had just
    earned his salary for his entire career--and to go do it again.

    Wow.


    The professor's last name was Clegg. He taught at Brigham Young
    University.

    --
    Cheers, Carlos.
    ESEfc-Efc+, EUEfc-Efc|;
    --- 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: comp.os.linux.misc

    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 Carlos E.R.@robin_listas@es.invalid to comp.os.linux.misc on Tue Nov 10 15:06:15 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-08 06:00, Charlie Gibbs wrote:
    On 2026-11-08, Robert Riches <spamtrap42@jacob21819.net> wrote:

    On 2026-11-08, Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:

    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.

    A piece of (grounded) anti-ESD foam from an integrated circuit
    order might have drained off the charge with perhaps less risk of
    even small sparks. One of the advantages of the carbon-based
    black back-coating Ampex put on their higher-end audio recording
    tapes back in the day was prevention of static build-up.

    We didn't think of that. Hmmm...

    Speaking of back-coated tapes, we had a few back-coated 9-track
    tapes in our shop. A customer who was leaving us asked to have
    his data written onto a tape, and we happened to grab one of the
    back-coated tapes. A few days later we got an angry call from
    said [ex-]customer accusing us of sabotaging them. They didn't
    know about back-coated tapes, so they automatically assumed that
    the back of the tape was always shiny Mylar. When they saw the
    dull backing of the back-coated tape, they assumed we had wound it
    onto a spool back-to-front to screw them up. Without even trying
    to read the tape first, they-respooled it so it really was on the
    reel back-to-front. Naturally, it didn't read too well. Once we
    got them to re-spool it properly (i.e. they way we gave it to them)
    all went well.

    Within a few years either side of 1980, a professor in an EE
    class told a story from early in his career. He was hired by GE
    to work on _BIG_ (as in 8 feet to 16 feet diameter) motors and
    generators. He said GE would hire EEs and teach them mechanical
    stuff, because that worked better than hiring MEs and teaching
    them electrical stuff.

    Interesting. As part of my commercial pilot course, our instructor
    arranged a tour of our local area control center. We were shown all
    the computer equipment (mostly DEC in those days). Our tour guide
    said much the same thing: it was easier to teach controllers about
    computers than to teach computer people about air traffic control.

    I was hired to do programming, despite my field being electronics,
    because the boss thought that it was easier to had en electronics
    engineer doing software than software engineers understanding electronics.

    He was happy that he could send me to clients for both type of problems.
    --
    Cheers, Carlos.
    ESEfc-Efc+, EUEfc-Efc|;
    --- 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: comp.os.linux.misc

    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: comp.os.linux.misc

    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 Robert Riches@spamtrap42@jacob21819.net to comp.os.linux.misc on Tue Nov 10 18:06:17 2026
    From Newsgroup: comp.os.linux.misc

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

    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 !

    I was told by a (different) professor that he once witnessed a washing-machine-sized disk drive that got a fleck of dust under a
    head, which rather quickly cascaded to a shaving of most/all of
    the oxide. He said he and his coworkers used square-mouthed
    shovels to scoop the shredded oxide out of the cabinet.
    --
    Robert Riches
    spamtrap42@jacob21819.net
    (Yes, that is one of my email addresses.)
    --- 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: comp.os.linux.misc

    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: comp.os.linux.misc

    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 Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.os.linux.misc on Tue Nov 10 18:45:11 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-10, Robert Riches <spamtrap42@jacob21819.net> wrote:

    I was told by a (different) professor that he once witnessed a washing-machine-sized disk drive that got a fleck of dust under a
    head, which rather quickly cascaded to a shaving of most/all of
    the oxide. He said he and his coworkers used square-mouthed
    shovels to scoop the shredded oxide out of the cabinet.

    One head crash we had was bad enough that you could see bits
    of bare aluminum gleaming among the debris on the pack.
    (I never did see one that sprayed oxide around much.)

    One day we had a CE in to do preventive maintenance on our
    drives. While the CE was bent over with his head in the
    drive well, someone came in and asked me what he was doing.
    I explained, with a straight face, that he was adjusting the
    speed at which the disk pack spun, since if it spun too fast
    the bits would come flying off and have to be scraped off the
    inside of the well.
    --
    /~\ 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 comp.os.linux.misc on Tue Nov 10 19:11:07 2026
    From Newsgroup: comp.os.linux.misc

    On Tue, 10 Nov 2026 15:06:15 +0100, Carlos E.R. wrote:

    I was hired to do programming, despite my field being electronics,
    because the boss thought that it was easier to had en electronics
    engineer doing software than software engineers understanding
    electronics.

    He was happy that he could send me to clients for both type of problems.

    My progression from hardware to software not planned but occurred as microprocessors were integrated into industrial controllers. It was
    helpful to have a feeling for hardware constraints. I missed the hardware
    as I got further into the metaphorical world. Pixels representing a skeuomorphic push button aren't a push button.
    --- 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: comp.os.linux.misc

    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: comp.os.linux.misc

    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: comp.os.linux.misc

    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 comp.os.linux.misc,comp.os.linux.advocacy on Tue Nov 10 22:03:31 2026
    From Newsgroup: comp.os.linux.misc

    On 11/10/26 05:30, Joel W. Crump wrote:
    On 11/8/2026 9:05 PM, c186282 wrote:

    -aFrom my point of view, certain things have simply become obsolete.
    Making a Mini PC replace my huge-by-comparison self-assembled system
    means that they are serious gear.

    -a-a The mini-PCs ... BMax and BeeLink of note ... are VERY
    -a-a nice units, esp for Linux. Have four of the 'cheap-laptop'
    -a-a power ones. MORE than enough for Linux, speedy, WERE
    -a-a cheap before the tariff wars and AI memory grab. Versions
    -a-a with more CPU are (were?) to be had.

    -a-a I do have a high-end i5 with plenty of mem and a SSD.
    -a-a Assembled it ... but it's still sitting in the back
    -a-a room doing nothing. Laptops, with Linux, perform Well
    -a-a Enough for everything I'm doing now.

    -a-a IF you are doing lots of GIS or engineering/physics
    -a-a or cutting-edge games then you DO need a super-
    -a-a powerful PC. But for MOST stuff ....


    Linux can run on all of them, yes, but I'm even getting perfectly
    adequate performance from Win11, eight-thread CPU with 13 GB usable RAM, seems a good realistic minimum and all I really need.

    For all I'm doing NOW ... yes ... the 'mini PCs'
    can do it all very efficiently with Linux. NUKE
    the pre-installed Winders immediately.

    My home apps are mostly Python now, lots of OpenCV
    and FFMPEG work. One cheapo home 'NAS'. The units
    don't choke. "Good Enough" for LOW investment.
    I'm happy.

    PREF MX Linux - not TOO big or TOO small and
    has some nice little perks.

    Office/department servers with dozens of clients
    and maybe external access - THEN you need more
    horsepower.

    So, scale For The Need.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc on Tue Nov 10 22:45:36 2026
    From Newsgroup: comp.os.linux.misc

    On 11/10/26 09:01, Carlos E.R. wrote:
    On 2026-11-08 05:23, Robert Riches wrote:
    On 2026-11-08, Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
    On 2026-11-07, Lars Poulsen <lars@beagle-ears.com> wrote:


    Within a few years either side of 1980, a professor in an EE
    class told a story from early in his career.-a He was hired by GE
    to work on _BIG_ (as in 8 feet to 16 feet diameter) motors and
    generators.-a He said GE would hire EEs and teach them mechanical
    stuff, because that worked better than hiring MEs and teaching
    them electrical stuff.

    He was tasked with solving a problem with premature bearing
    failure.-a When a failed machine was torn down, basically all the
    failed bearings were found to be coated with varnish.-a It turns
    out the moving parts within the bearing assembly were building up
    a static electric charge, which would eventually arc through the
    oil, creating a small spot of varnish.-a Eventually, the varnish
    would build up, and the bearing would fail.

    The solution was to add something to the oil to make it slightly
    conductive to electricity.-a Management told him he had just
    earned his salary for his entire career--and to go do it again.

    Wow.


    The professor's last name was Clegg.-a He taught at Brigham Young
    University.

    "Corporal Clegg, had a wooden leg. He won
    in the war, in 1944" ......... :-)

    As for BYU ... the Mormons aren't stupid, just
    kinda weird. But hey, a dozen nubile young
    brides ... who's gonna complain eh ? :-)

    Now never heard of INTENTIONALLY conductive oil.
    This is interesting.

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

    On 11/10/26 09:06, Carlos E.R. wrote:
    On 2026-11-08 06:00, Charlie Gibbs wrote:
    On 2026-11-08, Robert Riches <spamtrap42@jacob21819.net> wrote:

    On 2026-11-08, Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:

    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-a running at full speed!

    My first job was programming a Univac 9300 which had an RC2000
    interfaced to it.-a 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 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.-a 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.-a 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.

    A piece of (grounded) anti-ESD foam from an integrated circuit
    order might have drained off the charge with perhaps less risk of
    even small sparks.-a One of the advantages of the carbon-based
    black back-coating Ampex put on their higher-end audio recording
    tapes back in the day was prevention of static build-up.

    We didn't think of that.-a Hmmm...

    Speaking of back-coated tapes, we had a few back-coated 9-track
    tapes in our shop.-a A customer who was leaving us asked to have
    his data written onto a tape, and we happened to grab one of the
    back-coated tapes.-a A few days later we got an angry call from
    said [ex-]customer accusing us of sabotaging them.-a They didn't
    know about back-coated tapes, so they automatically assumed that
    the back of the tape was always shiny Mylar.-a When they saw the
    dull backing of the back-coated tape, they assumed we had wound it
    onto a spool back-to-front to screw them up.-a Without even trying
    to read the tape first, they-respooled it so it really was on the
    reel back-to-front.-a Naturally, it didn't read too well.-a Once we
    got them to re-spool it properly (i.e. they way we gave it to them)
    all went well.

    Within a few years either side of 1980, a professor in an EE
    class told a story from early in his career.-a He was hired by GE
    to work on _BIG_ (as in 8 feet to 16 feet diameter) motors and
    generators.-a He said GE would hire EEs and teach them mechanical
    stuff, because that worked better than hiring MEs and teaching
    them electrical stuff.

    Interesting.-a As part of my commercial pilot course, our instructor
    arranged a tour of our local area control center.-a We were shown all
    the computer equipment (mostly DEC in those days).-a Our tour guide
    said much the same thing: it was easier to teach controllers about
    computers than to teach computer people about air traffic control.

    I was hired to do programming, despite my field being electronics,
    because the boss thought that it was easier to had en electronics
    engineer doing software than software engineers understanding electronics.

    Very TRUE ! :-)

    Can do SOME electronics - pref digital, analog
    is SO fiddly. Lots of 'specialty' boards for
    various projects.

    DO buy some kind of "scope" - mystery problem
    was revealed once as an over-draw caused by
    an external device powering-up. Just a VERY
    narrow bit on the scope output - but DID
    reveal the minor design fault.

    He was happy that he could send me to clients for both type of problems.

    I did 40+ years as a Jack Of All Trades.
    Pension is now more than I made while
    working :-)

    Joe/Trump-flation will cut into that.

    Of interest, "salary eval" outside group.
    When I mentioned doing "embedded" apps
    my figure went way up. Even had the docs
    and drawings ... but they didn't need them
    (and wouldn't understand them anyway).

    --- 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: comp.os.linux.misc

    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: comp.os.linux.misc

    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 c186282@c186282@nnada.net to comp.os.linux.misc on Wed Nov 11 00:03:17 2026
    From Newsgroup: comp.os.linux.misc

    On 11/10/26 13:06, Robert Riches wrote:
    On 2026-11-10, c186282 <c186282@nnada.net> wrote:

    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 !

    I was told by a (different) professor that he once witnessed a washing-machine-sized disk drive that got a fleck of dust under a
    head, which rather quickly cascaded to a shaving of most/all of
    the oxide. He said he and his coworkers used square-mouthed
    shovels to scoop the shredded oxide out of the cabinet.

    Ummmmmm ... VERY VERY odd phrasing :-)

    As for the old "removable platter" HDDs, they
    were actually pretty good. Just DON't be tempted
    to pull 'em out while they are still spinning.
    SAW that once :-)


    --- 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: comp.os.linux.misc

    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
  • From Carlos E.R.@robin_listas@es.invalid to comp.os.linux.misc on Wed Nov 11 13:38:58 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-08 05:23, Robert Riches wrote:
    On 2026-11-08, Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
    On 2026-11-07, Lars Poulsen <lars@beagle-ears.com> wrote:


    Within a few years either side of 1980, a professor in an EE
    class told a story from early in his career. He was hired by GE
    to work on _BIG_ (as in 8 feet to 16 feet diameter) motors and
    generators. He said GE would hire EEs and teach them mechanical
    stuff, because that worked better than hiring MEs and teaching
    them electrical stuff.

    He was tasked with solving a problem with premature bearing
    failure. When a failed machine was torn down, basically all the
    failed bearings were found to be coated with varnish. It turns
    out the moving parts within the bearing assembly were building up
    a static electric charge, which would eventually arc through the
    oil, creating a small spot of varnish. Eventually, the varnish
    would build up, and the bearing would fail.

    The solution was to add something to the oil to make it slightly
    conductive to electricity. Management told him he had just
    earned his salary for his entire career--and to go do it again.

    The professor's last name was Clegg. He taught at Brigham Young
    University.


    There is something I don't understand. The entire machine would be built
    of metal, except the insulation on the coils. Ball bearings are metal,
    the balls are made of metal. How could the static build up? Maybe the
    oil layer was insulation enough?
    --
    Cheers, Carlos.
    ESEfc-Efc+, EUEfc-Efc|;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Robert Riches@spamtrap42@jacob21819.net to comp.os.linux.misc on Wed Nov 11 15:09:11 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-11, Carlos E.R. <robin_listas@es.invalid> wrote:
    On 2026-11-08 05:23, Robert Riches wrote:
    On 2026-11-08, Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
    On 2026-11-07, Lars Poulsen <lars@beagle-ears.com> wrote:


    Within a few years either side of 1980, a professor in an EE
    class told a story from early in his career. He was hired by GE
    to work on _BIG_ (as in 8 feet to 16 feet diameter) motors and
    generators. He said GE would hire EEs and teach them mechanical
    stuff, because that worked better than hiring MEs and teaching
    them electrical stuff.

    He was tasked with solving a problem with premature bearing
    failure. When a failed machine was torn down, basically all the
    failed bearings were found to be coated with varnish. It turns
    out the moving parts within the bearing assembly were building up
    a static electric charge, which would eventually arc through the
    oil, creating a small spot of varnish. Eventually, the varnish
    would build up, and the bearing would fail.

    The solution was to add something to the oil to make it slightly
    conductive to electricity. Management told him he had just
    earned his salary for his entire career--and to go do it again.

    The professor's last name was Clegg. He taught at Brigham Young
    University.


    There is something I don't understand. The entire machine would be built
    of metal, except the insulation on the coils. Ball bearings are metal,
    the balls are made of metal. How could the static build up? Maybe the
    oil layer was insulation enough?

    That's what I had understood he was saying. Prior to the
    additive being put in the oil, the oil insulated the bearing
    components from each other well enough for a voltage difference
    to build up that would arc through the oil and convert the oil to
    varnish and eventually cause the bearing unit to fail--and the
    additive made enough of a difference to prolong the life of the
    bearings.
    --
    Robert Riches
    spamtrap42@jacob21819.net
    (Yes, that is one of my email addresses.)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Rich@rich@example.invalid to comp.os.linux.misc on Wed Nov 11 16:35:30 2026
    From Newsgroup: comp.os.linux.misc

    Carlos E.R. <robin_listas@es.invalid> wrote:
    On 2026-11-08 05:23, Robert Riches wrote:
    On 2026-11-08, Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
    On 2026-11-07, Lars Poulsen <lars@beagle-ears.com> wrote:


    Within a few years either side of 1980, a professor in an EE class
    told a story from early in his career. He was hired by GE to work
    on _BIG_ (as in 8 feet to 16 feet diameter) motors and generators.
    He said GE would hire EEs and teach them mechanical stuff, because
    that worked better than hiring MEs and teaching them electrical
    stuff.

    He was tasked with solving a problem with premature bearing failure.
    When a failed machine was torn down, basically all the failed
    bearings were found to be coated with varnish. It turns out the
    moving parts within the bearing assembly were building up a static
    electric charge, which would eventually arc through the oil,
    creating a small spot of varnish. Eventually, the varnish would
    build up, and the bearing would fail.

    The solution was to add something to the oil to make it slightly
    conductive to electricity. Management told him he had just earned
    his salary for his entire career--and to go do it again.

    The professor's last name was Clegg. He taught at Brigham Young
    University.


    There is something I don't understand. The entire machine would be
    built of metal, except the insulation on the coils. Ball bearings
    are metal, the balls are made of metal. How could the static build
    up? Maybe the oil layer was insulation enough?

    Oil functions to lubricate moving parts by forming a very thin liquid
    layer between the bearing surfaces. So the actual metal of the
    bearings (if the lubrication is properly maintained) never actually
    make contact. The bearings "float apart" on a microscopically thin
    layer of oil.

    But oil, sans additives, is an insulator, so there is also no direct
    path for electrical conduction. So if the motion did build up static
    charges, they would eventually arc through the oil layer. That arcing
    would likely do no good for the oil in the path of the arc, so the
    "convert to varnish" makes overall sense.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to comp.os.linux.misc on Thu Nov 12 12:43:47 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-07 22:55, The Natural Philosopher wrote:
    On 07/11/2026 18:01, rbowman wrote:
    I can't pinpoint an exact date but there was a watershed where PCs went
    from painfully slow to acceptable
    For me, that was when I installed Linux :-)

    For me, nay. I switched to Linux, but speed was not the reason.
    Actually, my machine was slower. Linux wanted much more ram than I had,
    so it swapped. Specially browsing the web when javascript exploded, with
    a limited modem, was a pain.

    Circa yr 2000.


    I remember trying to fill a form that could take half an hour to render...
    --
    Cheers, Carlos.
    ESEfc-Efc+, EUEfc-Efc|;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to comp.os.linux.misc on Thu Nov 12 12:57:58 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-11 16:09, Robert Riches wrote:
    On 2026-11-11, Carlos E.R. <robin_listas@es.invalid> wrote:
    On 2026-11-08 05:23, Robert Riches wrote:
    On 2026-11-08, Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
    On 2026-11-07, Lars Poulsen <lars@beagle-ears.com> wrote:


    Within a few years either side of 1980, a professor in an EE
    class told a story from early in his career. He was hired by GE
    to work on _BIG_ (as in 8 feet to 16 feet diameter) motors and
    generators. He said GE would hire EEs and teach them mechanical
    stuff, because that worked better than hiring MEs and teaching
    them electrical stuff.

    He was tasked with solving a problem with premature bearing
    failure. When a failed machine was torn down, basically all the
    failed bearings were found to be coated with varnish. It turns
    out the moving parts within the bearing assembly were building up
    a static electric charge, which would eventually arc through the
    oil, creating a small spot of varnish. Eventually, the varnish
    would build up, and the bearing would fail.

    The solution was to add something to the oil to make it slightly
    conductive to electricity. Management told him he had just
    earned his salary for his entire career--and to go do it again.

    The professor's last name was Clegg. He taught at Brigham Young
    University.


    There is something I don't understand. The entire machine would be built
    of metal, except the insulation on the coils. Ball bearings are metal,
    the balls are made of metal. How could the static build up? Maybe the
    oil layer was insulation enough?

    That's what I had understood he was saying. Prior to the
    additive being put in the oil, the oil insulated the bearing
    components from each other well enough for a voltage difference
    to build up that would arc through the oil and convert the oil to
    varnish and eventually cause the bearing unit to fail--and the
    additive made enough of a difference to prolong the life of the
    bearings.


    Interesting. I always suspected the oil in ball bearings might act as an insulator, but I never knew one way or the other.
    --
    Cheers, Carlos.
    ESEfc-Efc+, EUEfc-Efc|;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to comp.os.linux.misc on Thu Nov 12 12:57:35 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-11 17:35, Rich wrote:
    Carlos E.R. <robin_listas@es.invalid> wrote:
    On 2026-11-08 05:23, Robert Riches wrote:
    On 2026-11-08, Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
    On 2026-11-07, Lars Poulsen <lars@beagle-ears.com> wrote:


    Within a few years either side of 1980, a professor in an EE class
    told a story from early in his career. He was hired by GE to work
    on _BIG_ (as in 8 feet to 16 feet diameter) motors and generators.
    He said GE would hire EEs and teach them mechanical stuff, because
    that worked better than hiring MEs and teaching them electrical
    stuff.

    He was tasked with solving a problem with premature bearing failure.
    When a failed machine was torn down, basically all the failed
    bearings were found to be coated with varnish. It turns out the
    moving parts within the bearing assembly were building up a static
    electric charge, which would eventually arc through the oil,
    creating a small spot of varnish. Eventually, the varnish would
    build up, and the bearing would fail.

    The solution was to add something to the oil to make it slightly
    conductive to electricity. Management told him he had just earned
    his salary for his entire career--and to go do it again.

    The professor's last name was Clegg. He taught at Brigham Young
    University.


    There is something I don't understand. The entire machine would be
    built of metal, except the insulation on the coils. Ball bearings
    are metal, the balls are made of metal. How could the static build
    up? Maybe the oil layer was insulation enough?

    Oil functions to lubricate moving parts by forming a very thin liquid
    layer between the bearing surfaces. So the actual metal of the
    bearings (if the lubrication is properly maintained) never actually
    make contact. The bearings "float apart" on a microscopically thin
    layer of oil.

    Makes sense. But I never knew this for sure.


    But oil, sans additives, is an insulator, so there is also no direct
    path for electrical conduction. So if the motion did build up static charges, they would eventually arc through the oil layer. That arcing
    would likely do no good for the oil in the path of the arc, so the
    "convert to varnish" makes overall sense.

    Yep...


    So this probably affects all machines, right? Cars included.
    --
    Cheers, Carlos.
    ESEfc-Efc+, EUEfc-Efc|;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to comp.os.linux.misc on Thu Nov 12 13:00:57 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-10 19:45, Charlie Gibbs wrote:
    On 2026-11-10, Robert Riches <spamtrap42@jacob21819.net> wrote:

    I was told by a (different) professor that he once witnessed a
    washing-machine-sized disk drive that got a fleck of dust under a
    head, which rather quickly cascaded to a shaving of most/all of
    the oxide. He said he and his coworkers used square-mouthed
    shovels to scoop the shredded oxide out of the cabinet.

    One head crash we had was bad enough that you could see bits
    of bare aluminum gleaming among the debris on the pack.
    (I never did see one that sprayed oxide around much.)

    One day we had a CE in to do preventive maintenance on our
    drives. While the CE was bent over with his head in the
    drive well, someone came in and asked me what he was doing.
    I explained, with a straight face, that he was adjusting the
    speed at which the disk pack spun, since if it spun too fast
    the bits would come flying off and have to be scraped off the
    inside of the well.


    X-D
    --
    Cheers, Carlos.
    ESEfc-Efc+, EUEfc-Efc|;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to comp.os.linux.misc on Thu Nov 12 13:04:18 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-11 06:03, c186282 wrote:
    On 11/10/26 13:06, Robert Riches wrote:
    On 2026-11-10, c186282 <c186282@nnada.net> wrote:

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

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

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

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

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

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

    I was told by a (different) professor that he once witnessed a
    washing-machine-sized disk drive that got a fleck of dust under a
    head, which rather quickly cascaded to a shaving of most/all of
    the oxide.-a He said he and his coworkers used square-mouthed
    shovels to scoop the shredded oxide out of the cabinet.

    -a Ummmmmm ... VERY VERY odd phrasing-a :-)

    -a As for the old "removable platter" HDDs, they
    -a were actually pretty good. Just DON't be tempted
    -a to pull 'em out while they are still spinning.
    -a SAW that once-a :-)

    Please tell, for those of us that were still in school ;-)


    I have a HD that if I remove from the HD dock station just after
    powering it off, I can feel resistance to change the orientation because
    of the inertia of the still spinning platters.
    --
    Cheers, Carlos.
    ESEfc-Efc+, EUEfc-Efc|;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.os.linux.misc on Thu Nov 12 15:32:29 2026
    From Newsgroup: comp.os.linux.misc

    On 12/11/2026 11:43, Carlos E.R. wrote:
    On 2026-11-07 22:55, The Natural Philosopher wrote:
    On 07/11/2026 18:01, rbowman wrote:
    I can't pinpoint an exact date but there was a watershed where PCs went
    from painfully slow to acceptable
    For me, that was when I installed Linux :-)

    For me, nay. I switched to Linux, but speed was not the reason.
    Actually, my machine was slower. Linux wanted much more ram than I had,
    so it swapped. Specially browsing the web when javascript exploded, with
    a limited modem, was a pain.

    Circa yr 2000.


    I remember trying to fill a form that could take half an hour to render...

    I didn't switch till yer average PC had more than enough for Linux.

    My transition was driven by application availability. Once Linux could
    do nearly all I wanted and an XP virtual machine the rest. that was it.

    I think I started with around 2GB of RAM - maybe 4...
    --
    There is something fascinating about science. One gets such wholesale
    returns of conjecture out of such a trifling investment of fact.

    Mark Twain

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Rich@rich@example.invalid to comp.os.linux.misc on Thu Nov 12 21:20:39 2026
    From Newsgroup: comp.os.linux.misc

    Carlos E.R. <robin_listas@es.invalid> wrote:
    On 2026-11-11 17:35, Rich wrote:
    Carlos E.R. <robin_listas@es.invalid> wrote:
    On 2026-11-08 05:23, Robert Riches wrote:
    On 2026-11-08, Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
    On 2026-11-07, Lars Poulsen <lars@beagle-ears.com> wrote:


    Within a few years either side of 1980, a professor in an EE class
    told a story from early in his career. He was hired by GE to work
    on _BIG_ (as in 8 feet to 16 feet diameter) motors and generators.
    He said GE would hire EEs and teach them mechanical stuff, because
    that worked better than hiring MEs and teaching them electrical
    stuff.

    He was tasked with solving a problem with premature bearing failure.
    When a failed machine was torn down, basically all the failed
    bearings were found to be coated with varnish. It turns out the
    moving parts within the bearing assembly were building up a static
    electric charge, which would eventually arc through the oil,
    creating a small spot of varnish. Eventually, the varnish would
    build up, and the bearing would fail.

    The solution was to add something to the oil to make it slightly
    conductive to electricity. Management told him he had just earned
    his salary for his entire career--and to go do it again.

    The professor's last name was Clegg. He taught at Brigham Young
    University.


    There is something I don't understand. The entire machine would be
    built of metal, except the insulation on the coils. Ball bearings
    are metal, the balls are made of metal. How could the static build
    up? Maybe the oil layer was insulation enough?

    Oil functions to lubricate moving parts by forming a very thin liquid
    layer between the bearing surfaces. So the actual metal of the
    bearings (if the lubrication is properly maintained) never actually
    make contact. The bearings "float apart" on a microscopically thin
    layer of oil.

    Makes sense. But I never knew this for sure.


    But oil, sans additives, is an insulator, so there is also no direct
    path for electrical conduction. So if the motion did build up static
    charges, they would eventually arc through the oil layer. That arcing
    would likely do no good for the oil in the path of the arc, so the
    "convert to varnish" makes overall sense.

    Yep...


    So this probably affects all machines, right? Cars included.

    It would seem to potentially impact all moving machinery where the
    motion could build up a static electric charge. But in the case of
    cars, engine oil contains a lot of additives so engine oil may also be slightly conductive (or very, I've never dipped ohmmeter probes into
    engine oil to test) such that the charge bleeds away before it reaches
    arc potential.

    In the electronics world, antistatic matts for work benches, and the anti-static wrist bands worn by workers to bleed off static, are
    grounded through (typically) 1M (mega - million) ohm resistors. So it
    does not take much conductivity to bleed away static charge buildups
    before they reach arc over potential. The 1M ohm resistances to ground
    are present so the workers don't get shocked via their anti-static
    wrist bands by being grounded and then brushing/touching a live,
    non-isolated, source of electric potential.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to comp.os.linux.misc on Thu Nov 12 22:51:00 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-12 22:20, Rich wrote:
    Carlos E.R. <robin_listas@es.invalid> wrote:
    On 2026-11-11 17:35, Rich wrote:
    Carlos E.R. <robin_listas@es.invalid> wrote:
    On 2026-11-08 05:23, Robert Riches wrote:
    On 2026-11-08, Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
    On 2026-11-07, Lars Poulsen <lars@beagle-ears.com> wrote:


    Within a few years either side of 1980, a professor in an EE class
    told a story from early in his career. He was hired by GE to work
    on _BIG_ (as in 8 feet to 16 feet diameter) motors and generators.
    He said GE would hire EEs and teach them mechanical stuff, because
    that worked better than hiring MEs and teaching them electrical
    stuff.

    He was tasked with solving a problem with premature bearing failure. >>>>> When a failed machine was torn down, basically all the failed
    bearings were found to be coated with varnish. It turns out the
    moving parts within the bearing assembly were building up a static
    electric charge, which would eventually arc through the oil,
    creating a small spot of varnish. Eventually, the varnish would
    build up, and the bearing would fail.

    The solution was to add something to the oil to make it slightly
    conductive to electricity. Management told him he had just earned
    his salary for his entire career--and to go do it again.

    The professor's last name was Clegg. He taught at Brigham Young
    University.


    There is something I don't understand. The entire machine would be
    built of metal, except the insulation on the coils. Ball bearings
    are metal, the balls are made of metal. How could the static build
    up? Maybe the oil layer was insulation enough?

    Oil functions to lubricate moving parts by forming a very thin liquid
    layer between the bearing surfaces. So the actual metal of the
    bearings (if the lubrication is properly maintained) never actually
    make contact. The bearings "float apart" on a microscopically thin
    layer of oil.

    Makes sense. But I never knew this for sure.


    But oil, sans additives, is an insulator, so there is also no direct
    path for electrical conduction. So if the motion did build up static
    charges, they would eventually arc through the oil layer. That arcing
    would likely do no good for the oil in the path of the arc, so the
    "convert to varnish" makes overall sense.

    Yep...


    So this probably affects all machines, right? Cars included.

    It would seem to potentially impact all moving machinery where the
    motion could build up a static electric charge. But in the case of
    cars, engine oil contains a lot of additives so engine oil may also be slightly conductive (or very, I've never dipped ohmmeter probes into
    engine oil to test) such that the charge bleeds away before it reaches
    arc potential.

    In the electronics world, antistatic matts for work benches, and the anti-static wrist bands worn by workers to bleed off static, are
    grounded through (typically) 1M (mega - million) ohm resistors. So it
    does not take much conductivity to bleed away static charge buildups
    before they reach arc over potential. The 1M ohm resistances to ground
    are present so the workers don't get shocked via their anti-static
    wrist bands by being grounded and then brushing/touching a live, non-isolated, source of electric potential.


    I remember technicians ignoring the wrist bands, still wrapped in the
    new plastic bags, hung from the racks, never used. They gave me one or
    two as gifts. When the rubber in those degraded and got sticky I bought
    a new one.
    --
    Cheers, Carlos.
    ESEfc-Efc+, EUEfc-Efc|;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to comp.os.linux.misc on Thu Nov 12 22:47:03 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-12 16:32, The Natural Philosopher wrote:
    On 12/11/2026 11:43, Carlos E.R. wrote:
    On 2026-11-07 22:55, The Natural Philosopher wrote:
    On 07/11/2026 18:01, rbowman wrote:
    I can't pinpoint an exact date but there was a watershed where PCs went >>>> from painfully slow to acceptable
    For me, that was when I installed Linux :-)

    For me, nay. I switched to Linux, but speed was not the reason.
    Actually, my machine was slower. Linux wanted much more ram than I
    had, so it swapped. Specially browsing the web when javascript
    exploded, with a limited modem, was a pain.

    Circa yr 2000.


    I remember trying to fill a form that could take half an hour to
    render...

    I didn't switch till yer average PC had more than enough for Linux.

    My transition was driven by application availability. Once Linux could
    do nearly all I wanted and an XP virtual machine the rest. that was it.

    I think I started with around 2GB of RAM - maybe 4...


    I started with 5 megs, but that was not enough for the new web pages
    with lots of javascript, which I needed. Not optional.

    I think I upgraded to 16 megs soon. maybe 32.

    Unsure...
    --
    Cheers, Carlos.
    ESEfc-Efc+, EUEfc-Efc|;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.misc on Thu Nov 12 17:45:03 2026
    From Newsgroup: comp.os.linux.misc

    On 11/12/26 07:04, Carlos E.R. wrote:
    On 2026-11-11 06:03, c186282 wrote:
    On 11/10/26 13:06, Robert Riches wrote:
    On 2026-11-10, c186282 <c186282@nnada.net> wrote:

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

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

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

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

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

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

    I was told by a (different) professor that he once witnessed a
    washing-machine-sized disk drive that got a fleck of dust under a
    head, which rather quickly cascaded to a shaving of most/all of
    the oxide.-a He said he and his coworkers used square-mouthed
    shovels to scoop the shredded oxide out of the cabinet.

    -a-a Ummmmmm ... VERY VERY odd phrasing-a :-)

    -a-a As for the old "removable platter" HDDs, they
    -a-a were actually pretty good. Just DON't be tempted
    -a-a to pull 'em out while they are still spinning.
    -a-a SAW that once-a :-)

    Please tell, for those of us that were still in school ;-)


    Just look up the term "gyroscopic precession" :-)

    Those big old drives were very well balanced, but
    nothing is *perfect* and that can get things going.


    I have a HD that if I remove from the HD dock station just after
    powering it off, I can feel resistance to change the orientation because
    of the inertia of the still spinning platters.

    Fer sure.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From rbowman@bowman@montana.com to comp.os.linux.misc on Fri Nov 13 03:04:44 2026
    From Newsgroup: comp.os.linux.misc

    On Thu, 12 Nov 2026 22:47:03 +0100, Carlos E.R. wrote:

    I started with 5 megs, but that was not enough for the new web pages
    with lots of javascript, which I needed. Not optional.

    I think I upgraded to 16 megs soon. maybe 32.

    I was curious about an old Compaq desktop in the shed. I never got around
    to seeing if it would boot iirc it ran Windows 95 in its day and I believe
    it has 5 MB or some other minuscule amount of RAM. I may have put Mandrake
    on it back around 2000. Even run Puppy Linux calls for 512 MB.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to comp.os.linux.misc on Fri Nov 13 11:38:47 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-12 23:45, c186282 wrote:
    On 11/12/26 07:04, Carlos E.R. wrote:
    On 2026-11-11 06:03, c186282 wrote:
    On 11/10/26 13:06, Robert Riches wrote:
    On 2026-11-10, c186282 <c186282@nnada.net> wrote:

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

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

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

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

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

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

    I was told by a (different) professor that he once witnessed a
    washing-machine-sized disk drive that got a fleck of dust under a
    head, which rather quickly cascaded to a shaving of most/all of
    the oxide.-a He said he and his coworkers used square-mouthed
    shovels to scoop the shredded oxide out of the cabinet.

    -a-a Ummmmmm ... VERY VERY odd phrasing-a :-)

    -a-a As for the old "removable platter" HDDs, they
    -a-a were actually pretty good. Just DON't be tempted
    -a-a to pull 'em out while they are still spinning.
    -a-a SAW that once-a :-)

    Please tell, for those of us that were still in school ;-)


    -a Just look up the term "gyroscopic precession" :-)

    -a Those big old drives were very well balanced, but
    -a nothing is *perfect* and that can get things going.

    Yeah, well, but I wanted the anecdotes, the colour. A technician running
    after the disks rolling down the corridor, things like that ;-D


    I have a HD that if I remove from the HD dock station just after
    powering it off, I can feel resistance to change the orientation
    because of the inertia of the still spinning platters.

    -a Fer sure.

    Yes, but only one disk does that to me. The rest are not so heavy to notice.
    --
    Cheers, Carlos.
    ESEfc-Efc+, EUEfc-Efc|;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Robert Riches@spamtrap42@jacob21819.net to comp.os.linux.misc on Fri Nov 13 17:39:17 2026
    From Newsgroup: comp.os.linux.misc

    On 2026-11-12, Rich <rich@example.invalid> wrote:
    ...

    In the electronics world, antistatic matts for work benches, and the anti-static wrist bands worn by workers to bleed off static, are
    grounded through (typically) 1M (mega - million) ohm resistors. So it
    does not take much conductivity to bleed away static charge buildups
    before they reach arc over potential. The 1M ohm resistances to ground
    are present so the workers don't get shocked via their anti-static
    wrist bands by being grounded and then brushing/touching a live, non-isolated, source of electric potential.

    The 1M resistors are a good idea for safety, but even that level
    of resistance doesn't completely stop effects on biological
    units. In high school, I had a Realtone stereo receiver (with
    the schematic on the back page of the owner's manual) with a 470k
    (half of 1M) resistor from the single-ended antenna input to what
    the schematic called chassis ground. The apparent intent was to
    bleed off any DC charges that might end up on the antenna wiring.
    However, this was in the days before (the annoying) polarized
    plugs in the US, so depending on how the power plug was inserted
    into an outlet, chassis ground could be either within a couple of
    volts of earth ground or ~120VAC away from earth ground.

    I was experimenting with connecting a long-wire antenna
    originally used with a (1N34A) crystal radio to the stereo
    receiver. Whenever I would be touching the antenna wire and my
    shoulder would touch the steel casing around the basement window,
    I would feel a rather sharp discomfort in the shoulder, similar
    to being pricked by a pin or needle. After a bit of sleuthing, I
    deduced that the discomfort was coming from the stereo receiver
    feeding 60Hz 120VAC through that resistor to the antenna wire.
    To avenge the discomfort I had experienced, that resistor met an
    untimely demise between the blades of a pair of wire cutters.
    --
    Robert Riches
    spamtrap42@jacob21819.net
    (Yes, that is one of my email addresses.)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Rich@rich@example.invalid to comp.os.linux.misc on Sat Nov 14 04:09:08 2026
    From Newsgroup: comp.os.linux.misc

    Robert Riches <spamtrap42@jacob21819.net> wrote:
    On 2026-11-12, Rich <rich@example.invalid> wrote:
    ...

    In the electronics world, antistatic matts for work benches, and the
    anti-static wrist bands worn by workers to bleed off static, are
    grounded through (typically) 1M (mega - million) ohm resistors. So it
    does not take much conductivity to bleed away static charge buildups
    before they reach arc over potential. The 1M ohm resistances to ground
    are present so the workers don't get shocked via their anti-static
    wrist bands by being grounded and then brushing/touching a live,
    non-isolated, source of electric potential.

    The 1M resistors are a good idea for safety, but even that level
    of resistance doesn't completely stop effects on biological
    units. In high school, I had a Realtone stereo receiver (with
    the schematic on the back page of the owner's manual) with a 470k
    (half of 1M) resistor from the single-ended antenna input to what
    the schematic called chassis ground. The apparent intent was to
    bleed off any DC charges that might end up on the antenna wiring.
    However, this was in the days before (the annoying) polarized
    plugs in the US, so depending on how the power plug was inserted
    into an outlet, chassis ground could be either within a couple of
    volts of earth ground or ~120VAC away from earth ground.

    I was experimenting with connecting a long-wire antenna
    originally used with a (1N34A) crystal radio to the stereo
    receiver. Whenever I would be touching the antenna wire and my
    shoulder would touch the steel casing around the basement window,
    I would feel a rather sharp discomfort in the shoulder, similar
    to being pricked by a pin or needle. After a bit of sleuthing, I
    deduced that the discomfort was coming from the stereo receiver
    feeding 60Hz 120VAC through that resistor to the antenna wire.
    To avenge the discomfort I had experienced, that resistor met an
    untimely demise between the blades of a pair of wire cutters.

    Indeed. The 1M resistors are chosen for safety (your heart is less
    likely to be stopped) not for discomfort purposes (you still may feel tingles/etc.). Discomfort teaches you not to do that again (or as in
    your case to rid yourself of the source). Your heart stopping ends
    your personal learning for good unless someone else is nearby and 911
    can respond rapidly enough.

    --- Synchronet 3.22a-Linux NewsLink 1.2