Language Selection

English French German Italian Portuguese Spanish

My Linux Story

Filed under

My Introduction Computers

I got my first computer around 1992, after the personal computering hobby had been around quite a while. I know I felt so far behind. I remember feeling so lost and thinking I'd never know what I was doing. But it didn't really matter because I never dreamed of doing anything actually computer related. The truth was, I just wanted a nice word processor from which I could print nice papers. I was in college and type written papers were required and typing for me meant spending more time correcting errors that actual research and writing. A computer seemed like the perfect answer.

I bought a second hand Tandy 2000, by Radio Shack. It had everything and only cost $500. It had some version of DOS on it and the computer guy put on a few programs for me. Well, I used it without ever thinking of checking for a modem until I quit college in my Junior year of nursing school. That's another story, but two words will suffice - sponge bath! Well, and two more - dying patients. I would never be happy nursing.

But I returned to college in Fall 1998 and realized my old Tandy was a dinosaur. The papers the other students turned in weren't in Dot Matrix. They had fancy fonts and pictures! I had to get a new computer.

I purchased my second computer at the local army base PX for $500, a Pionex I believe. It wasn't top of line, but about second. It came with Windows 98, and excellent tech support. It wasn't long before their friendly support staff was walking me through modem replacement, driver installation, and ultimately reformats/reinstalls.

I wasn't into a year using it before I became disenchanted and paranoid. Very paranoid. I feel so silly now, but I was so worried that some "hacker" would break into my machine in the few minutes I spent on the dial-up connection that I had bogged the machine down with a firewall, antivirus, and spyware hunter. mean anything to anyone? I had hacked this file and that file trying to keep my private information private and cover tracks and reformating about every 3 months. That's what it was averaging. About every 3 months. Then someone mentioned Linux.

Enter Linux

I spent much of 2000 trying to convert to Linux. I tried SUSE, Red Hat, and Mandrake among a few others. I always tucked tail and went back to Windows. ...until Mandrake 7.2 hit Wal-Mart shelves in the Fall of 2000.

All of a sudden I could get a decent screen resolution and KDE 1.99 (a 2.0 beta that it shipped with) was actually usable. ...or understandable. There was a list of applications in the menu instead of a bunch of directories (anyone remember the old 1.x menus?) Well, I was inspired enough to try and get my modem and sound working. See, everything else was working just fine either out-of-the-box or using the Mandrake Control Center. I never went back to Windows again.

Well, it took a week of booting to Windows to look something up on the internet and booting back to Mandrake to try something before my modem finally dialed, but I've never felt so excited and proud in all my life.

My ISA sound card took another week, but it was much easier now. I could search from Mandrake and by then someone had said the fateful word "Google" to me. It took a bit more voodoo to get ISA cards to work, but within another week I was listening to system sounds and music files.

Well, with the release of the 2.4 kernel that same fall I was able to use NVIDIA proprietary drivers and I was well on my path of discovery. I spent a few years learning Linux and helping others on the Mandrake mailing lists and Usenet users group.

Broadband had hit during 2001 and I had my firewall making me invisible, but mainly I felt this big sigh of relief. My paranoia was gone as was the weight of the world. I loved Linux and the commandline made sense. I never was able to form any patterns or retain all those mouse clicking routines used in Windows, but I could understand what was going on in that terminal. I was home.

I switched to Gentoo in 2003 and started this website in 2005. The rest is probably history.

It's All in the Timing

I was lucky to have switched to Linux when I did. I tried lots of other distros just for fun. I began experimenting with Howtos I'd run into. Back then howtos weren't "apt-get this, tick this box, and click OK." Back then they were 'get the source here, and the patch here and this one here, and open this file and replace this function with that one, then do this and that to this config file and then recompile this other program using this patch and edit its config file, then patch the kernel...' No mention of dependencies usually, you discovered them when you started to compile. Me and Texstar used to write back forth - "Hey hey! I got this to work! Here's a screenshot." Those were the days. It's all too easy now.

But that was considerably easier than it had been in the '90s. This is why I have such respect for the really old guys that have been using Linux since "real men write their own drivers" and why Linus is my hero. This is why I shake my head at those who ask, "Is Linux ready for Prime Time?"

Hell yeah, it's ready - and has been for quite a while.

Comment viewing options

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

What's your story?

Join Don, Lisa, and me and share your Linux story? When, why, and how did you switch to Linux? Have you switch recently, have you been around since the 90's, or somewhere in-between? Share your story.

You can comment here or use your own TuxBlog, free with your account here at

Don't be shy!

Year 2000

That's when I got exposed to it too... and to better options, better choice.

A very good story!

I too did something with my PC when i got pissed of windows... I got to work with Ubuntu 8.04. the rest is little similar to your story... i got so excited by working with Ubuntu because u know what actually is happening with a greater transparency than in windows. U can see my love story with my pc after installing Linux here


