Of the ones I knew, none of them were linux users at that time. They may have migrated to it years later, after deciding that Windows wasn't 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?


* SLMR 2.1a * Love is a grave mental disease. -Plato
---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Linux, networking, etc.
By: Dumas Walker to POINDEXTER FORTRAN on Sun Jul 20 2025 10:27:28

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).

This takes me back. I first started using Unix in about 1989 when I stared out with SCO Unix. At my first couple of jobs I encountered other *nix such as Xenix, Dynix, AIX, and a few others. I first discovered Linux when I picked up a .net magazine (It was a British mag for internet stuff) and it included a copy of Slackware 1.2.13. I accidentally blew away my WfW3.11 setup since I had no idea about duel bootings and the like at the time and Remember I was stuch with a "LI" something or other at the top. Another ago and LILO eventually ran and booted up, slowly, on my 486dx66 with 4mb ram. I eventually updated the system to a 486DX4-120 which I sent to the US before my immigration to be used for an IRC server in Toledo.

Anyway, I friend got me to try NetBSD and I used that for a while but I always had problems updating and getting library problems. I picked up a copy of Mandrake (to be Mandriva) at a local Half Price Books. I used that for a long time, but got tired of packages being out of date. I swithed to CentOS and got along well until they decided to go continuous release. I fiddled around with various releases until setting on Ubuntu which I was already using for my BBS machine by now anyway, eventually converting everything else over.

I did play with Yellowdog on a Mac G4 at work for a while, and also had the misfortune to come across zOS. I was sent on a 4 day course because the company might want to use it. They didn't. They were Nortel and went belly up.

Interesting thing about Linux was that it had SCO Compatability. It would run MicroFocus Cobol and would run our product. I have no idea if it can still do that.

A nice walk down memory lane. I think this is pretty much documented elsewhere, maybe I should just create a webpage and point to it eveytime this sort of thing comes up.

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com

no idea about duel bootings and the like at the time and Remember I was stuch with a "LI" something or other at the top. Another ago and LILO eventually ran
and booted up, slowly, on my 486dx66 with 4mb ram. I eventually updated the system to a 486DX4-120 which I sent to the US before my immigration to be used
for an IRC server in Toledo.

LOL, I had forgot about getting stuck with the "LI" on the screen and the
boot hanging. That was a frustration I had forgotten. ;)

Anyway, I friend got me to try NetBSD and I used that for a while but I always
had problems updating and getting library problems. I picked up a copy of Mandrake (to be Mandriva) at a local Half Price Books.

I tried Mandrake c2000. The install process went like a breeze, and it was able to identify my video card -- the test graphic looked perfect. Unfortunately, whatever the install process ID'ed it as was not passed onto
the installed OS. I eventually had to give that up and tried Correl (sp?) linux, which worked well but was no longer being updated or maintained.

Someone told me about libranet linux, another debian derivative. It worked great. Unfortunately, the maintainer passed and it also became
unmaintained. I migrated from that to debian and have stuck with it since.

I did play with Yellowdog on a Mac G4 at work for a while, and also had the misfortune to come across zOS. I was sent on a 4 day course because the compan
might want to use it. They didn't. They were Nortel and went belly up.

zOS is the IBM mainframe OS system. I was an IBM mainframe user, and COBOL programmer, for over 25 years but spent little time interfacing with the OS itself, so I cannot say much about it.

Before that, I spent a couple of years sometimes using an AS/400. I never
knew what OS those ran. Time to do some curiousity research.

Interesting thing about Linux was that it had SCO Compatability. It would run MicroFocus Cobol and would run our product. I have no idea if it can still do that.

IIRC, wasn't that what caused SCO to eventually try to sue linux, possibly
in an effort to take it over?

A nice walk down memory lane. I think this is pretty much documented elsewhere
maybe I should just create a webpage and point to it eveytime this sort of thing comes up.

That'd be handy. With my luck, I'd go to the trouble of creating the page
only to never have the topic come up again. ;)


* SLMR 2.1a * "You've stolen my soul!" - Granpa Simpson
---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Linux, networking, etc.
By: Dumas Walker to NELGIN on Mon Jul 21 2025 10:14:23

LOL, I had forgot about getting stuck with the "LI" on the screen and the boot hanging. That was a frustration I had forgotten. ;)

Yeah, alwys a good one. Never an indiaction what the problem was but it's obviously a missing driver from the boot kernel...but which...

I tried Mandrake c2000. The install process went like a breeze, and it was able to identify my video card -- the test graphic looked perfect. Unfortunately, whatever the install process ID'ed it as was not passed onto the installed OS. I eventually had to give that up and tried Correl (sp?) linux, which worked well but was no longer being updated or maintained.

I liked urpmi on Makdrake. I hate yum/dnf or apt takes so long because they want to check stuff each time. urpmi just got on with it.

Interesting thing about Linux was that it had SCO Compatability. It would run MicroFocus Cobol and would run our product. I have no idea if it can still do that.

IIRC, wasn't that what caused SCO to eventually try to sue linux, possibly in an effort to take it over?

It might have been. It's been a long time since that happened. We got the works at work. The OS, computer, tcp/ip, They all came with printed manuals. There must have been about 4 foot worth of printed material.

A nice walk down memory lane. I think this is pretty much documented elsewhere
maybe I should just create a webpage and point to it eveytime this sort of thing comes up.

That'd be handy. With my luck, I'd go to the trouble of creating the page only to never have the topic come up again. ;)

Nah, this comes up on a regular basis. There's always stuff I miss like HPUX, which is odd because I spend a while contracting at HP.

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com