New Slackware Linux Documentation Project

A recent posting at Jeremy’s LinuxQuestions.org really lit a fire under some hardcore Slackware users.

There is so much Slackware information spread out over the Net in the form of private blogs, forums, websites, etc. All that wonderful information is so spread out, though. A new initiative has been launched recently to gather all Slackware information together in one location. A wiki-based format is being used with Arch Linux’s outstanding wiki as inspiration.

Eric Hameleers (Alien Bob) and many others from LinuxQuestions.org have spearheaded this new initiative. We even seem to have the blessing of Slackware’s BDFL – Pat V. This is a community thing. All interested people are invited to come join in making this project a successful thing. The oldest living GNU/Linux distribution deserves this.

C’mon over and lend a hand. All assistance is appreciated. Community is what makes GNU/LInux and Open Source the awesome thing that it is.

Regards,

~Eric

Links:

the LQ.org conversation

the Slackware Documentation Wiki

the project discussion mailing list


5 Things Every Aspiring Linux User Should Know

Yes. Another one of those ubiquitous bullet articles. Everyone loves ’em, it seems.

There are some fundamental things that every person who turns on a Linux box should be familiar with before proceeding. Some of these things are often overlooked or never learned by new Linux users. It’s a shame, actually. Knowledge of the fundamentals can create a great foundation for further advancement later on down the road. If you’re going to learn something, learn it right.

Here we go…

  • Numero Uno, in my opinion, is the importance of knowing and accepting the fact that the GNU/LInux operating system is NOT Microsoft Windows. Don’t try to make it such. GNU/Linux is a unique Unix-based operating system using the Linux kernel developed by Linus Torvalds and the GNU operating system developed by Richard Stallman and others of the GNU Project. Individual distributions of GNU/Linux, such as Ubuntu, Slackware, Debian, Arch, etc., are projects created by different people and supported by many, many dedicated coders, repository maintainers, software creators, technical writers, etc. To paraphrase a nearly cliché quote, it takes a village to raise a Linux distro. 😉
  • Item the second: ROOT IS GOD! Caution must be exercised at all times when user privileges are elevated to that of root. Working in the root environment should be done like riding a motorcycle. You CANNOT auto-pilot while riding a motorcycle; neither should you do so when you are root. In other words, pay attention to what you’re doing. Think twice before tapping that Enter key. One slip as root could destroy your entire OS. It’s a powerful tool. Be respectful of its power. Ignore this if you enjoy losing data regularly and reinstalling your OS from scratch.
  • Third thing to know: the command line interface is not a demon from Hell that will grind you up in its toothy maw. It’s just another tool available to the GNU/Linux user for accomplishing tasks that must be accomplished. For most of you, the GUI (graphic user interface) will suffice, but there will be times that you may need to use the command line. Don’t fear it. Embrace your inner geek. Learn the command line. You may find that you can accomplish more work more efficiently while using it.
  • Fourth on the list: Security, it’s a wonderful thing. Remember all those virus and malware scanners that you had to use in MS Windows. Remember how scared you were about email attachments. Remember that time your Windows system got corrupted and you had to pay someone at Best Buy $300 to get it working again? Bad memories, huh? Well, guess what? Just as dogs don’t catch the same diseases that banana plants do, GNU/Linux is not susceptible to the vast majority of the bad stuff out there that cripples MS Windows. Does that mean you’re 100% immune from troubles while running GNU/Linux? Well, no. However, I’d be comfortable in telling you that you would be about 99% immune. I’ve been running GNU/Linux operating systems on my computers for half a dozen years now. I’ve NEVER, not once, ever had any virus or malware issues.
  • Fifth and lastly:MS Windows and Apple/Mac have wonderful community support from multitudinous sites and communities around the Internet: I wouldn’t refute that fact at all. However, it’s important to remember that GNU/Linux and Open Source are products of the communities themselves in many cases. They are directly created, maintained, distributed and supported by many, many dedicated souls all across the globe. If you take the time to explore these communities, you’ll find that the amount of knowledge out there just waiting for you to come learn it is astounding. I don’t believe there is any other technical project so overwhelmingly supported by its adherents and fans in the global community quite like GNU/Linux and Open Source. Don’t be shy. Ask for some help.