More in Tux Machines

Cinelerra GG Infinity – A Free Video Editing Software for Linux

We have covered a variety of video editing software that range from simple video editors to professional-class free alternatives.g. Shotcut and OpenShot. Today, we are happy to introduce to you another video editor capable of meeting your personal needs. Cinelerra GG Infinity is a robust free and open-source video editing software designed for rendering, motion tracking, compositing, and video editing on Linux computers. With it, you can edit videos into movie-like projects using beautiful transitions, texts, and effects with proper audio quality all from a modern 8k video editor. Read more

Ubuntu 20.04 Features the Return of a Familiar Face…

Having been recently crowned the greatest Ubuntu wallpaper of all time on Twitter the heralded Hardy Heron makes its (overdue, imo) return to Ubuntu desktop proper. The image last shipped on an Ubuntu .iso way back in 2008 — has it been that long already?! To ensure that the heron is fit and fine its encore in the Focal Fossa, Ubuntu desktop lead Martin Wimpress remastered the image from the original .svg source files. Read more

New Release: Tor Browser 9.0.9

or Browser 9.0.9 is now available from the Tor Browser download page and also from our distribution directory.

This release is updating Firefox to 68.7.0esr, NoScript to 11.0.23 and OpenSSL to 1.1.1f.

Read more

Bringing Leap and SUSE Linux Enterprise closer together - a proposal

Hi everyone,

today I have some exciting news and a proposal to relay: SUSE wants to
go another step in openness towards the openSUSE community and suggests
to bring the relationship of openSUSE Leap and SUSE Linux Enterprise to 
a new level.

Internally this idea is called "Closing the Leap Gap" and proposes to
strengthen and bring more closely together:

 * developer communities, by focusing on openSUSE Leap as a 
   development platform for communities and industry partners;
 * user communities, by leveraging the benefits of both a stable
   Enterprise code base and the speed of community contributions;
 * the code bases of openSUSE Leap and SUSE Linux Enterprise (SLE), 
   by not only sharing sources, but also offering the SUSE Linux 
   Enterprise binaries for inclusion in openSUSE Leap.

The proposal includes a three step approach:

 1. Merge the code bases for the intersection of openSUSE Leap 15.2 
    and SUSE Linux Enterprise 15 SP2 as much as possible without loss 
    of functionality or stability. (SUSE has started a cleanup process 
    on the SUSE Linux Enterprise side already.)
 2. In parallel to classic openSUSE Leap 15.2 create a flavor leveraging
    SLE binaries, leading to an intermediate release in the October 2020
    time frame.
 3. Build openSUSE Leap 15.3 with SLE binaries included by default
    (assuming community agreement).

As you can imagine, a number of people have been involved with this
so far, and I'd like to pull some of them in front of the curtain in 
a little interview.

Q: Thomas, all of engineering at SUSE reports to you, and I know 
   openSUSE is something you care about quite a bit.  What is SUSE  
   putting on the table here?

Thomas Di Giacomo: Let me step back, and give you a perspective as I see
  it. SUSE for 27+ years has been a part of global open source ecosystem
  that includes a vast number of developers, end users, communities,
  and organizations of all sizes working together and benefiting from
  the collective work. Most of our engineers are involved as well with
  some open source communities that they feel passionate about.

  Open source communities are an integral part of who we are and the
  ecosystem we serve. Naturally, we feel responsible to support the
  communities and the work done by them. openSUSE is no different and
  is actually even more special and very dear to SUSE. So, it should
  come as no surprise that we are fully committed towards the openSUSE
  project(s) and its community. It makes us all feel proud to see Leap
  and Tumbleweed grow and evolve, together with SUSE Linux Enterprise.
  This effort of our engineers working together with others in the
  openSUSE community will benefit everyone involved for many years 
  to come.

Q: And why are you doing this?

Thomas: We want open source to succeed for everyone – developers,
  contributors to end users and everyone in between. The benefits of
  open source are tremendous when the ecosystem grows as a result of
  the positive virtuous cycle of – contributing more, supporting the
  contributions, benefiting from contributions, which inspires more
  people contributing, and it goes on to grow as an upward virtuous spiral.

  We feel fortunate to be in the position of seeing the openSUSE community
  grow in tandem with the success of SUSE Linux Enterprise, and both
  feeding off each other to grow even more. This idea definitely goes in
  that direction. Now, let me defer to Matthias who came up with this idea.

Q: Okay, so, Matthias, first of all: what is your role at SUSE?

Matthias Eckermann: I am leading the Product Management team for 
  Linux platforms, covering SUSE Linux Enterprise, Edge, and Security.

Q: And what made you propose this?

