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.
Sockets - A Packet Snooper With A QT4 GUI (Req's libLQ-qt/mc2 dload) Part 1
Today's feature is
Running a packet snooper in an lqMiniTerm 'run' loop function.
[Note: the lqMiniTerm is evolving a bit and will continue to evolve for a while as we experiment and discover things that come up over and over that are easier to address in the mini terminal than in the main() file's code. Currently term_printf() is a candidate for becoming a miniterm feature. Find out why! :-) ]...
A couple of ways to work around unwanted C++ compiler warnings.
STL is a freaking nighmare to trace in a debugger so it's not too easy to tell what goes on in them but one thing became quite clear and that is that iterators are generic pointer types internally, which makes sense since STL needs to deal with so many different types.