#652 in Computers & technology books

Reddit mentions of TCP/IP Illustrated: The Implementation, Vol. 2

Sentiment score: 4
Reddit mentions: 7

We found 7 Reddit mentions of TCP/IP Illustrated: The Implementation, Vol. 2. Here are the top ones.

TCP/IP Illustrated: The Implementation, Vol. 2
Buying options
View on Amazon.com
Height9.75 Inches
Length8 Inches
Number of items1
Weight3.9242282636 Pounds
Width2 Inches

idea-bulb Interested in what Redditors like? Check out our Shuffle feature

Shuffle: random products popular on Reddit

Found 7 comments on TCP/IP Illustrated: The Implementation, Vol. 2:

u/TheSuperficial · 6 pointsr/programming

No question, W. Richard Stevens' books on the protocols and the implementation were the definitive works.

I haven't gone back to them recently to see how they've aged, but much of what I know about TCP/IP, I learned from those books. (I was tasked with switching over the internal communications on a large telecom system from a proprietary protocol to TCP/IP - again, I'm talking about the communications between boards in the system, not outside to switching centers and COs.)

Unfortunately, Vol. 3 pre-dated HTTPS (and SSL in general), too bad, I'm sure if he were still alive, Stevens would have done that topic justice.

u/mioelnir · 5 pointsr/freebsd

I can't recommend that book enough. It will give you a great overview over the services the kernel provides, design decisions and data structures.

In addition to that, these resources might also be of interest to you:

u/Cheeze_It · 2 pointsr/networking

Generally I go here if I want a good overview and operational view.


If I want to go for the long haul and depth....I start here (I used this list as it's nice and abbreviated of what does what in RFC land). Reading through those will give you a much better idea of how things were "supposed" to work. How they work with a vendor will always be up to interpretation, but the vendors are interpreting those RFCs.

There are quite a few books on Amazon that will teach it to you as well. I honestly would consider getting them too. This, this, this, this.

There's so many good books but those should give you that deep understanding.

u/uhelpmezero · 2 pointsr/askmeaboutmyjob

>>> Would you say that the majority of linux administrator jobs out there are partly plain help desk support?

No, not the majority. Help desk type support is in the "IT" or "Office sysadmin" category. You can avoid those kinds of jobs especially since they usually require windows administration skills/knowledge.

>>> Or is there something else, something more advanced where you wouldn't have to deal with ignorant users, fixing the same issues over and over again?

Most internet type companies with funding and a practical business model will have "IT sysadmins" who support office/user systems and another group (something like "operations") that handles design, infrastructure, and maintenance of backend multi-stage environments. It seems like the latter is what you're interested in.

>>> Are there any particular technical skills (related to linux) that I should focus on to make myself more appealing to the employer?

  1. Be, or appear to be, eager to learn anything and everything.
  2. Read this book: http://www.amazon.com/TCP-IP-Illustrated-Vol-Implementation/dp/020163354X
  3. Build a linux server. Build several linux servers of different flavors. Build BSD and solaris servers. Build and try out any OS you can get your hands on. Check out firsthand what's awesome and what sucks about each.
  4. Learn a scripting language. Bash/shell is the most universal, but people have their preferences. I think python and ruby are what's in demand these days.
  5. Learn how to use the vi editor, even if it's at a very basic level.
  6. Break shit and figure out how to get it working. Fixing things that you didn't break is the most impressive thing you can do at a job. And the faster you fix things, the more impressive it is.
  7. If a potential employer asks you what you did during that year long gap in your resume don't say, "Not much. Well… I drank a lot."

    The most successful unix sysadmins I know are always learning new things. Most of them would also be classified as alcoholics, but that's a different question for later on in your career.
u/TSimmonsHJ · 1 pointr/networking

It's a very dated recommendation, but uhh.. I'm old.



Helped me lots, way back when.

u/jpeek · 1 pointr/ccna

The world of networking is huge. It's a marathon not a sprint. Huge repositories of information exist. Take your time to go through them.

Start with these -



Use this to help supplement your studies -


As always Cisco has a ton of white papers -


Free Presentations from Cisco Live -


If you wish to look at things from a different vendors perspective look into Juniper Day One -


Finally RFCs are good place to get the nitty gritty of the protocols/standards -


u/phao · 0 pointsr/C_Programming

Care to elaborate on what you mean by functional program framework?

Are you talking about doing functional programming in C? I think there is a book on that. I think it's this one: http://www.amazon.com/Functional-C-International-Computer-Science/dp/0201419505/ - I'm not so sure though.

Are you talking about building framework/programs that are functional (as in robust, secure, ...)? If that is the case, then there is an interesting book named "C Interfaces and Implementations" going through several kinds of modules you might want to implement in C, and going through how you'd elaborate an interface and an implementation for them => http://www.amazon.com/Interfaces-Implementations-Techniques-Creating-Reusable/dp/0201498413/. This book covers the sort of thing that I believe you should be studying after learning the overall language syntax and semantics, how to combine features of C to solve not so trivial algorithmic problems, and so forth. In summary, it talks about modules design (both interfaces and implementations) in C.

There are more books here, like those listed in here http://www.iso-9899.info/wiki/Books. You can also check some more learning resources here http://www.iso-9899.info/wiki/Usenet and here http://www.iso-9899.info/wiki/Web_resources.

Still on my second interpretation of your functional program framework (because idk much about the first one besides that book "Functional C"), there are tons of very complicated systems built in C, like operating systems, server software, and so forth. And for many of them, there were books written. Here are some software for which you can find books on their design and implementation: