Slashdot Mirror


Linux Power Tools

Dan Clough writes "I found Linux Power Tools to be a useful book, although it does have some shortcomings. It's a 644-page, well-written book that covers almost all aspects of managing, administering, and optimizing a working Linux system. The book's cover claims the target audience as intermediate to advanced users, but I think that beginner to intermediate would be more accurate. More advanced users may find Linux Power Tools a little beneath their level." Read on for the rest of Dan's review. Linux Power Tools author Roderick W. Smith pages 644 publisher Sybex rating 8 of 10 reviewer Dan Clough ISBN 0782142265 summary Well-written introductory and intermediate material; a useful jumping off point for many tasks though not the definitive source for specialized ones.

The text doesn't cover installing a Linux system, but does point out some of the differences among the major distributions in common use today, specifically Debian, Mandrake, RedHat, Slackware, and SUSE. Much of the distro-specific information is contained in a chapter on package management (RPM, deb, tar.gz, and the GUI tools for the aforementioned distros). I found this book a good reference for a new user (and especially someone self-administering their Linux box for the first time), but most "expert" users will not find much here that they don't already know.

The author covers a wide range of software that is frequently used. This includes the major desktop environments KDE and Gnome (with a brief discussion of alternate window and file managers which can be used to create your own custom environment), and office application suites (fairly simple overviews of OpenOffice.org, KOffice, and Gnome Office). Also covered are the two most common bootloaders (LILO and GRUB), printer configuration options (LPRng and CUPS), and a pretty basic section on command-line shells and scripting. There are a couple of chapters that touch on the basics of doing backups (using tar), and some general methods of improving the security of a Linux system (such as using proper passwords and stopping unnecessary services). These topics are followed up by several sections on basic networking configuration (TCP/IP, DHCP, and DNS), and controlling network access with firewalls, TCP wrappers, and xinetd service restrictions.

The last few chapters cover setup and operation of various common server applications, including Apache, FTP, Sendmail, Postfix, SSH, and VNC. All of these server descriptions are of the "general overview" variety, and additional resources will be required by someone trying to configure them for the first time. The book includes a basic glossary aimed at beginners, and an excellent index. The inside front and back covers contain a nice list of essential Linux configuration files, with their default locations, although distro-specific variations are not included.

The two sections that I found the most useful are the kernel customization chapter, and the one on optimizing the X Window System configuration.

Although the kernel chapter contains information that can be found elsewhere, it offers a very understandable explanation, and should make the process of compiling a custom kernel (for performance optimization) achievable for someone who hasn't done it before. In short, everything I needed to know about was right there in one place, and eliminated the need to bounce back and forth between the numerous how-to documents available online. By following this book's guidelines, I was able to successfully compile a kernel optimized for my AthlonXP CPU, containing only the drivers I need, which resulted in noticeable improvements in bootup time, application loading times, and desktop responsiveness.

In the X Window System chapter, the use of options in the XF86Config(-4) config file was well explained, including how to set custom modelines useful for a non-standard screen resolution and/or refresh rate. Font configuration was very clearly discussed, and included directions for adding additional fonts, and enabling smoothing (anti-aliasing) in applications.

Linux Power Tools is an excellent reference book, well suited to assisting in specific tasks related to Linux system administration. There is no real new information here, but this book does better than most at having many things you want to know very accessible in one reference volume. I would compare it favorably with another of my favorite books -- O'Reilly's Running Linux. In fact I've found it to be even more valuable for some specific tasks. It is very complete and recent (copyright 2003), and I highly recommend it to other intermediate level system administrators.

You can purchase Linux Power Tools from bn.com. Slashdot welcomes readers' book reviews -- to submit a review for consideration, read the book review guidelines, then visit the submission page.

