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.
My apologies, previous versions had hidden lq-qt/mc2 lib dependencies. So I took the time to assemble only the needed functions into a lib include file, hiding my mc2 installation to make sure it didn't link by accident, and voila!
This is only a preview, but it's a stand alone app and it's full-featured as of this writing. This one truly has no mc2 dependencies.
First a bit of news re. the lq libs and mc2. (mc2 is the makefile creator developed here at this blog.)
The latest version of mc2 is undergoing testing and with any luck will include a SNAZZY set of graphics routines. The uitool is very nice for quickly writing moc files ui headers, etc. Currently some of the built-ins are a bit clunky, but they are effective and easy to use, such as the...
Note: This blog entry will to go away soon. Another version is in the works.
Note also that having the entire files rather than just a code snippet like a patch makes it easy see as much context as you need in order to recreate a change log by looking at ONLY the files that were changed from one build to another.
KDE's 'kompare' is an excellent utility for viewing changes.
So for now, since this is a little buggy (not serious but needs tweeking), consider...