Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
More than I can (or would want to) list has changed between the 2.4 and 2.6 series. The most obvious being the Linux Security Framework (or LSM) of which SE Linux is a user. Even within 2.6 structures are in a constant state of upheaval. Kind of shows: for instance Linux Kernel Modules (or LKM's) that worked with earlier versions of 2.6 likely won't work with current versions. Wrt /proc I'm not sure what you mean, but if you look at /proc entries for a single process for instance you'll see 2.6.n kernels carry much more information.
Like I hinted at in the other thread you should ask very specific questions and also tell us in detail what it is you are looking for. The way you ask for things right now is similar to asking somebody to count grains of sand in the Sahara and also describe each one in detail. Studying (the progress of) the kernel's source could be beneficial.
I have no opinion on which is the best kernel internals book - I'm not a kernel hacker. But if you read the reviews for that book I linked to on Amazon.com you'll see that people who've read it seem to think it's an awesome book.