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.
I’m sure it comes as no surprise that I’m a huge fan of open source development, as I’m sure most of you on here are. I’ve never really understood the mindset of, “We want you to buy and use our software, and you’re able to look at it far more objectively than we can much of the time, but we absolutely do NOT want you to be able to implement your potentially ground-breaking ideas into our software! And we’ll fix our own bugs, on our own time, thank you very much!”
/etc/rc.d/init.d contains all of the scripts to control all services. Any of them accept a start/stop/restart argument. Now, you have /etc/rc.d/rc1.d,rc2.d, and so on. These correspond to the various runlevels. For example, rc3.d is for text mode console, and rc5.d is x windows. In each of the rcn.d directories are a bunch of symlinks to scipts in init.d. They all begin with S or K (start or kill aka stop). They are arranged in order by the numbers following S or K. Here's the clever bit, the scripts
We refer to a file by its name. Computer refer to the file by its inode numbers. For every filesystem; there is an inode table. This table consists of Inode numbers & its correspondingmetadata. On the contrary; the mapping of filenames to inode numbers is stored in the directory containing the file.
To display the inode number of a file; say hindu one must issue the command
ls -i hindu
To display the total number of inode numbers in the filesystem ; you must issue the command...
And they have returned an affirmative verdict in my case.
Ok. It's a bit over the top. But if you haven't figured that out about me so far, you haven't read enough of my musings. Being over the top is what I seem to be about. And the comment here, refers to the fact that I got notice today of my case having been shipped. And yes, even the case, or should I say especially the case, is over the top.
I wrote about it before in the post before this one. Shall we call it the...