TZUTC: -0500
MSGID: 26668.memoryln@1:2320/105 2ce2a90c
REPLY:
PID: Synchronet 3.21a-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0
TID: SBBSecho 3.28-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0
BBSID: CAPCITY2
CHRS: ASCII 1
FORMAT: flowed
This is from a discussion I am having with someone on another network that,
after reading it a few times, I decided might also be appropriate here.
File under "work and tech" memories, some fuzzier than others. ;)
> DW> Of the ones I knew, none of them were linux users at that time. They
> DW> may have migrated to it years later, after deciding that Windows wasn't
> DW> to their liking.
> The timeline is off, I remember in 1994 working with Linux -- at work,
My timeline is probably off from yours because you were encountering it
professionally while my encounters were all not at work, so everyone I knew
who knew of linux was a hobbiest. The places I was working 1994-98 were either
still running something on top of DOS and Netware (like Wordperfect Office, a
Baby-36 emulator, or a Kermit terminal to access a "bigger machine"), were
running OS/2 (one client), and a few were either running Windows 3.1 or
WfWG 3.11 (the latter for networking).
Somewhere during 1998-2000, the place I was at upgraded from WfWG to NT 4.0.
My first run in with linux professionally didn't happen until 2006-09 or
thereabouts, when I was working with someone to try to get the z/OS side
and the linux side of our mainframe to work together. Something to do with
z/OS not supporting a certain flavor of encryption at the time (for ftp
transfers) while linux could... or so we thought. While we were working
on it, "the networking people" came up with the policy that all file
transfers had to go through a middle man server based platform because that
was "more secure."
That platform later made the news for getting hacked and leaking all sorts
of information but, luckily, we hosted our own server and didn't use theirs.
> I had a tech working for me who'd gotten a copy of SLS linux and we
> installed it on a leftover 486. Hardware support was extremely limited,
> it took a call to some people at Intel to get support for our
> EtherExpress 16 cards (To this day, we're not sure if we were allowed
> to have the code and my friend insists that he was responsible for
> Intel NIC support in Linux) and it all ended up being a wonderful
> project for a team of tech support people - but nothing that Joe User
> could manage.
Cool story. Of the top of my head, I cannot remember what type of network
card it was that I figured out worked with little/no pain (IIRC, they maybe
were 3COM products?) but, once I figured that out I stocked up on them. ;)
IIRC, whatever it was also worked pretty well with OS/2.
> A couple of years later, setting up SLIP on a Linux box was a pain,
> and running FVWM and a primitive browser was challenging.
I remember that always being at least somewhat of a pain until I switched over
to a cable modem. Can't remember when that was now, maybe 2009? I cannot
remember for sure when linux flavored browers seemed to catch up, maybe when
Chrome became a thing?
Mike
* SLMR 2.1a * "Mmmmmmmm.....doughnuts."
--- SBBSecho 3.28-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
SEEN-BY: 50/22 103/705 104/119 105/81 106/201 114/10 120/302 616 124/5016
SEEN-BY: 128/187 129/14 305 153/757 7715 154/10 30 50 110 700 203/0
SEEN-BY: 218/700 220/20 30 90 221/0 6 226/18 30 44 50 227/114 229/110
SEEN-BY: 229/206 300 317 400 426 428 664 700 705 240/1120 5832 263/1
SEEN-BY: 266/512 280/464 5003 5006 291/111 292/854 301/1 310/31 320/219
SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124
SEEN-BY: 467/888 633/280 712/848 770/1 902/26 2320/0 105 304 3634/12
SEEN-BY: 5020/400 8912 5054/30 5075/35
PATH: 2320/105 154/10 280/464 460/58 229/426
|
