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.
Browsers these days are still trying to re-fetch data when I press the infamous "back button". I think this was always a dumb idea.
No doubt that is the cause for many cases of web site double ordering. Someone backs up so they can print out the results of a previous page where they committed their order, and it causes the data to POST again, which places another order. Now days, for POST, you get a pop-up that says the browser needs to re-post the data.
Traditionally, static configurations of IP addresses were made based on the interface names, which were always constant. When the kernel started doing device probes in a way that interface names would vary from time to time even on the exact same set of NICs, then we needed udev to keep things orderly. Turns out even udev can be fool when you change NICs, or when moving system hard drives to a new machine. New MAC addresses mean the old interface names are unavailable. So network configurations...
I wish Linux had a loopback (stored in a file) or virtual (stored in RAM) disk block device which supported partitions. I know some of you will be jumping the reply button to tell me about the offset option for loopback. Well, no, that isn't it. I want such a device for the purpose of running bootloader installs on. That requires the bootloader to be able to access both the whole device and the partition(s) on what are whole/part related device inodes.
One of the things businesses do not like to do is so many upgrades of software versions. Once they get things stable with a combination of versions that work together, they like to leave it that way. Usually, most major distributions work well because those distributions try to make it work that way. Then the only reasonable upgrade for a business seeking stability is to upgrade to the distribution's next version.
But even then, such an upgrade of a distribution takes staff time,...
I have no idea when IPv4 exhaustion will reach the point where you have to use IPv6. You have IPv4 now, and no doubt virtually all ISPs will keep people on IPv4 in some way (even if they have to use NAT) much like cable TV companies are providing at least some means for analog TVs to work (with boxes as the convert their TV systems over to all digital). So YOU may think you won't need access to IPv6 for a while.