Syndicated Linux NewsThis forum is for the discussion of Syndicated Linux News stories.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've been thinking about how to best improve the Linux* userland over the last few days. I was venting pretty loudly about my Linux gripe of the day -- I don't even remember what I was complaining about at the time, but it was a mess of shell scripting, pipes, and about half a dozen command line programs that were conspiring to drive me up the wall. Before I could get into a really quality rant, the kind that would peel paint off the walls, the friend who I was giving an earful to asked me a question, probably to shut me up.
"So what would you do to fix it?"
That's not exactly a new question, but I hadn't been asked it before. So I put a little thought into it.
Has this guy read Linux Is Not Windows? He wants everything to be done from the GUI and he wants every option available from the GUI. He also wants only one programming language to be used, and so on. I believe Redmond produce a distro that he'd like.....
There’s also the other common path for libraries to go, equally wastefully. Somebody writes the library in a relatively consumable language, like C. Then, as people need to use it, bindings pop up for it–Ruby bindings, Python bindings, Perl bindings, whatever. As “language purity” starts to take hold (and most of the time, at some point or another, it does), for some reason it becomes important not to depend on that C library anymore, and it’s time to reimplement that C library in Ruby, in Python, in Perl. C’mon, let me hear you now: “uggggggggh.”
ZOMFG!!!11111!! ITS TEH BINDINGZ!!1
He thinks bindings are "reimplementations" of the original C library.