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.
No computer that was returned from ANY customer should EVER be resold (or the hard drive thereof) with whatever data that customer left on it. There could be many bad things on there, including viruses, trojans, kiddie porn, and communication gateways for terrorists (yeah, gotta toss in the T-word somewhere).
This means wipe the disk completely and re-image the original OEM operating system in its initial state (ready to ask for your name and such).
Sometimes when you make some mistake in an app, like forgetting to enter a subject for email, you get these popups warning of the problem. Then you have to click OK to dismiss the popup and correct the error.
What I would like to see is for the app to also be checking the error condition that caused the problem, and if it gets corrected, take the popup down automatically. Of course this also means the app developer would have to learn about multithreading and how to put the popup...
BIOS is still not smart enough, and has failed to reach the "holy grail" of doing just what system administrators want it to do. This means you AMI. And the others, too.
What I (and just about every system administrator I've talk to about this) want is to be able to specify a device boot order that does NOT get modified by the BIOS just because the media or device is absent in a future boot cycle. I want to have the USB memory stick be the FIRST boot device, conditional...
Isn't one of the kernel design intentions to move more things to user space and keep the kernel itself smaller? I think network filtering should be one of those things.
So why haven't they done that? Is it considered too much of a performance issue to use user processes filter packets? I don't think it would be. But maybe there is some functionality missing that can be done in the kernel and not in user space?
The API would not be hard. Just create device nodes...