10 of 144 comments (clear)

  1. I just bought by Dynamic+Ranger · · Score: 2, Informative

    "Moving to Linux: Kiss the Blue Screen of Death Goodbye!" by Marcel Gagne.

    It comes with a bootable CD so you can try out Linux without wiping your computer. I haven't tried it yeat, but the book is very readable and got great reviews on Amazon.

  2. Re:looking for a good windows to linux book. by RobertB-DC · · Score: 4, Informative

    I would like to find a book more suited to transitioning from windows to Linux

    While looking for Knoppix hints, I ran across a page by the author of something called Moving to Linux , subtitled "Kiss the Blue Screen of Death Goodbye." It purports to do what you're asking for, but I haven't bought it and don't know anyone who has, so YMMV.

    --
    Stressed? Me? Of course not. Stress is what a rubber band feels before it breaks, silly.
  3. Re:looking for a good windows to linux book. by irc.goatse.cx+troll · · Score: 4, Informative

    Can't help you on the book, but I'd advise you to aim for O'Rielly rather than the 'Learn $X in 24 hrs' type books.

    I did want to reply to a sepcific comment, though,
    "One of the reasons why I don't use Linux is because of this. It's not about fearing change as much as I know how windows works to the point I can set in up in under an hour rather than mess with linux for days."

    This really depends on your definition of 'set up'. You could pop in a knoppix cd and be done with knx-hdinstall in about 20minutes and have a fully working linux system, but thats not really set up as to my definition. When I setup a linux box, I configure it exactly how I want, everything from login configs to disable local passwords, shell configs to setup everything how I want, IP QoS configs so my downloads don't kill my ping in quake or SSH, SSH public keys so I don't need to retype a password everywhere, /etc/hosts so I can login to my servers without typing the full hostname, and plenty more. Its a process that takes the lifespan of your install, but generally you're satisfied after a week or so, but when I recently tried windows 2003 I found that it was the same experience -- a week or so to have things how you want it, but still a while longer to fine tune everything (each little apps preferences, installing all of the third party software you need, hunting down serial numbers, the relative[to linux] mess that is drivers/hardware) All of this stuff is optional configuration, but I feel its a required step for setting up your machine.

    One thing I can suggest though is if you're going to dual boot, use ext2 or ext3fs, and look into the 'ext2fsd' project. Mounts an ext2 filesystem in windows, defaults to ReadOnly but can be setup to write also. Very useful.

    --
    Pain lasts, kid. Its how you know you're alive. Sometimes I think this growing up thing is just pain management-TheMaxx
  4. Re:looking for a good windows to linux book. by Daytona955i · · Score: 2, Informative

    It's kindof hard to say this is how you do it in windows and then this is how you do it in linux.

    In windows, you click a lot of "ok"s and reboot a lot. In linux, you: ./configure; make; sudo make install

    In windows, you install buggy drivers that conflict with other drivers and crash your system. In linux, you either compile support directly into the kernel or compile a loadable module.

    In windows, you endlessly navigate through menu's to try and find a preference. In linux, it's usually one config file has all you preferences... and it's usually somewhere either in your home directory for user preferences or somewhere in /etc

    The problem is, windows creates a security blanket. It's easy to use and administer. This creates a cheapened definition of "expert" as well as creating a whole new definition of "beginner"

    Some of my definitions:
    An expert in windows would be someone who is comfortable editing the windows registry (or at least as comfortable as you can get playing with such a horrible creation) and knows what an IRQ is.

    An intermediate windows user knows what a dll is, how to install and configure any windows programs. They can also troubleshoot most problems.

    A beginner is someone who can navigate through the filesystem and run programs like office and internet explorer and be fairly confident in their skills as a user. Knows very little about maintaining their computers.

    Thus a beginner/intermediate may know to run defrag and scandisk every once in a while.
    A intermediate/advanced person may know the problem lies in the registry but can't fix it without doing a re-install

    Now for the linux definitions:
    a beginner is someone who knows what KDE or GNOME is and can login and open up a web browser. Can also usually install an easy-to-install linux distro (like redhat)

    an Intermediate user, knows what their hardware is and can not only install a linux distro but configure/setup most of the major applications (like XFree86) without using a GUI. Being able to recompile a kernel (that works) is mandatory for an intermediate user.

    An expert user is someone who has intimate knowledge of the linux filestructure. Is able to modify startup scripts. Basically, someone who could make their own linux distro.

    given this classification, it sounds like this book is for beginner/intermediate users. (That's not beginner OR intermediate)

    So far the closest book to a true Linux Powertools is Linux in a nutshell but the old UNIX Powertools is one of the greatest UNIX books and I would love to have one updated specifically for linux. It's a shame this book isn't it because I got really excited for a minute there.

  5. Re:The Point is? by dev0n · · Score: 3, Informative

    Perhaps in my original point I should have said "books are better FOR SOME PEOPLE" instead of just "books are better" .. because there ARE a lot of people out there who learn best from books, and who feel more confident about tackling new problems if they have a reference to refer to.

    I personally use a combo of books/web references whenever I do *anything* new. I learn best that way.

  6. Re:UNIX Power Tools by rk_nh · · Score: 3, Informative

    The updated third edition has been revised to include updated information on Linux, FreeBSD, Mac OS X, etc. I use it constantly and have never been stuck with a problem I couldn't solve.

  7. Re:Actually it's not a bad book by transient · · Score: 4, Informative
    Try apropos:
    % apropos schedule
    cron (8) - daemon to execute scheduled commands (Vixie Cron)
    cron [crond] (8) - daemon to execute scheduled commands (Vixie Cron)
    --

    irb(main):001:0>
  8. Not An Introductory Book by reallocate · · Score: 2, Informative

    It's not an introductory book. The title, while not very helpful or decscriptive, is in keeping with a long line of 'power tools' titles targetting DOS and Windows users.

    That quiblle aside, the book occupies a middle ground between the abundant "how to install Linux" books on one side of the spectrum and the myriad books for trained and wannabe admins on the other side of the spectrum. There's a market in that middle ground for books targetting Linux users who are neither newbies or admins, but simply people who want to learn a bit more.

    --
    -- Slashdot: When Public Access TV Says "No"
  9. Re:Books? by MoronBob · · Score: 2, Informative

    I find most of the resources and how-to's on the web refering to linux already outdated when I try to use them but you have to start somewhere. For beginners books are a good place to start. With linux and computers in general one needs to be persistant and get good at adapting to an infinite number of variables. I use books as an convenient way to get a good overview of the subject before diving in and getting my hands dirty. No resource is perfect or a replacement for experience.

    --
    Telecommuting! What about socialization?