Language Selection

English French German Italian Portuguese Spanish

About Me

I saw somewhere that it was advisable to include an "About Me" page for sites and blogs in case someone wants to quote you or address you formally and it adds credibility.

So for those that don't yet know, I'm Susan Linton. I live in the great state of Tennessee in the southern US of A. I have a Bachelor of Science degree from Austin Peay State U, and a few credits towards my Masters. I've worked as a middle school teacher, substitute teacher, auto mechanic, factory technician, cashier, auto body sander, auto parts department manager, call center agent and waitress (when I was 13 years old) over the course of my life. I currently run and write for this website and write for other sites and publications.

I've been using computers since 1992 when I purchased my first machine with DOS on it. I later bought a machine with Windows 98 and in the fall of 2000 I switched permanently to Linux. First Mandrake, then Gentoo fulltime, but I've tested about every one out there at some point. I don't claim to be an expert, but I love Linux and open source software. I enjoy installing distros and sharing with others what I see.

I can be contacted at this email address.

More in Tux Machines

Black Hat 2014: Open Source Could Solve Medical Device Security

On the topic of source code liability, Greer suggests that eventually software developers, including medical device development companies, will be responsible for the trouble their software causes (or fails to prevent). I think it’s fair to say that it is impossible to guarantee a totally secure system. You cannot prove a negative statement after all. Given enough time, most systems can be breached. So where does this potential liability end? What if my company has sloppy coding standards, no code reviews, or I use a third-party software library that has a vulnerability? Should hacking be considered foreseeable misuse? Read more

Does government finally grok open source?

Yes, the government -- one U.S. federal government employee told me that government IT tends to be "stove-piped," with people "even working within the same building" not having much of a clue what their peers are doing, which is not exactly the open source way. That's changing. One way to see this shift is in government policies. For the U.S. federal government, there is now a "default to open," a dramatic reversal on long-standing practices of spending heavily with a core of proprietary technology vendors. Read more

The OS LinuX Desktop

Reader Oliver wanted to make his Linux Mint desktop look as much like a Mac as possible so others would find it easy to use. Given some of our previous Linux featured desktops, we know it wasn't tough, but the end-result still looks great. Here's how it's all set up. Read more

A Linux Desktop Designed for You

Desktop environments for Linux are not released ready-made. Behind each is a set of assumptions about what a desktop should be, and how users should interact with them. Increasingly, too, each environment has a history -- some of which are many years old. As you shop around for a desktop, these assumptions are worth taking note of. Often, they can reveal tendencies that you might not discover without several days of probing and working with the desktop. Read more