Enjoy your new GNU/Linux adventure. It can lead to a long relationship with a fabulous operating system, outstanding open source applications, and wonderful friendships.

Later…

~Eric

Further reading:

The Open Source Initiative

The Free Software Foundation

The Linux Foundation

Open Respect


Community Burnout

Those of us in the Linux/Open Source community understand this well, I’m afraid.

Bruce Byfield writes:

Hang around the free and open source software community for any length of time, and you can’t help seeing examples of burnout. A colleague takes on too much, and suddenly they’re working harder for fewer results.

They have a hard time concentrating on their work. They neglect their personal life. When challenged, they become defense and unusually hostile. Eventually, they withdraw — and, sometimes, they don’t come back.

Read the rest of this interesting article at Datamation.

Later…

~Eric


Linux – How I Got Here… and Where I’m Headed

Sometimes, we all have to look back down the path we’ve taken to more fully understand that path that lies ahead.

I started my Linux Adventure a bit late in life. I’ve always had an interest in all things technical. My career for the majority of my working life was as an electronics technician (component level repair). I had aspirations at one time of gaining an engineering degree in electronics; other paths were taken, though.

My first experience with computers and programming and such was in 1979-80, when I was attending tech school. We were trained on kit-made 8080A computers that were so primitive that they were programmed directly via octal machine code. The outputs of the machines were led light displays. This was ridiculously simplistic by today’s computing standards.

I didn’t choose computers as my field of endeavor, though. I was much more interested in RF (radio frequency) and audio electronics. That decision probably made for a much different life than others would have. I regret lacking the vision that others had regarding the future of the computer. Hindsight shows me that I would have enjoyed a career in that field very much.

I did not have much interaction with computers from the early 80s till about 2000, with the exception of some fun times with a Commodore SX64 and some intriguing games from a company called Infocom. Oh, I had some experience with PC-type systems at the workplace in the early 90s, but I never really developed a passion for them.

I remember in the late 90s sitting at my kitchen table reading computer store ads and dreaming about getting a system for my home. I never could justify the money for it, unfortunately. I had other priorities. In 2000, my brother bought a new system for himself and passed his old system on to me. It was a little Pentium I – 90Mhz machine. I set that guy up and signed on to a bunch of free dial-up ISPs and off I went…

My current passion with computers and operating systems came about directly from my initial experiences with the Internet in 2000. Yeah, I was a little late coming to the party. I’ve been trying to catch up ever since. I have come a long way, though. I’ve been building my own systems since 2001 or so. I crossed over from MS Windows to GNU/Linux in 2006. I’m currently reading and learning all I can about the GNU/Linux operating system.

I made some resolutions in the new year to learn more about specific Linux subjects; one in particular was shell scripting. I’m currently reading and experimenting with that now. I’m also publishing some basic lessons regarding this stuff as I go along. I learned a long time ago that a great method for learning is to learn by teaching. I have to research and learn something before I can write an article about it here.

Whatever I learn, I like to pass on to others. That is the beating heart of the GNU/Linux Open Source community. I have learned so much from the selfless acts of others in this community that I am driven to give something back. It is a mission of mine to educate, to assist, to entertain, and to ease the transition of new Linux Adventurers into this wonderful community. I am no guru when it comes to Linux, but I have gained enough knowledge to get around without getting lost too often. I have much to learn yet, but when I do learn it, I’ll be here or somewhere helping others to learn it too.

A man called Bruno inspired me.

I would one day love to earn a living writing technical related articles or books regarding GNU/Linux. I would like to be employed in some fashion that would allow me to use my knowledge in a GNU/Linux business environment; as a systems administrator or a technical writer for some company or other. Sadly, my late-coming to the party and the fact that I’m no young spring chicken anymore has hindered my abilities to secure any positions like these. I’m totally self-taught and hold no industry certifications. I would love to attend school again to learn more in this field, but again… it doesn’t always work out that way.

I’m not at all sure what my future path is going to be like. It’s a day-to-day thing right now. However, I will always be learning; and with any luck, I’ll always be here passing it along to you.

Thanks for reading/commenting.

Later…

~Eric