Re: my reading plan need suggestion
From: Michael Zawrotny (zawrotny_at_jaguar.sb.fsu.edu)
Date: 06/07/05
- Next message: Zeljko Vrba: "Re: Shared Libraries : library paths ??"
- Previous message: Bilal: ""sigprocmask" doesn't return"
- In reply to: Måns Rullgård: "Re: my reading plan need suggestion"
- Next in thread: Asbjørn Sæbø: "Re: my reading plan need suggestion"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 7 Jun 2005 12:57:28 GMT
In addition to Måns's comments, which I agree with, I would add a few
more below.
Måns Rullgård <mru@inprovide.com> wrote:
> "jessewoo@gmail.com" <jessewoo@gmail.com> writes:
>
>
> Just remember that reading alone won't get you far. You have to play
> around with the machine, do some experimenting.
Absolutely. No question about it.
[ snip ]
> > 7, Unix in a Nutshell [O'Reilly]
I would probably buy it, but not necessarily read all of it. Much of
the content is also in some of the other books (sed, awk, vi, etc.) a
good portion of the rest is information that is already in the online
documentation in man/info format, although someone in the learning
stage will probably find the Nutshell version to be easier reading.
That being said, I usually find it faster to type "man foo" than to
reach up to the shelf, grab the book and find the page that talks
about foo, but it requires getting used to the terseness of most man
pages. I would consider that pretty much a requirement for any degree
of *nix expertise in any case.
[ snip ]
> > 11, UNIX Network Programming [Addison Wesley]
> > 12, TCP/IP Illustrated 1-2 [Addison Wesley]
You might switch the order of reading for these two. Doing network
programming without a solid understanding of TCP/IP would be tough.
TCP/IP Illustrated also makes fairly liberal use of tcpdump output to
show what packets are going where. tcpdump (or equivalent such as
ngrep, (t)ethereal, etc.) is an essential tool in debugging network
problems, including client/server communication.
> > Is the list wisely listed? Does it contain one or two that aren't
> > worth reading or does it miss any essential books? After finishing the
>
> Depending on what sort of programming you want to do, something more
> specialized might be useful.
Very true. Unix programming covers an enormous range, systems
programming, networking, sysadmin, ... The books you have cover all
of that, which is good, but after you've read a good bit of each,
you'll probably want to narrow your focus to maintain your sanity.
I would add a book or two on version control, using either cvs or
subversion. O'Reilly has print books on both, with the subversion one
also being available for free at http://svnbook.red-bean.com. You can
also find legitimate online copies of books on cvs, such as the one at
http://cvsbook.red-bean.com. Many people underestimate the need for
version control. It is a huge safety net to know that you can go back
to the last fully working version if the code gets completely hosed while
you do some kind of major reorganization or other sweeping changes.
A dozen books is a lot to absorb. This is especially true since some
of these books (e.g. all of the one that Stevens authored) have an
immense amount of detail in them, much of which is hard to appreciate
until you've got more experience in actual work in that area. You may
want to read for overview and let the details go by the first time
through, then come back and re-read the relevant parts when you are
working on a project related to that material.
Mike
-- Michael Zawrotny Institute of Molecular Biophysics Florida State University | email: zawrotny@sb.fsu.edu Tallahassee, FL 32306-4380 | phone: (850) 644-0069
- Next message: Zeljko Vrba: "Re: Shared Libraries : library paths ??"
- Previous message: Bilal: ""sigprocmask" doesn't return"
- In reply to: Måns Rullgård: "Re: my reading plan need suggestion"
- Next in thread: Asbjørn Sæbø: "Re: my reading plan need suggestion"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
