Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Linux Software

Learning More About Linux? 184

teh moges asks: "From an administrator point of view, I know a lot about Microsoft Windows: where files are stored, where settings are, which registry keys to edit, how to change drivers, and so on. I made the initial switch to Linux a year ago. I now feel capable enough with using Linux, from an end user's point of view, so that when things go wrong, I can fix them. I now want to become even more familiar with Linux. Are there any great resources, such as websites, wikis or books for someone that wants to find out exactly how Linux works and how to fix and modify it?"
This discussion has been archived. No new comments can be posted.

Learning More About Linux?

Comments Filter:
  • Three letters (Score:3, Interesting)

    by i_should_be_working ( 720372 ) on Thursday April 19, 2007 @08:03PM (#18806511)
    LFS [linuxfromscratch.org]
  • heres a few (Score:3, Interesting)

    by drfrog ( 145882 ) on Thursday April 19, 2007 @08:26PM (#18806703) Homepage
    http://tldp.org/ [tldp.org]

    this is the linux doc proj the one place i found indispensable while learning slackware back in the day

    lately http://www.debuntu.com/ [debuntu.com] is a god send as well

    and of course , unlike windows software, most linux software readme files are actually filled with useful information

    othjer than that either a quick google on a specific question or jump onto irc will usually get you some help

  • by bersl2 ( 689221 ) on Thursday April 19, 2007 @08:41PM (#18806841) Journal
    While I agree that the Gentoo documentation is excellent, I can't say I liked the distribution. Maybe if I were to have installed it myself from scratch, instead of having inherited an installation, I might have understood why stuff broke as often as it does. But my one experience with Gentoo was on a production machine, and the first time I tried to update the system, the mailing system broke.

    My own advice to the submitter is to go between Gentoo and LFS with respect to automation and below both with respect to complexity and use Slackware. I've used it exclusively for my own machines for the several years I've used Linux, and in the process of taking a stable core system and trying to add onto it, compiling from source as necessary, I've broken and fixed things enough. The build scripts are available too, so you can customize as in LFS, but with the advantage of simple packaging.
  • by schon ( 31600 ) on Thursday April 19, 2007 @09:02PM (#18807005)
    I would say that you made a nice example of selective quoting, but you couldn't even get that part right. You probably should have said "no [...] registry".

    No magical black box registry

    the /proc filesystem? That's a "registry" if I ever saw one.
    Could you explain how it's a "magical black box"?

    And you know what? Everything in it shows up as (wait for it..) files - which was kind of the point of the message you replied to.
  • Just read this (Score:3, Interesting)

    by swillden ( 191260 ) * <shawn-ds@willden.org> on Thursday April 19, 2007 @11:39PM (#18808261) Journal

    There are probably some good books out there, and I hope you get some recommendations for them, but there is one key thing that you should learn about Linux that will get you 99% of everything you'll ever need to know about how your system works: How it boots.

    If you understand how everything gets started you'll understand how it all fits together, and, even better, you'll have the starting point you need for tracking down anything else you need to figure out. And the great thing is that it's simple enough to described reasonably completely in one brief slashdot post.

    The boot process consists of the following steps:

    1. The boot loader loads the kernel
    2. The kernel mounts the root file system and finds and runs /sbin/init, the first userspace process
    3. /sbin/init finds and reads /etc/inittab, which tells /sbin/init what shell script to run to kick everything off (/etc/init.d/rc, usually).

    That's it. All you have to do is go read that shell script and you'll find out how absolutely everything running on your system gets started, from the file systems that are mounted to the network devices that are configured to the graphical user interface. Of course, along the way, you'll run across dozens of commands and hundreds of configuration files that you'll have to look up, but with 'man' and a little persistence you will gain an understanding of each major component, where it lives, what it does, how it gets started, restarted, killed and modified.

    Even better, you don't have to worry about understanding it all at once. Once you find the /etc/init.d/rc script, and see how it executes all of the other scripts in /etc/init.d, you'll be well equipped to track down the answer to any question you have about how your system works. Sometimes getting an answer will mean traipsing through a few levels of indirection, but all the information is there. No magic, nothing hidden, all there for your perusal and/or modification.

  • by KWTm ( 808824 ) on Friday April 20, 2007 @12:56AM (#18808703) Journal
    From time to time I'll visit http://librenix.com/ [librenix.com], a "linux tutorial" aggregator site where people collect various tips about Linux and its various applications. This is often how I will hear about various applications, methods to secure your computer, tricks for administering Linux, etc. For example, as of this writing, among the first page list of articles we have a tutorial on installing VirtualBox in Linux, emacs essentials, how to install dual monitors, etc. Most articles are good, although the styles can vary since Librenix just points to various web pages; they weren't created for Librenix itself.

    Recommended.
  • by baldass_newbie ( 136609 ) on Friday April 20, 2007 @06:40AM (#18809899) Homepage Journal
    Running Linux is one of the best books for learning the overall structure of systems. Matt even notes the basic exceptions between Slackware and most other core distros in terms of structure and processing.
    Indispensible.

It's a naive, domestic operating system without any breeding, but I think you'll be amused by its presumption.

Working...