Are You a Longtime LJ Subscriber?

The 200th issue of Linux Journal is rapidly approaching, and we'd like to take this opportunity for everyone to learn a bit more about some of the people who've helped make LJ possible for so many years. If you're a longtime subscriber, please fill out the form on this page by September 10, 2010.

We will randomly select ten subscribers who participate, and send the
"winners" a free T-shirt.

______________________

Jill Franklin, Executive Editor, Linux Journal

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Still have a couple of 1994 issues

cjcox's picture

I've gotten rid of most of the physical mags... but do have the archive CDs... but I did have two from 1994. Different times...

Longtime LJ Subscriber

w6bi's picture

I got into Linux in 1995 or 1996, with a 16-floppy distro (I skipped on diskettes 17-32; the app I was using didn't need X). It ran on a 40 MHz 386!

Why did I start using Linux? It's an interesting story. In the 80s, the FCC let amateur radio operators use digital protocols more advanced than the archaic Baudot they had been restricted to for decades. By the mid-80s, ham radio operators were running a variant of X.25 over the air called AX.25. It in turned transported TCP/IP.

Brian Lantz, KO4KS, authored a combination BBS and IP routing program he dubbed TNOS. This was in the early days of the Internet, which while primitive compared to today's 'net, allowed efficient distribution of the code and he soon had a dedicated group of users of his software.

He added features and bug fixes to it steadily, and soon it grew to the point to where his C compiler (Turbo C, I believe) could no longer compile it. [A side note - he sent it to Borland for them to look at, and he was told it was the most complicated C program they'd ever seen] As a result, he switched to Linux, compiling TNOS with GCC, and a large percentage of his users followed him (from DOS to Linux; talk about culture shock...). I was one of those followers, with my trusty 386/40 with 8 Megs of RAM.

Since then I've gone from Slackware to Red Hat Linux,then to Fedora (with occasional dalliances with Kubuntu and OpenSUSE). There's been no other operating systems but Linux in my house since about 2002. My wife's workstation was the last to convert - she runs Fedora 13, as I do. My server runs CentOS 5.5.

I participate in my local LUG (http://www.sclug.org) and am involved in the Southern California Linux Expo. Since I don't code, it's my way of giving back to the FOSS community (thanks for the great software!!)

I believe I started my subscription to Linux Journal around 1999, and it's one of two magazines I look forward to getting in the mail every month (the other? Scientific American), and read it cover to cover immediately after receiving it. I think the assortment of articles from beginning to advanced is excellent, as I get something from each and every one, and from each and every column. Keep up the great work!

Orv

Subscriber since 1996

Robert Johnson's picture

Love the magazine.

Always fresh!

Jim Ballard's picture

Great magazine. Keep it comin'!

Webcast
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers

Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.

Learn More

Sponsored by AMD

White Paper
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions