All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: Book Recommendations
Date: Tue, 12 Nov 2002 13:17:39 -0800	[thread overview]
Message-ID: <5.1.0.14.1.20021112123254.020f5b60@celine> (raw)
In-Reply-To: <070a01c28a83$ff0d0f30$64fea8c0@pkrausxp>

At 02:45 PM 11/12/02 -0500, Paul Kraus wrote:
>What books would you recommend?

Alice in Wonderland, A Farewell to Arms, The Great Gatsby, Zen and the Art 
of Motorcycle Maintenance, Goodnight Moon ... oh wait! You want computer 
books. See below.

>If it seems broad it is supposed to be :) I want recommendation on
>newbie, intermediate, advanced, scripting, programming, and security :)

OK. Seriously now. Technical books are not good in the abstract; they are 
useful for particular purposes. Without a better understanding of your 
needs, anyone here who makes recommendations is shooting in the dark. With 
that warning ...

newbie -- haven't been one in a long time. Back in 1993, there were no 
books for Linux beginners (there barely was Linux itself ... I never did 
manage a successful install of Yggdrasil). I still have the O'Reilly 
Essential System Administration from those days (actually, I replaced my 
original copy with the second edition), and though I never refer to it any 
more, in the early days, struggling with early versions of Slackware,  it 
was an everyday tool.  It's probably too out of date for use today (unless 
I missed a 3e), but I'd look for something like it. I'd also look closely 
at some of the book-level materials available from the Linux Documentation 
Project (the URL keeps changing, so google the phrase). Every 
beginner-level "Intro to Linux" book I've ever read (I used to review them 
for an online site) was junk, as were most "Intro to Unix" books.

intermediate, advanced -- here you move into specifics too quickly for a 
general answer. I find the O'Reilly Internet Core Protocols book almost 
indispensible (I refer to it at least weekly), and I still occasionally use 
the O'Reilly TCP/IP Network Administration. Among the others I keep around 
(offered not as suggestions for you, but illustrations of how quickly this 
area moves into esoteric specifics) are the PostScript Red, Blue, and Green 
books; several texts on data structures and algorithms; several books on 
user-interface design; and a book that discusses the details of the PPP 
protocol. (I rarely consult any of these, but when the occasion arises, I 
find their availability a real timesaver.) I also liked Elias' suggestion 
here, but I don't actually own  the Tannenbaum book he recommended, since I 
don't do a lot of OS development.

scripting, programming -- I'm not a good bash scripter, so I'll pass there. 
This area is, of necessity, language specific. I program in Perl, C, and 
C++ on Linux, and I actually use these books:

         Perl -- Programming Perl and Perl Cookbook (both O'Reilly 
publications).

         C -- Practical C Programming (O'Reilly) and Linux Application 
Development (Addision-Wesley). Beware of the original K&R C book that Elias 
suggested; it predates the ANSI C spec by many years, and the spec departed 
from it in ways that matter. I also like Kernighan and Pike's The Practice 
of Programming. The Stevens set Elias suggested is a classic, but I don't 
actually own it either.

         C++ -- Practical C++ Programming (O'Reilly). I also like Bulka and 
Mayhew's Efficient C++ ... but it is a couple of years old now, and there 
are probably better, newer books.

security -- it's a jungle out there, and security moves too fast for books 
to keep up. I do like Schneier's Applied Cryptography ... but every other 
security book I've ever bought seemed outdated within 3 months. Your best 
resource here is the Internet -- start with your Linux distro's security 
mailing list, perhaps add in a general-purpose list like bugtraq, and 
follow the leads they offer.


--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2002-11-12 21:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-12 19:45 Book Recommendations Paul Kraus
2002-11-12 21:17 ` Ray Olszewski [this message]
2002-11-12 22:51   ` Elias Athanasopoulos
2002-11-13 10:27   ` dashielljt
2002-11-13 14:11   ` Joshua Lee
2002-11-12 21:34 ` Elias Athanasopoulos
2002-11-13 14:01 ` Joshua Lee
  -- strict thread matches above, loose matches on Subject: below --
2005-12-23 23:11 Book recommendations ed
2005-12-23 23:27 ` Michal Piotrowski
2005-12-24  0:11 ` Steven Rostedt
2005-12-24 10:33   ` Pekka Enberg
2005-12-24 12:38     ` ed
2005-12-24 12:41       ` Steven Rostedt
2002-11-13 12:10 Book Recommendations [ Jason ]
2002-11-12  6:24 [ Jason ]
2002-11-13 22:01 ` Elias Athanasopoulos
2002-11-14  9:51   ` dashielljt
2002-11-14 20:32     ` Elias Athanasopoulos
2002-11-14 19:27       ` Ray Olszewski
2002-11-15 11:25         ` Elias Athanasopoulos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.0.14.1.20021112123254.020f5b60@celine \
    --to=ray@comarre.com \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.