Matthias: My team and I realized that the engagement of our SLE 
  business with the openSUSE community does not fully fit our view 
  on openness, and that mutual benefits are not leveraged sufficiently.

  We discussed what it would take to bridge the gap and bring the
  relationship to the next level. Beyond a common ground on the
  technical side, the code streams, this requires learning from each
  other; for example, we need to re-establish an open feature process
  between community, SUSE, and our industry partners.

  Thus we developed "Closing the Leap Gap", and - to test whether it
  might have a chance to fly - we outlined the initial idea with the
  openSUSE Board before going for approvals by SUSE management.

Q: You mention the board, so let me ask.  What is your take?
   What opportunities, benefits do you see?  What risks?

Dr. Axel Braun: With this change, we can make better use of our
  resources, as two code bases converge - so one build target less to
  consider. Everyone who packages for Leap and for Package Hub will
  immediately benefit from this.

Marina Latini: It's really exciting to see how SUSE is trying to increase
  its support for Leap, reducing the existing differences between our
  openSUSE Leap and SLE. I can see this proposal as a way to be more
  inclusive, giving to the community the opportunity to contribute in 
  an easier way to Leap and giving the chance to bring the openSUSE 
  spirit also in an Enterprise product like SLE.

  On the other hand, every new move is a change and we need to be sure
  that the changes won't limit our community freedom to submit packages
  to Leap or won't slow down Leap for following the internal SUSE
  development model.

Q: Matthias, that sounds like some extra effort required.
   How is SUSE contributing, what is SUSE committing to?

Matthias: Indeed, there is quite some one-time effort needed to get
  (back) to the common ground; this is covered by SUSE engineering teams;
  two groups are heavily involved: The Open Build Service experts are
  designing a workflow for a smooth integration of the binaries, and
  for reducing the long term maintenance efforts for our community
  contributors. SUSE release managers and packagers are working hard
  to synchronize the code bases without losing functionality or quality.
  Hundreds of change requests have been filed already, and to get this
  done properly, we are delaying the release of SUSE Linux Enterprise
  15 SP2 to July.

  And we are willing to invest more, to drive the idea to success
  quickly: we would take the burden, to create an intermediate openSUSE
  Leap release in October 2020 which then would incorporate SUSE Linux
  Enterprise binaries into Leap the first time.

  Probably, Adrian can comment on the Build Service aspects, and Lubos
  what it means to developers within SUSE and to the community release

Q: So, Lubos, as release manager for Leap, what have you been doing
   so far, and what is the impact you see?

Lubos Kocman: I spent most of the time on collecting data regarding SLE
  and Leap differences and having follow-up discussions and transforming
  feedback into action items. Max and the rest of the openSUSE release
  engineering team meanwhile did an excellent job of keeping Leap release
  activities going forward.

  The idea of re-using should generally lower the effort on the Leap side.
  However, it comes with the price of increased complexity to bring all
  pieces together. A new process will allow external contributors to file
  feature or update requests directly to SLE. This will already help a lot.

Q: Is this an outcome bound effort, or time bound?  I know the SLE
   release schedule is a bit like a 300m tanker.

Lubos: It's both. I see this as a balance between what can we deliver,
  how, and to what date. It took quite some effort to create a plan
  acceptable by all involved teams. Splitting the work across the
  upcoming two releases seemed to be accepted well at least by 
  involved parties so far.

Q: So, that is SLE 15 SP2.  How about Leap 15.2?

Lubos: openSUSE Leap 15.2 will have to slip by about 8 weeks to incorporate 
  all changes from the SLE and align with its new schedule. I believe that 
  the release will find a great use for extra time since we're still 
  finishing the refresh of packages from Factory. The prototype will 
  be meanwhile available in parallel to the openSUSE Leap 15.2.

Q: How is that research proceeding, Adrian?

Adrian Schröter: We have an idea about the setup in
  I anticipate to have a first prototype of the build setup in next three
  weeks. And more important is how to develop the workflows to allow a
  more collaborative joint effort between SLE and openSUSE development.

  However, we must keep in mind that this is really an entire new way to
  develop a distribution. On one hand it makes a lot of sense to integrate
  for example the SUSE Backports (aka Package Hub) people directly in our
  development process. This will make our distribution development stronger.

  On the other hand, we also must find ways how to solve new problems.
  For example how to keep our builds for architectures not covered by
  SLES like Arm 32bit and RISC-V. Also the turn around times of submissions
  and build results will be a challenge in the initial setup. And last but
  not least, the installed systems and users may need to deal with more

  But we have one year to work on these problems in parallel to our
  stable distribution. And we are indeed looking forward to make 
  openSUSE and SLE development more beneficial than ever.

Gerald: Thanks everyone for your input.  I'll be sharing all this with
  openSUSE mailing lists, and am sure there will be further questions,
  offers to help, and other input, so please chime in there. has an FAQ with
more details.

Lubos is going to send a proposal with more details on the implementation
side to opensuse-factory@.

I suggest we focus technical discussions of this offer and proposals
there (opensuse-factory@) and general discussions on opensuse-project@.

So, what do you think?

Read more